Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

passowrd env variables not available from *-dispatcher-commit jobs on PJM #41

Open
zelial opened this issue Nov 30, 2016 · 0 comments
Open

Comments

@zelial
Copy link

zelial commented Nov 30, 2016

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/

mkluson added a commit to mkluson/platform-ci that referenced this issue Dec 21, 2016
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.
lulinqing pushed a commit that referenced this issue Dec 29, 2016
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant