I had recently setup a new stage in my deploy process. It had yet to be tested and a developer checked in some code which triggered a build. My team (devops) was promptly contacted with a generic failure message (from the person and system). What had happened?The build error as seen within Visual Studio was:
ERROR: The deployment for release template 'Prospect Connect' has not been completed successfully. Check the releases history for more details.
Exit: 1
This doesn’t give anyone much to go on. Furthermore the following message was also included which didn’t help:
Exception Stack Trace: at System.Activities.Statements.Throw.Execute(CodeActivityContext context)
at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager)
at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
Unfortunately as of 2013 Update 4 you cannot drill into the Release Manager error within Visual Studio. My developers don’t have access to RM yet so it was up to me to see what had happened.
As it turns out the new stage I added was failing because the environment is in a different domain and it could not access the drop location. What I wanted to change though is a way to generate good builds and green lights back to the team. They only care about deploys to the first (dev) environment and not the next stage.
To accomplish that I removed the automation from the second stage. I had only put it in place until the team could decide what their process was going to be. For now I will send notification to the devops team to approve and deploy builds to the next stage.
My goal was accomplished because the system stops at that point and send back to TFS Build a successful deploy message for the first stage.
What other things in RM have you seen that return an Exit 1 back to TFS Build?
No comments:
Post a Comment