-
Notifications
You must be signed in to change notification settings - Fork 72
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
Various stability fixes discovered during testing #12
Various stability fixes discovered during testing #12
Conversation
@bparees @gabemontero Wouldn't mind if you could take a look, especially around the dependent plugin upgrades? |
</dependency> | ||
|
||
<!-- testing --> | ||
<dependency> | ||
<groupId>org.jenkins-ci.plugins.pipeline-stage-view</groupId> | ||
<artifactId>pipeline-stage-view</artifactId> | ||
<version>1.0</version> | ||
<version>2.1</version> | ||
<scope>test</scope> |
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.
i think we're going to need to work with @tdawson to get all these plugin packages updated before our image can consume this new version of the plugin. :/
Can someone put those plugin/rpm changes in a nice list. having everything in layered json isn't the easiest to determine everything that was changed. Also, jenkins 1.651.3 ... gonna be hard to do .... just letting you know, it will take longer than that plugins. |
Ah I thought @bparees told me I could safely upgrade the Jenkins version... |
@jimmidyson our rhel image currently includes 1.651.2, is that sufficient? (our centos image has 1.651.3) |
thanks for the tip - let me retest with 1.65.2 but I can't imagine any problems with that. |
@tdawson sure thing, here's the full list being introduced by @jimmidyson. I did not double check to see if any of our plugin rpm packages are already at these levels, however:
|
Thanks @bparees. |
Note that pipeline-stage-view is only upgraded in test scope here for me to visualize stages while developing plugin - I guess it makes sense to upgrade anyway, but that is not a requirement of this sync plugin. |
Retested at 1.651.2 & all works fine. I'm going to move most of the plugins to test scope as they're not hard dependencies of the sync plugin, but rather versions that should be adopted to help with general pipeline stability & feature set. |
I've just scoped dependencies properly. Required dependencies are: git 3.0.0 Recommended upgrades for pipeline jobs (but not direct runtime dependencies of this plugin) are: workflow-step-api 2.4 |
I'm going to self-merge this once tests have passed so I can push some changes that require this PR to be merged. LGTM |
thanks @jimmidyson! @tdawson i'd prefer to update everything @jimmidyson listed but since they aren't absolute requirements, feel free to manage your other priorities as needed. |
Just double checked and we'll have to update all of the ones listed. |
One quick question, looks like several of the packages are already newer than you have listed. Can I use the newer versions or would you like the specific ones you listed. Here is the list pipeline-rest-api 2.1 (2.2) |
Damn those over-productive developers... Upgrading is fine. |
Done: plugins updated to git 3.0.0 puddles have been created, images have been built with new puddles. I'll work on getting the jenkins-1 rpm updated. That's going to be trickier to get it into puddles. For now, proceed as if I can't update it. |
No description provided.