3 ms·
A scheme I settled on a previous job that I really liked for internal apps was: branch-buildno Where branch is the git branch, and buildno came from our build
by ownedthx 11y ago
A scheme I settled on a previous job that I really liked for internal apps was:
branch-buildno
Where branch is the git branch, and buildno came from our build machine (Jenkins in our case).
examples:
* develop-5
* master-10
I then used this ivy-based project: https://github.com/sethcall/depends https://github.com/sethcall/depends to push those dependencies to our own internal artifact repository.
Because of this, I could say, 'use the latest artifact on the develop branch', or, I could say 'use exactly master-103'. Those two alone were pretty powerful.
By the way, I asked Maven devs if this would numbering scheme would possible (at the time, I would have happily used Maven instead of Ivy because I had to build some tooling to use Ivy); they were strongly against the idea: http://maven.40175.n5.nabble.com/Is-it-possible-to-tie-current-git-branch-to-project-version-td5543110.html http://maven.40175.n5.nabble.com/Is-it-possible-to-tie-curre...