The RISE of DevOps: Certificate

There are lots of definition of DevOps out there and all are well defined. And as everyone says DevOps is not a new species in IT industries, it already exist out there somewhere in your industries.  You have to just collect it, brush it and make it sine by getting all pieces together.

And I realize  this when i was taking DevOps course..while going through the courses It took me flash back and then I realize , this is not a new things we are gonna do..this is the things which we are already doing or practicing on daily basis. Only difference is that we are not doing this together taking all the departments or division on same journey…

And at the end of course, it taught me, this DevOps revolution will be successful only when all teams are working together, respect each other, are customer oriented and having same goal and vision of an organization.. in simple word its a Culture and Professional movement… And I called it  “THE RISE OF DEVOPS“.

Thank you DevOps Institute for designing this Course and finally  I am Proud DevOps certificate Holder…thanks ITSM Zone for course contents..and BIG thanks to all Team members of Dev and Ops division of SGIS for their inspiration and guidance.

Through this posts I will be sharing my learning and practices of DevOps…So Stayed tune  to THE RISE OF DEVOPS 🙂

cert-devops-new
DevOps Foundation Certification

Tracker Response files not found (Tracker.exe)

Few Days Back while building one of the project we were getting below error continuously.

On looking in to msdn we finally got the workaround solution for this issue.

Solution:

Edit the build definition (Team Explorer => solution => builds => (select your build definition) right click Edit Build Definition => Process (on left) => 3. Advanced => under MSBuild Arguments paste the following:

/p:TrackFileAccess=false

from http://social.msdn.microsoft.com/Forums/en-US/tfsbuild/thread/baf16a4b-c25d-4722-a844-6276344b0db2

Here are words from MSBuild Developer from Microsoft.

The trigger for the error is that the GenerateResource task must be run during the build in such a way that we embed FileTracker (a tool we have been using for up-to-date check) in the process itself — when targeting 4.0, when targeting 3.5 on a 32-bit machine, or when targeting 3.5 on a 64-bit machine when running 64-bit MSBuild.

To work around the error, you can either set TrackFileAccess=false, as has already been observed, or if you’re on a 64-bit machine and targeting 3.5 exclusively, the error should also go away if you start using 32-bit MSBuild instead.

TrackFileAccess=false works around the error by turning off the use of FileTracker; the downside is that that means the you will no longer be able to use FileTracker-based up-to-date check, so your VS 2010 C++ projects and your GenerateResource task invocations will now always build, even when there have been no changes — the latter generally causing a cascading rebuild for the managed compilers as well, since they consume the .resources files.

Thanks,
Sara Joiner
Developer, MSBuild

For more Info you can visit below links.
https://connect.microsoft.com/VisualStudio/feedback/details/508650/tracker-response-file-not-found

Feel free to provide your comments and suggestion.
Thanks!!
MD. Jawed

NetTcpPortSharing service: failed to start the service

Few Days back when I was running and build, it started throwing an exception as:

The TransportManager failed to listen on the supplied URI using the NetTcpPortSharing service: failed to start the service because it is disabled.
An administrator can enable it by running ‘sc.exe config NetTcpPortSharing start= demand’..
—> System.InvalidOperationException: Cannot start service NetTcpPortSharing on computer ‘.’. —> System.ComponentModel.Win32Exception: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

Solution
To enabled, run the following command in console windows as mention in the error log
sc.exe config NetTcpPortSharing start= demand

 


To disable it, run the following command in a console window.
sc.exe config NetTcpPortSharing start= disabled

And after that run you build once again. I’m sure it would not throw any error next time.

Thanks,
Md. Jawed

Add an Alert on TFS when a build failed or partially succeeded

To get the notification related to your build you have launched the Team Foundation Build Notification tool to have a small popup alert every time a build finishes and starts.
But now you would like to go a bit further and receive a mail with the build result every time a build fails (or let’s say do not succeed).
Use the TFS’ alerts
The Team Foundation Server includes a powerful alert system, but by default, you cannot do so many things.

Use the Team Foundation Server Power Tools
If the Project Alerts does not allow so many things, the underlying alert system is very powerful. And you can use the Team Foundation Server Power Tools  that allow a very fine control of the alerts.


You can then create a new rule like the following one : 


Note that for the Send To field, you can either indicate an account name, or an email address. In the case of an account name, this corresponds to an AD account, and you must have configured the email address of that person in the Active Directory.

~jawed

Build Failed with an error as SGEN: Unable to generate a temporary class (result=1). SGEN: Internal compiler error (0xc00000fd) SGEN: Out of memory

One of the build were continuously failing with an error as

 
But in other hand the same build were getting succeeded on 32 bits Build agent machine.
Then we triggered the same build on our other 62 bits Build agent and we found that all 62 bits build agent are giving the same error while compiling this build.
And finally we came to this conclusion that the versioning of MSBUILD.exe which is creating an issue not the Build agent machine.
It means to run the same build with green we have to trigger the build on 62 bits build agent but force them to take 32 bits MSBuild.exe to run this Build.
To do this we have to perform this.
Edit Build Definition
Processes ->Advance-> MSBuild Platform-> X86.
 
Thanks,
MD. Jawed