Yeah, any commit needs to be done by an actual committer. What I'd advise for this release is that we do the TeamCity release build against a personal fork of the repo, where TeamCity has creds to push etc, and then the release manager pushes the commits/branches/tags to the canonical repo manually. It's a little awkward, but meets the requirements for ASF policies.
Can I get access to the TeamCity setup and a walk through of the process? I'd like to start working on how I can (wearing my Infra hat here) figure out how to make this process smoother and better integrated with Apache processes going forward - and admittedly, how I can port it to Jenkins, given my personal biases. =) I am also interested in seeing how the Groovy release process may be able to provide a model for other ASF projects looking for a more automated release build process. A. On Wednesday, May 20, 2015, Emmanuel Lécharny <[email protected]> wrote: > Le 20/05/15 11:26, Cédric Champeau a écrit : > > Another issue I remembered this morning: the artifactory plugin for > > TeamCity that we use is responsible for creating a release branch and > > tagging. It is also the one that updates the repository and changes the > > version numbers automatically. It is going to be a problem because to do > > this it requires credentials on the Git repo. Is this something that we > can > > ask to infra? Currently we use an authentication key, but user/password > is > > also supported. Of course we could cheat and use our personal > credentials, > > but ehm, if we can avoid this... > > If it's for a technical commit, then I think the best - and easier - > would be to ask INFRA. If they don't want to create this special user, > then the simplest solution would be to use the Release Manager creds, > but I agree, that would be not really convenient. > > >
