Right now we have a custom job for running JJB after patches are merged to the 'jenkins' repo.
Once we can handle credentials in standard-CI we can move this functionality into the 'check-merged' job.
We have this in d/s jenkins already right?
no, both instances still use the deploy job.
Added the relevant credentials to secrets file.
secret name: jenkins_cli
Available keys: user, password, url
Patch created and verified, now blocking on code review
Patch is merged, new functionality verified, old job removed as well.