I had quite a few problems setting the workflow as follows:<\/p>\n\n\n\n
Jenkins<\/em>‘ Gerrit<\/em> trigger<\/em> page describes well what should be done with access for refs<\/em> in Gerrit<\/em>, but here’s the extra that makes all the difference:<\/p>\n\n\n\n If the rest is set well, time is for a test – ruin a build purposefully in a file, commit and push to refs\/heads\/:refs\/for\/ <\/em><\/strong>and sit and watch how Jenkins<\/em> tells Gerrit<\/em> to mark the commit that ruined the build as failed and to keep it in Limbo. Then do an amend with a fix, and Jenkins<\/em> will re-build the stuff, tell Gerrit<\/em> it is all ok now, and simultaneously send a signal to Rundeck<\/em>. Gerrit<\/em> will auto-merge this time good code to master, and the rest of the devs can pick up from there.<\/p>\n\n\n\n P.S. If people keep committing a new patchset<\/em> instead of amending it for Gerrit<\/em>, start yelling after the second time it happens, it might help do the manual monster merges that will follow… <\/p>\n\n\n\n <\/p>\n\n\n\n <\/p>\n","protected":false},"excerpt":{"rendered":" I had quite a few problems setting the workflow as follows: I’d make a change in ansible files, and push them to a git behind Gerrit Gerrit would trigger Jenkins with the new commit, and Jenkins would apply the linter on the committed files. If all is good, the files are send upstream to Rundeck that than picks the nodes …<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-48","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/blog.simulakrum.vpndns.org\/index.php?rest_route=\/wp\/v2\/posts\/48","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.simulakrum.vpndns.org\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.simulakrum.vpndns.org\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.simulakrum.vpndns.org\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.simulakrum.vpndns.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=48"}],"version-history":[{"count":1,"href":"https:\/\/blog.simulakrum.vpndns.org\/index.php?rest_route=\/wp\/v2\/posts\/48\/revisions"}],"predecessor-version":[{"id":49,"href":"https:\/\/blog.simulakrum.vpndns.org\/index.php?rest_route=\/wp\/v2\/posts\/48\/revisions\/49"}],"wp:attachment":[{"href":"https:\/\/blog.simulakrum.vpndns.org\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=48"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.simulakrum.vpndns.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=48"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.simulakrum.vpndns.org\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=48"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
for Verify<\/em>:
– Started: 0
– Successful: 1
– Failed: -1
– Unstable: 0
– Not Built: -1<\/strong>
for Code Review<\/em>:
– Started: 0
– Successful: 1
– Failed: -1
– Unstable: 0
– Not Built: -1 <\/strong>
for Gerrit Verified Commands<\/em>, under Successful<\/em> a –submit<\/em><\/strong> should be added in the line.<\/li>