use Git for Jenkins Config
I suggest we use SCM Sync configuration plugin for Jenkins. That way it is clear who changed what and why. Ideally we could even do review of changes but I don't think that's easily possible. I suggest we nonetheless use gerrit as git server (without review aka "refs/heads/master"). That way we can use Gerrit to comment on changes. Gerrit isn't great for post submit review but for Jenkins config it should be sufficient. I suggest we create a new gerrit repo "jenkins". No one else other than Jenkins should be able to write to that repo. Because the plugin doesn't support two-way sync.
#4 Updated by Szilárd Páll about 5 years ago
Roland Schulz wrote:
I suggest we make this a priority because it help with the other things with little extra work.
If it is indeed little extra work, it would be a great first step, I think.
I've had a brief look, as an example I only found the dummy/test repo of the author from that it's not entirely clear how readable and understandable are real-world jenkins config files and consequently how useful is it to have changes show up in CR. However, if gerrit changes published for every commit do not turn out to be useful, these can be disabled later, independently of the git repo itself.
#7 Updated by Roland Schulz about 5 years ago
It is now fully functioning. The changes now show up in gerrit: https://gerrit.gromacs.org/#/q/project:jenkins+is:merged . So far the xml configs of plugins isn't pushed yet.
#8 Updated by Teemu Murtola about 5 years ago
- Category set to Jenkins
Renaming the nightly documentation job seems to have screwed up the sync, and now it spams the footer of the pages. Plus the commit that for pushed to gerrit seems to be so big that at least Safari hangs trying to open the web page...