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

Updating another job's thresholds based on this job #75

Open
nrchandan opened this issue Aug 18, 2015 · 0 comments
Open

Updating another job's thresholds based on this job #75

nrchandan opened this issue Aug 18, 2015 · 0 comments

Comments

@nrchandan
Copy link

I use two Jenkins jobs in my project - one for building PRs and the other for building the master branch. I have the violations plugin set up in both the jobs, and both use the recently released ratcheting feature. However, this leads to frequent build failures when PRs compete to fix violations.

For example, one PR fixes some violations which automatically updates the threshold (say 10 pylint issues fixed out of 130 so now 120 is the new threshold), but the other PR only updates the README but now fails since the new threshold of 120 is lower than the 130 of the codebase on which this commit is based.

Ideally, I would like to disable ratcheting in the merge job and keep it enabled in the master job, but have the master job post the new thresholds to the merge job on successful build. Does it make sense? Is there a "right" way to do this? Is it possible to update the parameters of one Jenkins job from another using the Jenkins Java API, or does it necessitate the use of Jenkins REST API or file IO?

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