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

Calling jenkins job builder with no config file #44

Merged
merged 1 commit into from
Dec 29, 2016

Conversation

mkluson
Copy link
Contributor

@mkluson mkluson commented Dec 21, 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.

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.
@optak
Copy link
Contributor

optak commented Dec 21, 2016

I consulted this patch with Martin today and I would recommend it for merge.
It can fix build-on-commit use case.
If not, well,... it's broken already and nobody except from baseos-qe uses it, so the risk of regression is minimal.

@lulinqing lulinqing merged commit a51105b into RHQE:master Dec 29, 2016
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

Successfully merging this pull request may close these issues.

3 participants