-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Filter out plugins already installed #207
Comments
…d, creating a new pull request for this" This reverts commit 02cc97a.
…-e back to ensure build failues if there are issues
…-e back to ensure build failues if there are issues, based on plugins packged in the jenkins.war file.
Updated to base analysis on jenkins.war, test results: |
@gmacario I added the use case you suggested on PR #219 when I tested I observed with the current implimentation you have restart the docker instance for the plugins to get copied from the /ref directory and restart jenkins to see them. I see two choices(maybe you see more):
I am thinking approach #1 is probably the way to go for right now.. Thoughts? |
…rt running at compile time in the docker file and also running with exec on an exisitng container
@gmacario - I implemented a warning the you have to restart the container and squished the commits. |
…updated with feedback
#219 is merged |
…updated with feedback
When we pass in a list of plugins, it would be efficient if the list was filtered based on what is already installed. If the team is agrees this is a good idea I can take a shot at modifying the script.
The text was updated successfully, but these errors were encountered: