Closed nagyo closed 11 months ago
Kindly pinging the owners of the origin PRs, if you could take a look that would be awesome 🙏🏻 , @jenkinsci/google-oauth-plugin-developers, @amuniz, @basil
Please create a new release to include this fix 🤗
Note that the warning is just a warning and should not affect any real feature of this plugin. A release was not automatically generated because the PR lacks the right labels. I'll trigger a release now.
I'll trigger a release now.
Oh, I can't as I don't have permissions. Can you take care @basil? I think if you add one of the "releaseable" labels to this PR and trigger the cd pipeline then it will generate a release.
In #188 a dependency inconsistency was introduced by removing the version of oauth-credentials (at that time
0.646.v02b_66dc03d2e
), see:https://github.com/jenkinsci/google-oauth-plugin/pull/188/files#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8L182
and adding a bom version (
2465.va_e76ed7b_3061
) that contains the previous version (0.645.ve666a_c332668
) of oauth-credentials.See bom version added: https://github.com/jenkinsci/google-oauth-plugin/pull/188/files#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8R89
See version of oauth-credentials in bom: https://github.com/jenkinsci/bom/blob/2465.va_e76ed7b_3061/bom-weekly/pom.xml#L715
Due to this change when installing the google-oauth-plugin to a vanilla Jenkins (2.426.1) the following exception is thrown:
This originates back to a java API change in the oauth-credentials-plugin, see https://github.com/jenkinsci/oauth-credentials-plugin/pull/16
With the update of the bom version the proper oauth-credentials plugin is registered as a dependency, see changes between the current and the next bom version:
https://github.com/jenkinsci/bom/compare/2465.va_e76ed7b_3061...2483.v3b_22f030990a_#diff-df30c196b4c4872fdfa9378b991827b2433d220d66f83c0f0a1e868010ee3767R720
The PR aims to resolve issues #200 and #204
Testing done
Local maven build passed with the updated bom version. A locally built hpi file was installed on a vanilla Jenkins (2.426.1), no exceptions were observed.
I'm no expert of dependency chains between different Jenkins plugins, so please take that into consideration, I just followed the clues along the way.