Remove version from configuration-as-code dependency#7
Conversation
| <groupId>org.jenkins-ci.plugins</groupId> | ||
| <artifactId>plugin</artifactId> | ||
| <version>3.18</version> | ||
| <version>4.46</version> |
| <properties> | ||
| <jenkins.version>2.60.3</jenkins.version> | ||
| <java.level>8</java.level> | ||
| <jenkins.version>2.319.3</jenkins.version> |
There was a problem hiding this comment.
This is a really old baseline, please consider the following.
https://www.jenkins.io/doc/developer/plugin-development/choosing-jenkins-baseline/
| <jenkins.version>2.319.3</jenkins.version> | ||
| <useBeta>true</useBeta> | ||
| <access-modifier-checker.skip>true</access-modifier-checker.skip> | ||
| <plugin-bom.version>1607.va_c1576527071</plugin-bom.version> |
There was a problem hiding this comment.
property is not needed just move it to where it is used.
|
Did not notice the PR before you pinged but I would like to see these values updated at least. :) |
bc362b2 to
5d634c2
Compare
|
Hi @jetersen, I tried to update my PR according to your comments. Can you have another look? Cheers, |
|
@jetersen could you take a second look? |
|
@jetersen can you maybe trigger the tests once again and merge this pr? |
|
I think the Jenkins file needs updating 🤕 |
|
@pascal-hofmann any chance you could take a look? |
This enables Bill of Materials for Jenkins plugins. See https://www.jenkins.io/doc/developer/plugin-development/dependency-management/#jenkins-plugin-bom
5d634c2 to
1e6bced
Compare
96e979e to
5a62240
Compare
|
Sorry, this got buried under other things on my desk. @jetersen Can you have another look? I assume my Jenkinsfile changes are not effective as I have not write access to the repo. |
|
I just had a look at the logs. It really does ignore my Jenkinsfile. |
|
Hi @jetersen, Cheers |
|
I will merge this, but revert if it fails |
|
Hmpf, this did not work. :( It's a bit hard to test for me, without permission on the pipeline. Would be great if someone could have a look. Thanks in advance, |
|
Tried here: |
The plugin did not work with latest releases of configuration-as-code because it pinned to version 1.0.