operations/puppet triggers two jobs per patch, and thus consume two instances. We could have a single job instead that runs both tox and rake. Would be a bit slower but that will save an instance per patch.
Description
Description
Details
Details
Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
Merge operations/puppet jobs | integration/config | master | +1 -36 | |
Experimental job that merges puppet.git jobs | integration/config | master | +34 -1 |
Event Timeline
Comment Actions
Change 344404 had a related patch set uploaded (by Hashar):
[integration/config@master] Experimental job that merges puppet.git jobs
Comment Actions
Change 344404 merged by jenkins-bot:
[integration/config@master] Experimental job that merges puppet.git jobs
Comment Actions
Change 344410 had a related patch set uploaded (by Hashar):
[integration/config@master] Merge operations/puppet jobs
Comment Actions
Change 344410 merged by jenkins-bot:
[integration/config@master] Merge operations/puppet jobs
Comment Actions
Tested, works. I have update the castor cache by rebuilding a build with ZUUL_PIPELINE=postmerge.
Deployed and announced on ops list.
Comment Actions
Mentioned in SAL (#wikimedia-operations) [2017-03-23T16:22:07Z] <hashar> Merged operations/puppet.git Jenkins job in a single one that runs tox then rake - T160923