TFS 2015 vNext force build number

1
votes

Back in TFS 2013 you could temporarily hardcode a build number and then switch back to auto increment to skip ahead with build numbers. Now with TFS 2015 vNext, it seems like I can no longer do this. I went to make a new build definition and wanted to carry on from the last build number from my XAML build but it wouldn't move up.

Any ideas or workarounds for this?

1
tfstfs-2015
Can you show a detail example ? - Chamberlain
Apparently it doesn't work in TFS2015 according to stackoverflow.com/questions/3914801/… - you can see an example of what I'm trying to do in my comment in your answer. - jmcdade
Well, it's actually impossible. Please see my update answer. - Chamberlain
Well, it did work up until TFS2015. I would like to be able to convert my builds from XAML to vNext without losing my build count... - jmcdade
How did you achieve? Did it work in XAML build of TFS2015? You can customize the build Template of XAML build, however it can't be achieved in VNext Build. In VNext, you can only add build steps. I think this may be the reason. - Chamberlain

1 Answers

0
votes

It's also supported. Please check this link for detail steps:Generate custom build numbers in TFS Build vNext

update

Unfortunately, it's impossible.$(Rev:.rr) Its start by one.

What is $(Rev:.rr)?

To ensure that every completed build has a unique name. When a build is completed, if nothing else in the build number has changed, the Rev integer value is incremented by one.

Source:MSDN