Option to allow PR's to _not_ perm increment the build number
Hi :)
yeah, me again :/
Ok - this is the scenario...
Next build number: 35.
I have master and dev branches.
I have done all my work / team has done all their work and it's
all on dev. We are now ready to go live.
To do that, we PR from dev ->
master.
This fires off a build/test/no-deploy in AV. So the build number for this AV build is 35. Ok, np.
PR check finishes. all is green. I then ACCEPT this PR. AV kicks off again, but as number 36.
This means, every time I do a release, it always skips numbers.
Can we have the OPTION to not increment builds for PR's. Behind
the scenes, this might create build numbers for PR's like :
next-build-number + Guid.NewGuid().ToString() or
something.
Remember - this is just for PR checks ...... not the actual PR that is committed.
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Feodor Fitsner on 13 Jul, 2015 09:18 PM
Hm, what if that PR is updated and new build kicked off?
2 Posted by Pure Krome on 13 Jul, 2015 10:28 PM
Any time the PR is being checked the build number will not be incremented (if that option is set).
So if an update to a PR kicks of a CI PR-Build .... then no new increment.
Only for commits or merges to PR's.
Support Staff 3 Posted by Feodor Fitsner on 13 Jul, 2015 10:31 PM
So, how to make the version unique this case? Looks like version format should have kind of guid or timestamp or random?
- Feodor
4 Posted by Pure Krome on 13 Jul, 2015 10:45 PM
correct. because we don't really care about the version number for PR checks .. in my example (above) i just appended
Guid.NewGuid()to the end. any random junk can be appended, IMO.. like a timestamp, ticks or guid.Support Staff 5 Posted by Feodor Fitsner on 15 Jul, 2015 05:34 PM
OK, we'll see if that can be done nicely. Would you file a new issue please?
6 Posted by Pure Krome on 05 Aug, 2015 01:03 AM
Soz - totally forgot to add this issue.
Now added :)
Pure Krome closed this discussion on 05 Aug, 2015 01:03 AM.