-
Notifications
You must be signed in to change notification settings - Fork 52
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 updatecli for plugins #1063
Conversation
Okay not sure why it reports: I had the same issue locally but I can't figure out why it is not able to see the shell scripts 🤔 |
Tested locally with changed values.yaml diff --git a/updatecli/values.yaml b/updatecli/values.yaml
index ac89ff5..12022d4 100644
--- a/updatecli/values.yaml
+++ b/updatecli/values.yaml
@@ -3,6 +3,6 @@ github:
email: "41898282+github-actions[bot]@users.noreply.github.com"
username: "github-actions"
token: "UPDATECLI_GITHUB_TOKEN"
- owner: "jenkinsci"
- repository: "bom"
- branch: "master"
\ No newline at end of file
+ owner: "jetersen"
+ repository: "jenkins-bom"
+ branch: "fix/bomPlugins" |
locally bash/powershell scripts works as intended however having updatecli run the scripts it messes with the standard out of
|
Co-authored-by: Tim Jacomb <[email protected]>
- jenkins2.289.x | ||
- jenkins2.303.x | ||
- jenkins2.319.x | ||
- jenkins2.332.x |
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.
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.
You mean when a given plugin gets updates for multiple LTS lines? I think it is fine for those to be separate PRs, since this is not the normal case. A plugin will only be mentioned in a bom-2.*.x/pom.xml
when it is overridden there relative to the newer lines, so when Jenkins baselines are updated across more than one LTS bump in a given plugin release, we would only be adding one such entry.
Lets try it, we can always modify it 😄 |
But why is this needed if Dependabot is already proposing PRs for these dependencies? |
Dependabot was not doing for all of them @basil only once where version number was appended to like credentials |
Sounds like a bug then, with this PR being a workaround for that bug. But better would be to determine the root cause and fix the original bug. |
Well again another problem is that dependabot does not understand the plugin version in relation to the Jenkins version. This fix uses plugin manager to update dependency according to Jenkins version for the certain BOM lines. |
That problem also applies to the plugins in |
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.
Do not understand how all of it works, but looks good. Thanks!
branch: "{{ .github.branch }}" | ||
|
||
sources: | ||
jenkins2.289.x: |
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.
Looks like this file needs to be maintained when adding or removing lines. Would you mind adding a note to https://github.com/jenkinsci/bom/#lts-lines to this effect?
- jenkins2.289.x | ||
- jenkins2.303.x | ||
- jenkins2.319.x | ||
- jenkins2.332.x |
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.
You mean when a given plugin gets updates for multiple LTS lines? I think it is fine for those to be separate PRs, since this is not the normal case. A plugin will only be mentioned in a bom-2.*.x/pom.xml
when it is overridden there relative to the newer lines, so when Jenkins baselines are updated across more than one LTS bump in a given plugin release, we would only be adding one such entry.
@jetersen this is pretty broken—it keeps on filing PRs for the same updates we do not want; unlike Dependabot it does not remember that a given update was rejected. Unfortunately my knowledge of all this is very limited and I could not figure out how to cleanly disable just the plugin updates without the core updates. |
@jglick I am unsure why these updates incorrect? 🤔 Seems fine to me 😕 https://github.com/jenkinsci/bom/blob/master/updatecli/update-plugin.ps1 |
I think it's this issue, #1507 (comment) Could just drop the line anyway |
Right.
Probably could; it has so many overrides at this point I am not sure there is much point in publishing new BOM releases, especially when we have a new line arriving (I hope) shortly.
Also an option. (For Dependabot you have this option in the YAML config but you can also just close a PR to reject a given update.) Probably beyond my Powershell skills. |
We can have it read a YAML config as well. We can also decide to turn off plugin updates for certain BOM lines when decided 🤔 |
fixes #1019
This will find the latest Jenkins version matching the
x.xx.x
and check each plugin in the specified pom.xml