Skip to content
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

Use plugin bom version prior to trilead API upgrade #212

Merged
merged 1 commit into from
Jul 26, 2024

Conversation

MarkEWaite
Copy link
Contributor

Use plugin bom version prior to trilead API upgrade

The plugin compatibility tester mistakenly uses the version of optional plugins that is provided by the pom of the tested plugin rather than using the version of plugin that is listed in the pom file of the plugin bill of materials.

Because of that issue, the 2.426.x plugin bill of materials version needs to remain on an older version in order to not include an optional dependency on a newer version of the trilead API plugin.

3080.vfa_b_e4a_a_39b_44 is the version immediately before a trilead API plugin upgrade in the BOM.

More details are available in:

Additional information is also available in:

Testing done

Confirmed that plugin BOM tests pass with:

LINE=2.440.x PLUGINS=git-server,workflow-basic-steps,git,pipeline-model-definition,docker-workflow,blueocean TEST=InjectedTest bash local-test.sh

Once an incremental build is available for this pull request, I'll test it with the plugin BOM.

Submitter checklist

  • Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
  • Ensure that the pull request title represents the desired changelog entry
  • Please describe what you did
  • Link to relevant issues in GitHub or Jira
  • Link to relevant pull requests, esp. upstream and downstream changes
  • Ensure you have provided tests - that demonstrates feature works or fixes the issue

The plugin compatibility tester mistakenly uses the version of optional
plugins that is provided by the pom of the tested plugin rather than
using the version of plugin that is listed in the pom file of the plugin
bill of materials.

Because of that issue, the 2.426.x plugin bill of materials version
needs to remain on an older version in order to not include an optional
dependency on a newer version of the trilead API plugin.

3080.vfa_b_e4a_a_39b_44 is the version immediately before a trilean API
plugin upgrade in the BOM.

jenkinsci/bom#3404 has more details

jenkinsci#211 includes
some discussion as well.
@MarkEWaite MarkEWaite requested a review from a team as a code owner July 25, 2024 21:23
@@ -93,7 +93,11 @@
<dependency>
<groupId>io.jenkins.tools.bom</groupId>
<artifactId>bom-2.426.x</artifactId>
<version>3208.vb_21177d4b_cd9</version>
<!-- Last 2.426.x BOM version before a trilead api upgrade -->
<!-- Trilead API upgrade breaks plugin compatibility tests due to poor handling of optional dependencies -->
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we have an issue recorded somewhere related to this problem?

Copy link
Contributor Author

@MarkEWaite MarkEWaite Jul 25, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hehe :)

Copy link
Member

@olamy olamy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@MarkEWaite
Copy link
Contributor Author

Passed a full test of the plugin bom. Ready to merge and release.

@olamy olamy merged commit 884f71d into jenkinsci:master Jul 26, 2024
15 checks passed
@MarkEWaite MarkEWaite deleted the explore-bom-versions branch July 26, 2024 00:41
@MarkEWaite
Copy link
Contributor Author

@olamy could you label the pull request as developer so that it will generate a new release?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants