-
Notifications
You must be signed in to change notification settings - Fork 49
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
Add custom-folder-icon
to the managed set
#1406
Add custom-folder-icon
to the managed set
#1406
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.
The latest CI build failed on the bom-2.346
with:
Failed to execute goal org.jenkins-ci.tools:maven-hpi-plugin:3.32:validate-hpi (default-validate-hpi) on project sample: Dependency io.jenkins.plugins:custom-folder-icon:jar:2.0 requires Jenkins 2.357 or higher. -> [Help 1]
The way this works is we have the following BOM lines:
bom-weekly/pom.xml
bom-2.361.x/pom.xml
bom-2.346.x/pom.xml
bom-2.332.x/pom.xml
bom-2.319.x/pom.xml
Each line inherits from the preceding line. So bom-2.361
inherits from bom-weekly
and overrides (to older versions) any plugins where the latest version does not run on the 2.361.x LTS line.
Since custom-folder-icon
2.0 requires Jenkins 2.357 or higher, version 2.0 will work for the bom-weekly
line and the bom-2.361
line, but it won't work on the bom-2.346
or older lines. So you'll need to at least edit bom-2.346
to provide an older version for that line and below.
@basil Thanks for the clarification. Fixed in my latest commit. Yet the build still fails, not sure if this is an issue on github's end?
... which is later on causing ...
|
the developer connection url is probably using ssh, switch it to https to make it work https://github.com/jenkinsci/slack-plugin/blob/master/pom.xml#L38-L43 |
@timja So how would I go about this for the already existing releases? Would this mean I have to provide a new release for the "legacy" version as well as the current one that contain a https url? |
yes, do a backport release with that change to fix it |
Thanks for the PR @strangelookingnerd! |
No description provided.