Skip to content

docs: clarify Jenkins BOM usage for Pipeline testing#8792

Open
ayushHardeniya wants to merge 2 commits intojenkins-infra:masterfrom
ayushHardeniya:docs-testing-bom-usage
Open

docs: clarify Jenkins BOM usage for Pipeline testing#8792
ayushHardeniya wants to merge 2 commits intojenkins-infra:masterfrom
ayushHardeniya:docs-testing-bom-usage

Conversation

@ayushHardeniya
Copy link
Contributor

@ayushHardeniya ayushHardeniya commented Feb 4, 2026

While reviewing the developer testing documentation, I noticed that the Pipeline testing section
references the Jenkins Bill of Materials (BOM) without explaining how it is used in practice.

This change adds a brief explanation and a concrete Maven dependencyManagement example to clarify
the recommended approach for managing test dependency versions.

@ayushHardeniya ayushHardeniya requested a review from a team as a code owner February 4, 2026 08:32
@probot-autolabeler probot-autolabeler bot added the documentation Jenkins documentation, including user and developer docs, solution pages, etc. label Feb 4, 2026
Copy link
Contributor

@MarkEWaite MarkEWaite left a comment

Choose a reason for hiding this comment

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

This seems like it is duplicating the instructions in the linked page and making a mistake while doing it.

If the link is not enough to explain the plugin bill of materials, then I think we should provide a link to the "Use the plugin BOM" section of the "Improve a plugin" tutorial.

@ayushHardeniya
Copy link
Contributor Author

ayushHardeniya commented Feb 4, 2026

Thanks for the clarification.
I’ve removed the inline BOM example and updated the section to link directly to the “Use the plugin BOM” documentation in the Improve a plugin tutorial instead, to avoid duplication and ensure correctness.

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

Labels

documentation Jenkins documentation, including user and developer docs, solution pages, etc.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants