Read-only deploy keys

Re:Read-only deploy keys by sytse on Wednesday June 17, 2015 @05:26AM (#9730753)

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

[ Parent | on HN ]

Re:Read-only deploy keys by llasram on Wednesday June 17, 2015 @05:46AM (#9730805)

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.

[ Parent | on HN ]

Re:Read-only deploy keys by sytse on Wednesday June 17, 2015 @06:54AM (#9730983)

Why not use the sha as the build identifier across SCM, CI and deployment? It exists already.

[ Parent | on HN ]

Re:Read-only deploy keys by mdaniel on Wednesday June 17, 2015 @04:22PM (#9734982)

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"

[ Parent | on HN ]

Re:Read-only deploy keys by sytse on Thursday June 18, 2015 @08:13AM (#9738053)

Good point, but if you bump the version yourself why not set a tag?

[ Parent | on HN ]