DEV Community

loading...

Discussion on: Automate It - Be Lazy - Part II

Collapse
dmfay profile image
Dian Fay

Have you thought about having Jenkins close the issue once a commit message including its id lands on the master branch? Especially in concert with a pull request workflow, that would let the build server handle just about everything gitmergeandclean.sh does (Jenkins would need permissions to automatically delete the remote branch and wouldn't be able to clean your local repository). But you might have some specific process requirements that necessitate kicking off the merge manually.

Collapse
khmarbaise profile image
Karl Heinz Marbaise Author

Hi Dian,
first thanks for your comment.
And yes this could be done but unfortunately this can't be done on the Apache Software Foundation side, cause there we do not use pull request (or something which something like PR's). A PR must be "authorized" by a committer which means we have to create a branch for it and commit it later which means a name of a committer is given here (difference between committer/author)..cause the main source of truth is not GitHub but it is gitbox.apache.org/repos instead which does not directly support PR's in the way GitHub does. That's the reason why we need to go that way.

I'm currently experimenting with scripts to handle this also making this easier for me to support the contributions from other people in more simpler and faster way...