Release Management and Dsc - How to queue a build when a release is in progress?

I have VSO and Release Management 2013.4 working and deploying to Azure vm's via DSC
The build profile is set to trigger on commit to the Git repo and the release template is set to be triggered on successful build from TFS
However if a developer commits in quick succession the resultant builds cause releases to overlap in RM? - this causes some of the releases to fail with a DSC error ("the consistency check or pull cmdlet is in progress....")
Is there a way to force RM to prevent concurrent releases? (based on the same release template and build profile)

Thats correct - in this instance its VSO as source control and using the hosted release management to attempt to deploy to azure vms
And yes build takes about 5 minutes but the release template can take up to 15 minutes to run - this means that a second build can cause the same release template to run again (its set to trigger on build)
Error log from RM
xception Message: New deployment is not allowed as an another deployment is in progress. Retry the deployment after sometime. (type OperationFailedException)
Exception Stack Trace: at Microsoft.TeamFoundation.Release.EnvironmentProvider.Azure.Implementation.AzureDeploymentProvider.ReadDeploymentResponse(DeploymentResponse response)
at Microsoft.TeamFoundation.Release.EnvironmentProvider.Azure.Implementation.AzureDeploymentProvider.DownloadBuilds(DeploymentMachineSpecification deploymentMachineSpecification, AzureStorageSpecification azureStorageSpecification)
at Microsoft.TeamFoundation.Release.EnvironmentProvider.Azure.Implementation.AzureDeploymentProvider.RunScript(String scriptPath, String configurationPath, MachineSpecification machine, StorageSpecification storage, Dictionary`2 configurationVariables)
at Microsoft.TeamFoundation.Release.Tasks.DeployDsc.Execute(DscComponentParametersV2 dscComponentParameters, AzureStorage azureStorage, String[] dnsNameAndUpdatedWinRmPort, String userName, String password, String dscScriptPath, String dscConfigurationPath, Boolean skipCACheck)
at Microsoft.TeamFoundation.Release.Automation.Tasks.DeployDscTask.DscExecute(DscComponentParametersV2 dscComponentParameters, AzureStorage azureStorage, String[] dnsNameAndUpdatedWinRmPort, String userName, String password, String dscScriptPath, String dscConfigurationPath, Boolean skipCACheck)
at Microsoft.TeamFoundation.Release.Automation.Tasks.DeployDscTask.DscDeploy(AzureStorage azureStorage, DscComponentParametersV2 dscComponentParameters, String userName, String password, String dscScriptPath, String dscConfigurationPath, String skipCACheck)
at Microsoft.TeamFoundation.Release.Automation.Tasks.DeployDscTask.Execute(IAutomationContext context)
at Microsoft.TeamFoundation.Release.DistributedTask.TaskProcessor.TaskExecutor.Execute(TaskExecutionContext context)

Similar Messages

Release Management and Azure Hosted Build Agents

Good day,
I configured Release Management as follows:
http://intovsts.net/2014/11/06/connect-visual-studio-release-management-to-visual-studio-online-and-microsoft-azure/
In this material mentioned that it is for VS Online (which I don't use)... However, I can't get it to work with Hosted Build Agent in Azure. When I try to release I get error
"Exception Message: The directory name is invalid (type Win32Exception)"
What actually mean that Release Management Client is not installed on the Build Agent.
Is it so, that I can't use Release Management with Hosted Build Controller/Agent? What other options to drive test Release Management w/o full TFS installation are available?
Looking forward for your answers! Thank you in advance!

Hi Voron81,
Thanks for your post.
You’re using On-premise TFS Server(TFS 2013 Update 4) rather than the VSO? If yes and you installed the RM Server, you should install the RM Client on your On-premise build agent machine.
For which software installed on hosted build server, please refer to the information in this article:
http://listofsoftwareontfshostedbuildserver.azurewebsites.net/.
If you want use your VSO account as RM Server to deploy to Azure, please refer to the solution this article:
http://www.visualstudio.com/get-started/deploy-to-azure-vs.
For how to use the VSO account as RM Server, please refer to the steps in this article:
http://www.visualstudio.com/get-started/manage-your-release-vs.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

I cannot see my Iphone 4 in my device window in the finder anymore. It use to appear so I could copy the camera pictures off of it and transfer them to other folders. Does anyone have and idea how to get it back when you plug it in initially. Thanks

I cannot see my Iphone 4 in my device window in the finder anymore. It use to appear so I could copy the camera pictures off of it and transfer them to other folders. Does anyone have and idea how to get it back when you plug it in initially. Thanks

You will want to open iPhoto, go to the iPhoto menu and select Preferences. Under the General tab, next to Connecting camera opens: select iPhoto. Close the preferences and quit iPhoto. Reconnect your iPhone 4. iPhoto should open automatically and offer to import your pictures. Import them and then do what you want with them.
Best of luck.

How do I find out when a release will be made containing fixes to known bugs?

I'm currently using Firefox 22.0 which is part of Ubuntu Precise (12.04). I have not been able to find out when a release will be made containing fixes to known bugs in Firefox. How do I find out when a release will be made containing fixes to known bugs?

For desktop
* latest release http://www.mozilla.org/firefox/notes/
* latest beta http://www.mozilla.org/firefox/beta/notes/
* latest Aurora http://www.mozilla.org/firefox/aurora/notes/
For mobile
* latest release http://www.mozilla.org/mobile/notes/
* latest beta http://www.mozilla.org/mobile/beta/notes/
* latest Aurora http://www.mozilla.org/mobile/aurora/notes/

What is Extension Manager and what/how do you use it?

What is Extension Manager an how do you use it?

Please refer to http://helpx.adobe.com/extension-manager/topics/extensions.html.

Media and Effects manager and video windows won't show up when STP launches

Today I launched Soundtrack Pro (from FCP Studio 5 Academic) and neither the Media and Effects Manager window (with Browser, Search, Favorites, Bin & Effects tabs) or the Video would show up. All I get is the project window.
When I tried importing an audio file or opening a multi track file, I still don't get these two windows, and under the window menu, all of these options are GREYED OUT.
Is there a certain setting I need to bring up the other two windows this program needs? Shouldn't they just be there when the program launches? HELP!

Update:
So, I just tried re-installing the software and I still only get the multi-track window when the program launches. I can not see any way to get the video viewer or Media and Effects manager windows to show up.
Please, what am I doing wrong?

How best we can use the Rollback and RollbackAlways mechanism in Visual Studio Release Management Template

Hello All,
We need a clarification on Rollback and RollbackAlways in Release template.
We checked a scenario for Rollback and RollbackAlways:
In Release Template, we have the first activity as “Configure Application Pool” and then followed by a rollback action of “Create Application Pool”
and “Create Web Site” then followed by "Code Deployment" via TFS build.
We tested with 2 scenario’s:
With App Pool and Web Site already existing: when triggered the build, configure
app pool succeeded, then Rollback action was skipped (as previous action was successful), finally deploy the code executed (code deployed) and build got succeeded.
Deleted App Pool and Web Site: when triggered the build, configure app pool failed (as no app pool existed), Rollback action executed (as previous action failed) – created app pool and web site then finally
deploy the code executed (code deployed)
But build failed (Error: Configure app pool action failed).
Ideally the build should succeed as the roll back action got executed and code deployed successfully.
Please correct us if our understanding is wrong.
Also, Kindly let us know how best we can use the Rollback and RollbackAlways mechanism in Release Management
Looking forward for your positive response.
Thanks in advance.
Regards,

Hi Shashank,
Rollback Always runs if any of the actions in the template failed. Rollback will run if action just above rollback fails or if any of the actions below the Rollback fails.
Article here (http://www.incyclesoftware.com/2014/03/understanding-rollbacks-release-management/) clearly explains how Rollback and Rollback
Always work.
I think you come across this issue since you are using build to do the "code deployment" action. You should use the release template to do that.
As far as I know you cannot use Rollback to achieve condition check (App pool exist in your case) action.
For this you can create your own Power Shell component (which checks if the app pool exist and is not create it) and add it as a tool in RM server (RM Server Inventory).
Another option is you can follow the workaround in below thread "Answer" quoted below. That is execute Remove app pool regardless if it exist or not (which does not fail) and then create app pool.
I was able to get it working by removing the app pool which does not fail if it doesn't exist. Removing then creating seems the long way around but it works.
Flow:
Remove Application Pool
Create Application Pool
https://social.msdn.microsoft.com/Forums/en-US/43bf21c8-e233-4e58-a5a8-2592b78bc466/vs-2013-release-management-create-application-pool-fails-if-it-already-exists?forum=tfsbuild
Cheers!
Chaminda

RE: List Archive and Release Management

Hi back.
>> what procedures do people use to manage the development, testing
and release of software?
It's useful to have a separate repository for Development, QA, Production,
etc. It's true that you have to 'import' between them, each time you
propagate changes. It might seem like a pain to constantly export/import,
but actually it's better that way.
Firstly, you should only export to QA when you're absolutely sure it's ready
for quality assurance, and this doesn't happen every day (or shouldn't)
Second, the advantage of this is that you get a 'clean' import and compile
each time, with no other baggage. This is especially critical when you
migrate from QA to a production environment.
There's no need to have a testing_verXX repository, just make a different
workspace for each version of test.
Just check out all the components, import, and integrate. The 'old'
workspace will have a snapshot of the old release.
* Don't Update that old workspace or you'll lose it!
* Put an administrator password on the repos, to protect against
inadvertent usage.
* It's expensive to have many repositories running on your environment
manager, so I recommend only one repos for each of development, QA and
Deployment.
* You might want to consider only bringing up the production repos as
required, they hog RAM like crazy.
It's critical to have a complete image of each version of every application
you have in production. That way, you can recreate any problem.
It's even useful to migrate your development repos every now and then. As
you know, these repos beasties can grow quite large, and it's god to start
from scratch on a regular basis.
For example, every month or so, our core architecure team releases a new
version of the core components. We all integrate, and we create a new repos
from the core architecture stuff, and import all our stuff over the top of
it. That way, we keep a loose coupling between sub-systems, and their stuff
never depends on ours. Also, with a split developmen repos, you can locate
the different teams on different intranets, or even on different sides of
the world, all with relatively little fuss.
Forté SCM hooks and SCCSWe use a unix version control called CMVC.
Whenever we integrate, it checks out the pex files, exports them, and checks
them back in.
John Pianezze
S1 Technologies (Asia Pacific)
Melbourne, Australia
-----Original Message-----
From: Duncan Kinnear [SMTP:[email protected]]
Sent: Wednesday, July 21, 1999 1:05 PM
To: [email protected]
Subject: List Archive and Release Management
Hi folks!
First of all, does anyone know what's going on with the list archive
on
SageIT? There doesn't seem to be a search facility anymore. Seems
a
bit weird when each message is appended with a little signature
'advertising' a searchable archive.
Second (and this is the biggy!), what procedures do people use to
manage the development, testing and release of software? I'm
talking
about how you keep them separate, how you do hot-fixes, how you
identify installed versions at customer sites, etc.
I've thought that we could do it with separate repositories for
"current
development", "testing_verXX", "release_verXY", etc., where we
export
from "development" and then import into "testing", and similarily
for
"release".
Also, we are looking at using the Forté SCM hooks and SCCS on our
Unix host to store historical versions of the projects/classes. But
we
somehow need to identify which version of a particular component is
installed at the customer site. I had thought of defining a
constant in
each project/class called "SCCS_VER" which contains the SCCS
keywords that get mapped to SCCS ID and date when put into SCCS.
Then the constant could be used to display these values in a
Window's
"About" window.
Any thoughts/opinions welcome.
Cheers,
Duncan Kinnear,
McCarthy and Associates, Email:
[email protected]
PO Box 764, McLean Towers, Phone: +64 6 834
3360
Shakespeare Road, Napier, New Zealand. Fax: +64 6 834
3369
Providing Integrated Software to the Meat Processing Industry for
over 10 years
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive
<URL:http://pinehurst.sageit.com/listarchive/forte>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/forte>

Under Forte 2 we used to export all projects, then import them into a make
repository, then produce an app. Due to the time involved importing &
exporting, and errors resulting from importing projects out of order, we
switched to making copies of the dev repository and producing apps from
that. For us, it used to take 2+ hours to export/import, as opposed to 5
minutes for copying repository files. Unfortunately, we have found that
unless we force-compile prior to deploying, we will get errors when
attempting to compile partitions.
Our current procedure:
Shut down dev repos
Copy to make env
make a workspace that includes all projects
force-compile
update
integrate
make a new workspace for each app to make
make each app
export code
remove unused workspaces
clean repos
-----Original Message-----
From: Peter Sham (HTHK - Assistant Manager - Software Development, IITB)
[mailto:[email protected]]
Sent: Wednesday, July 21, 1999 3:31 AM
To: John Pianezze; Duncan Kinnear
Cc: [email protected]
Subject: RE: List Archive and Release Management
Hi,
We, like what you've explained, keep different releases of our application
in different workspaces. However, when the release is getting larger, this
"check-out-every-components-then-overwrite-by-import" procedure get tougher.
Sometimes, it even creates garbage in the repository which corrupts my
workspace.
So, I have an alternative proposal on this procedure ( though I haven't
really test on this idea ) which is to create a new repository for each new
release.
What do you think?
Regards,
Peter Sham.
-----Original Message-----
From: John Pianezze [SMTP:[email protected]]
Sent: Wednesday, July 21, 1999 3:44 PM
To: Duncan Kinnear
Cc: [email protected]
Subject: RE: List Archive and Release Management
Hi back.
what procedures do people use to manage the development, testingand release of software?
It's useful to have a separate repository for Development, QA, Production,
etc. It's true that you have to 'import' between them, each time you
propagate changes. It might seem like a pain to constantly export/import,
but actually it's better that way.
Firstly, you should only export to QA when you're absolutely sure it's
ready
for quality assurance, and this doesn't happen every day (or shouldn't)
Second, the advantage of this is that you get a 'clean' import and compile
each time, with no other baggage. This is especially critical when you
migrate from QA to a production environment.
There's no need to have a testing_verXX repository, just make a different
workspace for each version of test.
Just check out all the components, import, and integrate. The 'old'
workspace will have a snapshot of the old release.
* Don't Update that old workspace or you'll lose it!
* Put an administrator password on the repos, to protect against
inadvertent usage.
* It's expensive to have many repositories running on your environment
manager, so I recommend only one repos for each of development, QA and
Deployment.
* You might want to consider only bringing up the production repos as
required, they hog RAM like crazy.
It's critical to have a complete image of each version of every
application
you have in production. That way, you can recreate any problem.
It's even useful to migrate your development repos every now and then. As
you know, these repos beasties can grow quite large, and it's god to start
from scratch on a regular basis.
For example, every month or so, our core architecure team releases a new
version of the core components. We all integrate, and we create a new
repos
from the core architecture stuff, and import all our stuff over the top of
it. That way, we keep a loose coupling between sub-systems, and their
stuff
never depends on ours. Also, with a split developmen repos, you can locate
the different teams on different intranets, or even on different sides of
the world, all with relatively little fuss.
Forti SCM hooks and SCCSWe use a unix version control called CMVC.
Whenever we integrate, it checks out the pex files, exports them, and
checks
them back in.
John Pianezze
S1 Technologies (Asia Pacific)
Melbourne, Australia
-----Original Message-----
From: Duncan Kinnear [SMTP:[email protected]]
Sent: Wednesday, July 21, 1999 1:05 PM
To: [email protected]
Subject: List Archive and Release Management
Hi folks!
First of all, does anyone know what's going on with the list archive
on
SageIT? There doesn't seem to be a search facility anymore. Seems
a
bit weird when each message is appended with a little signature
'advertising' a searchable archive.
Second (and this is the biggy!), what procedures do people use to
manage the development, testing and release of software? I'm
talking
about how you keep them separate, how you do hot-fixes, how you
identify installed versions at customer sites, etc.
I've thought that we could do it with separate repositories for
"current
development", "testing_verXX", "release_verXY", etc., where we
export
from "development" and then import into "testing", and similarily
for
"release".
Also, we are looking at using the Forti SCM hooks and SCCS on our
Unix host to store historical versions of the projects/classes. But
we
somehow need to identify which version of a particular component is
installed at the customer site. I had thought of defining a
constant in
each project/class called "SCCS_VER" which contains the SCCS
keywords that get mapped to SCCS ID and date when put into SCCS.
Then the constant could be used to display these values in a
Window's
"About" window.
Any thoughts/opinions welcome.
Cheers,
Duncan Kinnear,
McCarthy and Associates, Email:
[email protected]
PO Box 764, McLean Towers, Phone: +64 6 834
3360
Shakespeare Road, Napier, New Zealand. Fax: +64 6 834
3369
Providing Integrated Software to the Meat Processing Industry for
over 10 years
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive
<URL:http://pinehurst.sageit.com/listarchive/forte>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive
<URL:http://pinehurst.sageit.com/listarchive/forte>-
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive
<URL:http://pinehurst.sageit.com/listarchive/forte>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/forte>

Release Management questions

Hi all,
I've been looking at Visual Studio Release Management and on the whole, I think it's good, but I have a few issues that someone here may have already worked around.
Can I send an email to a group of users once the deployment is complete that includes custom text
including details about the build (e.g. build number)?
Is it possible to skip stages? We have 4 Development environments, but may not always want to deploy to all of them before moving onto Test
Our builds create 4 different sets of output - one for each environment (DEVT, TEST, STAG and PROD). Each of these is in a separate folder. Do I have to define separate components for each of these and specify the build number of each of them when triggering
a release? One of our apps has 7 different components and if I have to enter the build number 7x4 times it is going to take a while!
How can I run a script against a database that is not in a fixed location - e.g. c:\buildoutput\app\1.2.3 (4.5.6.7)\scripts\scripttorun.sql if the folder that contains the build output is different for every build (i.e. the version number changes)
Easy questions to answer I'm sure, but any help will be appreciated :)

Hi Mark
If you are planning on going for RM 'all in', in my experience it's probably best to be prepared to ditch what you already have in terms of deployment artefacts and start again so it works best with RM. This isn't as bad as it sounds. My thoughts as follows:
As far as I can see RM doesn't have a role in deploying to desktop clients as it's not designed for that.
My preference is to xcopy stuff where possible. If there are problems xcopy feels like it's going to be the easiest to debug.
You want to define one build definition that results in each of your deployables in 9 separate folders (I'm assuming the client is now out of scope here) as files you can xcopy with a tokenisation story in place for each deployable. (Different
story for web apps and services.)
You define your environments via Configure Paths > Environments
You link your environments / stages in a chain / pipeline via Configure Paths > Agent-based Release Paths (assuming you are not using DSC)
You create 9 components for each of your deployables. You don't worry about the build version as RM dynamically supplies this but you do specify the 'Path to package' eg \WebApp1Folder\_PublishedWebsites\WebAppName. The component will also
deal with tokenisation.
The components are used in the Agent-based Release Template which is based on the Agent-based Release Path specified earlier. Your 9 components will be used at each stage. The 'Path to package' will always be the same but the config will change as
required for each stage. There is no need to specify a parameter for the environment since you will reuse the component in each environment.
Your DEVT / virtual garages problem sounds like it needs some thought. Is DEVT part of the deployment pipeline ie is it a critical part of the route to live? If not then you will want to treat them separately.
Hope all this makes sense. At my work we are implementing continuous delivery on existing applications and it's 50 times harder than creating a demo pipeline.
Very happy to be helping by the way - other people's problems are a great source of possible blog posts :).
Cheers - Graham

Access, execute mof from pull server using release management

I have created a DSC pull server and deployed a mof to this server.
I could access the mof from pull server using below script and it executed successfully from powershell ISE.
    1.
Configuration
C_Pull_Webserver
    2.
    3.
LocalConfigurationManager
    4.
    5.
AllowModuleOverwrite=$true;
    6.
ConfigurationID
= "db00cf80-cb0e-4537-8344-90e3906e0b34";
    7.
RefreshMode
= "Pull";
    8.
DownloadManagerName
= "WebDownloadManager";
    9.
RefreshFrequencyMins
= 15;
    10.
ConfigurationModeFrequencyMins
= 30;
    11.
ConfigurationMode
= "ApplyAndAutoCorrect";
    12.
DownloadManagerCustomData
= @{
    13.
ServerUrl
= "http://myserver:8080/PSDSCPullServer/PSDSCPullServer.svc";
    14.
AllowUnsecureConnection
= "TRUE" }
    15.
    16.
    17.
#Create MOF to push
    18.
C_Pull_Webserver
    19.
#push the MOF: this will engage pull mode
    20.
$FilePath
= (Get-Location
-PSProvider FileSystem).Path
+ "\C_Pull_Webserver"
    21.
Set-DscLocalConfigurationManager
-ComputerName "CHN-AERO-VM13"
-Path $FilePath
-Verbose
I removed the below lines from the above script
19.
#push the MOF: this will engage pull mode
20.
$FilePath
= (Get-Location
-PSProvider FileSystem).Path
+ "\C_Pull_Webserver"
21.
Set-DscLocalConfigurationManager
-ComputerName "CHN-AERO-VM13"
-Path $FilePath
-Verbose
andand tried to access it from release management and i get the below error
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.AggregateException: One or more errors occurred. ---> Microsoft.TeamFoundation.Release.Common.Helpers.OperationFailedException:
Perform operation 'Invoke CimMethod' with following parameters, ''methodName' = SendConfigurationApply,'className' = MSFT_DSCLocalConfigurationManager,'namespaceName' = root/Microsoft/Windows/DesiredStateConfiguration'.
Failed to apply configuration in the DSC script to the computer. Consult the Logs below for details of the error.
System.Management.Automation.RemoteException: Unable to find the mof file. Make sure you are generating the MOF in the DSC script in the current directory.
   at System.Management.Automation.PowerShell.CoreInvokeRemoteHelper[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)
   at System.Management.Automation.PowerShell.CoreInvoke[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)

Don't know. How did you generate the MOF?
When I run this it works just fine:
Configuration C_Pull_Webserver{
LocalConfigurationManager{
AllowModuleOverwrite=$true;
ConfigurationID = "db00cf80-cb0e-4537-8344-90e3906e0b34";
RefreshMode = "Pull";
DownloadManagerName = "WebDownloadManager";
RefreshFrequencyMins = 15;
ConfigurationModeFrequencyMins = 30;
ConfigurationMode = "ApplyAndAutoCorrect";
DownloadManagerCustomData = @{
ServerUrl = "http://myserver:8080/PSDSCPullServer/PSDSCPullServer.svc";
AllowUnsecureConnection = "TRUE"
C_Pull_Webserver
¯\_(ツ)_/¯

SOA Integration between FS-Account Management and Bank Analyzer under BS 8.0

Hello all, we have set up the soamanager i.o. to integrate account manager and FS-business partner with the Bank Analyzer under Release 8.0 For the business partner this works fine. For master data of the current accounts we encounter the following problem:
We have configured the soamanager on the consumer side installing the consumer: BankAccountContractProcessingCurrentAccountContractEventOut On this side we would like to use message type: CurrentAccountContractFSCreatedBulkInformation_V3.
However the consumer (account management) provides CurrentAccountContractFSCreatedBulkInformation_V2 only, which is the xml-formate for Release BS 7.0.
Can anybody tell me, how to configure AM (consumer side), such that it provides the correct xml-formate for Release 8.0. For more information please refer to the document: IOA_technical_configuration_19. For further info on soamanager-config refer to the appendix.
Thanks, Sebastian Sachse

hi Sebastian
please refer to Katja Bornschein ([email protected]) as the owner ot the IOA-Scenarios. She will give you the information needed. As far as I know '_V3' is used only in FSAPPL500 (Release 9.0, GA in November 2014)
BR, Ernst

Release Management slow to tell TFS that a deployment was successful.

This is an example of the slowness from one of my projects:
A build is queued > MSBuild starts within ten seconds > the build is complete within 35 seconds > I see "Creating the release and waiting for deployment results" within 50 seconds from the build status page > The build deploys to the
first deployment stage, Release Management is done, there is nothing left to do
within 60 seconds > The build status page is "waiting for deployment result..." for 5-7 minutes > Build status changes to "Build succeeded".
Does anybody know why the build takes 1 minute to build and deploy, but the "Build status" page doesn't update until 5 minutes later?
I am using TFS 2013.4, RM 2013.4, and Agent-based releases. My template is "ReleaseTfvcTemplate.12.xaml"
Edit: Also, this Release Template seems to ignore "Release Target Stage". I set "Release Target Stage" to "Development Staging" (my second stage) and it still went to "Development" (my first stage). I did not have this
problem with the 11.1 template. Should I use that instead?

I am going to change the verbosity of all the logs to the highest setting and get back with you.
However, I wanted to add some additional information to the problem before I do:
We are using CI and gated check-ins.
If I set "Release Build" to False, then the build completes in 30 seconds.
If I set "Release Build" to True, then the build completes in 30 seconds. Within 60 seconds I can usually check Release Management and see that the build is past the "Deploy" stage and in the "Validation" stage. Checking the
deployment directory confirms that it has deployed. Up until recently the build summary would show that build as a success almost immediately... now it hangs for 5 minutes.
Sometimes the build summary shows a failure due to a Release Exception DESPITE seeing that the release was successfully deployed in Release Management.
This is a huge problem because we use gated check-ins. This happens whether a check-in triggers the build or it's a manually triggered.
Screenshot 1 of build configuration:
Screenshot 2:

Release Management 2013 Update 3 doesn't display retry button

When using Release management 2013 Update 3. I do not get a button to retry failed releases. I am viewed one answer on here that states the release needs to be automatically created from a build. I tried that solution and it still does not appear.
I am the Release Manager and I have every permission given to my account. Can anyone help me with this.
Thanks

Hi Release Mgmt,
Thanks for your post.
First, please upgrade your Release Management 2013 Update 3 to Release Management 2013 Update 4. Then run your TFS build to trigger the release template, if the release not be executed successfully, open the release in RM Client>>Releases tab, you
will see that Retry Failed Deployment button. Please refer to the discussions and answer reply in this post:
https://social.msdn.microsoft.com/Forums/en-US/e47c574b-adcc-4f58-8cd5-49c474adcbc8/how-to-repeate-a-release?forum=tfsbuild.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Error in TFS Release Management Server after Upgrading to Update 3

Some weird and unexplained error logged in InRelease aka (Release Management) server event log after upgrading Release Management Update 1 to update 3.
Below error started getting logged only after upgrading to Update 3.
Even though we started the Inrelease Server and all agents but no luck.
Any immediate help would be much helpful.
----------------------------------- EVENT LOG ERROR ------------------------------------
Timestamp: 12/15/2014 10:22:18 AM
Message: 'LambdaValue>' is not of type 'ServerActivity'. When loading this instance you must ensure that the activity with name 'LambdaValue>' implements
'ServerActivity'.: \r\n\r\n at
System.Activities.ActivityInstance.System.Activities.Runtime.ActivityInstanceMap.IActivityReference.Load(Activity activity, ActivityInstanceMap instanceMap) at System.Activities.Runtime.ActivityInstanceMap.InstanceList.Load(Activity activity, ActivityInstanceMap
instanceMap) at System.Activities.Runtime.ActivityInstanceMap.LoadActivityTree(Activity rootActivity, ActivityInstance rootInstance, List1
secondaryRootInstances, ActivityExecutor executor) at System.Activities.Runtime.ActivityExecutor.OnDeserialized(Activity workflow, WorkflowInstance workflowInstance) at System.Activities.Hosting.WorkflowInstance.InitializeCore(IDictionary2 workflowArgumentValues,
IList1
workflowExecutionProperties) at System.Activities.Hosting.WorkflowInstance.Initialize(Object deserializedRuntimeState, DynamicUpdateMap updateMap) at System.Activities.WorkflowApplication.LoadCore(DynamicUpdateMap updateMap, TimeoutHelper timeoutHelper, Boolean
loadAny, IDictionary2 values) at System.Activities.WorkflowApplication.Load(Guid instanceId, TimeSpan timeout) at System.Activities.WorkflowApplication.Load(Guid instanceId) at Microsoft.TeamFoundation.Release.ServiceProcessor.Processor.WorkflowInstance.WorkflowInstanceCacheSingleton.<.cctor>b__1(WorkflowApplication
app, Guid id) at
Microsoft.TeamFoundation.Release.ServiceProcessor.Processor.WorkflowInstance.WorkflowInstanceCache.CreateApplicationInCache(CreateParameters createParameters, Guid id) at Microsoft.TeamFoundation.Release.ServiceProcessor.Processor.WorkflowInstance.WorkflowInstanceCache.GetInstance(CreateParameters
createParameters, Guid id) at Microsoft.TeamFoundation.Release.ServiceProcessor.Processor.WorkflowInstance.CachedWorkflowInstanceLoader.GetInstance(DeploymentLog log, CreateParameters createParams) at Microsoft.TeamFoundation.Release.ServiceProcessor.Processor.DeploymentControllerServiceProcessor.ContinueDeploymentWithFinalComponentState(DeploymentLog
log) at Microsoft.TeamFoundation.Release.ServiceProcessor.Processor.DeploymentControllerServiceProcessor.ContinueDeployment(String log)
Category: General
Priority: -1
EventId: 0
Severity: Error
Title:
Machine: **********
Application Domain: /LM/W3SVC/1/ROOT-1-130630102320068767
Process Id: 6628
Process Name: C:\Windows\SysWOW64\inetsrv\w3wp.exe
Win32 Thread Id: 1344
Thread Name:
Extended Properties:

Dear Charles-Li,
Thank you so much for your reply.
we started using Release Management Update 1 and it was worked perfectly fine. then we move to upgrade existing Release Management(server,
Database and agent) with Update 3, which we did, and its working fine except lots of error as mentioned in above thread, are getting logged in server event log at regular interval till now(3-4 errors every second).
even though lots of error are getting logged but we are not facing any issue while using Release Management with update 3.
But i am bit curious to know out reason for getting those error.
<<clean
the cache folder and restrat Release Management and try again>>
already tried but no luck.
Thanks!!

TFS Group not updating in Release Manager

I have a bunch of release paths and plans tied to a development group with security for those plans defined by TFS Groups managed by the development team. They recently had a new hire start and added him to their TFS groups but the developer can't
access their release plans in Release Manager. I checked the groups he was added to in TFS in Release Manager and they don't have him listed. I verified that the developer is a member of those TFS Groups via the team's project site. I can't delete
the group and re-add it since it is part of multiple release paths and plans so, short of detaching the group from TFS and adding the user in Release Manager, I can't find a way to get the group to update in Release Manager. Any ideas?

Hi Coding4ever,
Thanks for your reply.
I reproduced this scenario in my RM 2013 Update 4 Client, and received the same result. For this issue, you can try this workaround: open that TFS group in RM Client, click
Detach From TFS button, then click Delete button delete this TFS group from RM Client, then click
New>>New From TFS to re-add this TFS group into your RM Client.
For this TFS group updated users not show in RM Client issue, please
submit it to Microsoft Connect Feedback portal at: https://connect.microsoft.com/VisualStudio. Microsoft engineers will evaluate them seriously.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Release Management and Dsc - How to queue a build when a release is in progress?

Similar Messages

Maybe you are looking for