I have built a new compiler host in the puppet-diffs project using buster. We should add this to the jenkins so it is avalible to be used by the puppet compiler. I belive this means applying the puppet-compiler-node label. We should also add something to the puppet-compiler code or jenkins job to alert the user what version of puppet is being used
Description
Details
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | jbond | T236468 add compiler1003 to jenkins | |||
Resolved | jbond | T236672 labstore1006.wikimedia.org failing to compile on compiler1003 |
Event Timeline
@hashar has added this to Jenkins now https://integration.wikimedia.org/ci/label/puppet-compiler-node/. for future reference this is something done manually via the web interface by someone (RelEng?) with permissions
Change 546146 had a related patch set uploaded (by Jbond; owner: John Bond):
[operations/software/puppet-compiler@master] puppet_compiler: Add puppet version to the PCC report
That is indeed done via the web interface. The new node can be seen at: https://integration.wikimedia.org/ci/computer/compiler1003.puppet-diffs.eqiad.wmflabs/
Change 546146 merged by Jbond:
[operations/software/puppet-compiler@master] puppet_compiler: Add puppet version to the PCC report
Change 546897 had a related patch set uploaded (by Jbond; owner: John Bond):
[operations/puppet@production] puppet_compiler: bump puppet-compiler version
Change 546897 merged by Jbond:
[operations/puppet@production] puppet_compiler: bump puppet-compiler version
The instance has been added to Jenkins https://integration.wikimedia.org/ci/computer/compiler1003.puppet-diffs.eqiad.wmflabs/
Seems there are some follow up patches for buster compatibility. Should we continue and have compiler1001 and compiler1002 rebuild as Buster instances?
@hashar i think if we get no more issue reports this week then we can rebuild 1001 and 1002 on Monday?