-
Notifications
You must be signed in to change notification settings - Fork 55
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
plugins.txt: freeze plugins to working versions #563
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hah, I meant only freezing the plugins that we need by looking at which ones exactly Jenkins is complaining about. But this works too for now!
Did you verify that the latest Jenkins comes up successfully with this? |
Yeah I told him to just freeze them all. Maybe we can work on #562 soon? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
The issue was with |
EDIT: good to go, fixed a version typo |
We ran into a version mismatch between jenkins and the plugins while setting up jenkins in the staging cluster. Lets freeze the package versions to avoid the mismatch.
Saqib is the Elsa of Jenkins plugins. |
We ran into a version mismatch between jenkins and the plugins
while setting up jenkins in the staging cluster. Lets freeze the
package versions to avoid the mismatch.