Using the Release Template that came with Release Management Client (Update 2), we are trying to do an automated deployment using TFS Build and Release Management Server 2013 Update 2.
Everything went fine until we decided to start using tokenized Web.Config (Web.config.token) to help us manage our deployments.
It seemed simple enough, create the variables in the Release Template Components, and put matching __ VARIABLES__ in duplicate Web.config.token.
Set the Build Template to Process Build Tokens and hit go.
The build doesn't seem to actually process the token file and we are left with the original Web.config. Any ideas what I'm doing wrong?
It says it's processing the tokens but it doesn't actually do any of that. Build Log:
Overall Build Process
Overall build process
Update build number
Run on agent (reserved build agent {Redacted} Build - Agent 2)
Initialize environment
Get sources from Team Foundation Version Control
Associate the changesets that occurred since the last good build
Compile, Test and Publish
Run optional script before MSBuild
Run MSBuild
Built {Redacted}.sln for default targets.
Built ${Redacted}.csproj for default targets.
Built $/{Redacted}/.nuget/NuGet.targets for target(s) _DownloadNuGet.
Built $/{Redacted}.Database.sqlproj for default targets.
MSBuild Log File
Run optional script after MSBuild
Process the release
Get the Build Directory
If ProcessReleaseTokens is set
Initialize tokens
Prepare folder to search
Find all .token files
Process each .token file
Rename files
Assign
Remove read-only flag from x.y
Copy x.y.token to x.y
If ReleaseBuild is set
Try to release the build
Get the build details
Initialize release build variables
Get the Release Management install directory
Verify the Release Management install directory
Get the Release Management install directory (x64)
Get the Team Project Collection instance
If ConfigurationsToRelease is not set
Copy binaries to drop
Process each ConfigurationsToRelease
Release the build
Run the Release Management build process for the current configuration
Microsoft.TeamFoundation.Release.Build starting process...
Processing using the following parameters:
TeamFoundationServerUrl: {Redacted}
TeamProjectName: {Redacted}
TeamProjectWithCollection: {Redacted}
BuildDefinitionName: {Redacted}
BuildNumber: {Redacted}
TargetStage:
Creating the release and waiting for deployment result...
Release was created and deployment was successful.
If a Release Build error cccurs
Skipped due to successful completion
Run optional script before Test Runner
Run VS Test Runner
Run optional script after Test Runner
Get Impacted Tests
Publish Symbols
Perform Final Actions On Agent
Copy binaries to drop
Reset the Environment
