Embed and install native libraries #51
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 7 commits
August 18, 2015 20:09
This will be used to help extract the native libraries out of the JAR and into a suitable spot for semi-permanent storage, on both the Jenkins master and agents/nodes/slaves.
Verification was made possible with the NativeLibraryExtractor.
This pretty much completes the minimally viable implementation.
|
Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests |
olivierdagenais
added a commit
that referenced
this pull request
Aug 20, 2015
Embed and install native libraries.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In preparation for unpacking the native libraries on agents, switch to unpacking them on the master, as well. This has the added benefit that it should no longer be necessary to restart the whole Java process (i.e. just reloading Jenkins itself, from, say, Tomcat) when upgrading the plugin, because the native libraries will be loaded from a location NOT under the tfs sub-folder.
Manual testing
Uploaded the tfs.hpi to my Jenkins server, restarted it for what should be the last time and ran a job: the Microsoft/TFS_SDK/14.0.1/ folder structure was created and the appropriate native libraries were loaded.
Mission accomplished!