To test tool labs manifests. This would effectively be @scfc and myself at the moment.
https://integration.wikimedia.org/ci/job/operations-puppet-catalog-compiler/
To test tool labs manifests. This would effectively be @scfc and myself at the moment.
https://integration.wikimedia.org/ci/job/operations-puppet-catalog-compiler/
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | valhallasw | T97580 Allow Tool Labs volunteer roots to submit jobs on puppet-catalog-compiler | |||
Resolved | yuvipanda | T93644 Allow Valhallasw to sign an NDA |
+ @Joe who wrote the puppet catalog compiler.
The Jenkins access list is configured to allow trigger a build for people being member of either LDAP groups: wmf or nda.
@scfc has a NDA and is in the 'nda' LDAP group, so he should be able to trigger run.
For @valhallasw a NDA would be ideal and unleash a lot more tools (ex: https://graphite.wikimedia.org/ ). I am not sure I can add an access list that allow build of a single job nor do I know how nasty a run of operations-puppet-catalog-compiler can be though. I am willing to endorse your application for a NDA :]
@valhallasw is a member of the Phabricator project WMF-NDA, so I assume that just needs to be "reflected" in LDAP.
I am a bit confused about https://integration.wikimedia.org/ci/job/operations-puppet-catalog-compiler/build?delay=0sec which I assume is the UI? It mentions a lot of "Puppet 2 vs. 3". So I would enter in GERRIT_CHANGE_NUMBER the number of the change I want to test? Does LIST_OF_NODES allow Labs nodes, e. g. tools-bastion-01.eqiad.wmflabs, or does it only work for nodes in site.pp?
I can submit jobs now, so (although I can't get them to run *successfully* atm) this task is resolved.