3 ms·

I don't understand, won't you tag a release commit first manually and than have it be created by the CI server?

• llasram 11y ago
  Some people using manual tagging as a mechanism to communicate something to CI as you suggest, but others let CI tag successful builds. When I re-did my team's CI a few years ago I chose the latter because it creates less friction for continuous deployment -- every commit which passes the tests automatically becomes a deployable artifact with a monotonically increasing build number which can be tracked across SCM, CI, and deployment.
  • sytse 11y ago
    Why not use the sha as the build identifier across SCM, CI and deployment? It exists already.
    • mdaniel 11y ago
      Heh, you've never worked with a project/product manager, have you? "Yes, ma'am, version 1b6411f has been deployed successfully. Now I just need to edit the pom and bump the version to 2e1080d"
      • sytse 11y ago
        Good point, but if you bump the version yourself why not set a tag?