You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
there are jobs on the PJM[1] that need access to global variables defining access te jenkins instance via JJB. The JOB_BUILDER_USER variable is vissible but JOB_BUILDER_PASS isn't:
I come with better solution for issue RHQE#41. Instead of injecting password to all
jobs, which update or create some other job, I change the way how xml for
updating/creating job is obtained from source yaml file.
In case jekins job builder does not need access to Jenkins instance, it is called
without any config file.
I come with better solution for issue #41. Instead of injecting password to all
jobs, which update or create some other job, I change the way how xml for
updating/creating job is obtained from source yaml file.
In case jekins job builder does not need access to Jenkins instance, it is called
without any config file.
Hi,
there are jobs on the PJM[1] that need access to global variables defining access te jenkins instance via JJB. The JOB_BUILDER_USER variable is vissible but JOB_BUILDER_PASS isn't:
https://platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/ci-setup-dispatcher-commit/32/injectedEnvVars/
Please change the definitions of the dispatcher jobs so that they get created including the following yaml snippet:
wrappers:
- inject-passwords:
global: true
mask-password-params: true
(suggested by droble in https://engineering.redhat.com/rt/Ticket/Display.html?id=429262 )
Thank you
[1] e.g. https://platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/ci-setup-dispatcher-commit/
The text was updated successfully, but these errors were encountered: