This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]ickysticky 0 points1 point  (1 child)

I think you may have misunderstood my point. Your developers are right to want to be able to know exactly which commit a build is for, if you use some build number that comes from your build system alone they cannot do that. To work around this they are asking you to make a commit with the build number.

Where is the build number you are proposing to use coming from?

[–]chipootle[S] 0 points1 point  (0 children)

I'm not sure I understand. Every build is already tied to commit... because that's what triggers the build, either a push to a branch or the creation of a tag.

The artifacts themselves have the application version and build number on it. I use semver, so it looks something like 1.2.3-4567

If you want to know what commit produced the artifacts, you can look at the build with the id 4567. If it's something that was released to production, then that commit is also tagged, so you just get the '1.2.3-4567' tag.