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

[JENKINS-46386] Make SystemProperties safe to call from agent JVMs #3362

Merged

Conversation

jglick
Copy link
Member

@jglick jglick commented Mar 21, 2018

See JENKINS-46386. Tested manually using steps given in JIRA.

Accomplishes basically the same thing as #3065, but much more simply. Filing this now because the effectiveness of #3067 seems to have been lost after #3173.

Proposed changelog entries

  • Prevent some cases of linkage errors relating to Servlet classes when code is run on an agent.

Desired reviewers

@jenkinsci/code-reviewers @reviewbybees

@jglick jglick added the needs-more-reviews Complex change, which would benefit from more eyes label Mar 21, 2018
@jglick jglick mentioned this pull request Mar 21, 2018
6 tasks
Copy link
Member

@oleg-nenashev oleg-nenashev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. The difference in #3065 is mostly about potential extensibility of engine. Likely YAGNI

🐝

@oleg-nenashev
Copy link
Member

@reviewbybees done

@oleg-nenashev oleg-nenashev added ready-for-merge The PR is ready to go, and it will be merged soon if there is no negative feedback and removed needs-more-reviews Complex change, which would benefit from more eyes labels Mar 22, 2018
@jglick
Copy link
Member Author

jglick commented Mar 22, 2018

mostly about potential extensibility of engine

Exactly. Since the API remains restricted, we are free to refactor to an extension point if it seems necessary.

@oleg-nenashev oleg-nenashev merged commit 63a5803 into jenkinsci:master Mar 23, 2018
@jglick jglick deleted the SystemProperties-JENKINS-46386 branch March 23, 2018 17:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-for-merge The PR is ready to go, and it will be merged soon if there is no negative feedback
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants