Details
-
New Feature
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
Description
Currently there is no easy way to use pipeline in unit tests.
You need to add all of the required deps and exclude lots of conflicting versions of dependencies.
It would be nice if I could just add a dependency on the aggregator with scope test and be done with it - but this also is not possible due to upper-bounds conflicts.
Attachments
Issue Links
- blocks
-
JENKINS-51008 Complete the PCT flow started in JENKINS-50540 for git plugin
-
- In Progress
-
- depends on
-
JENKINS-58716 Failure to check out specified tag for incremental version
-
- Resolved
-
- is blocked by
-
-
- Resolved
-
- is duplicated by
-
JENKINS-33268 plugin-pom and core/war should produce/consume a BOM
-
- Resolved
-
- is related to
-
-
- Resolved
-
- relates to
-
-
- Open
-
-
-
- In Progress
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Closed
-
- links to
Activity
| Field | Original Value | New Value |
|---|---|---|
| Resolution | Not A Defect [ 7 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
Converting to a more general RFE that the Jenkins project should publish a BOM somewhere you could import which specifies consistent versions of all plugins listed (incl. transitive dependencies) in the setup wizard’s suggested list; to be refreshed at least with every LTS line (versioned accordingly), and perhaps more often, taking latest versions from the update center.
| Component/s | plugin-pom [ 21982 ] | |
| Component/s | workflow-aggregator-plugin [ 21710 ] | |
| Component/s | workflow-basic-steps-plugin [ 21712 ] | |
| Component/s | workflow-cps-plugin [ 21713 ] | |
| Component/s | workflow-job-plugin [ 21716 ] | |
| Issue Type | Task [ 3 ] | New Feature [ 2 ] |
| Priority | Minor [ 4 ] | Major [ 3 ] |
| Summary | should be an easy way to use pipeline in unit tests | Easy way to select compatible plugin versions for test scope |
| Resolution | Not A Defect [ 7 ] | |
| Status | Resolved [ 5 ] | Reopened [ 4 ] |
| Status | Reopened [ 4 ] | Open [ 1 ] |
| Remote Link | This issue links to "CloudBees Internal CJP-7862 (Web Link)" [ 18952 ] |
| Summary | Easy way to select compatible plugin versions for test scope | Select compatible plugin versions using a BOM |
After getting some experience with the effect of a BOM on plugin POMs, I am becoming more convinced that this is the right direction. For example, common POM maintenance can be performed by adding entries to dependencyManagement, but just using a newer parent would be a lot simpler.
| Link | This issue relates to JENKINS-45047 [ JENKINS-45047 ] |
| Link |
This issue is duplicated by |
| Link |
This issue is duplicated by |
| Remote Link | This issue links to "pom-manipulation-ext (Web Link)" [ 19402 ] |
| Link |
This issue is related to |
| Link |
This issue is duplicated by |
jglick, could you expand on why you're suggesting that? None of the work that I'm doing at the moment is around test infrastructure for plugins/core per se (ATH work excepted), and is mostly geared around delivering the Jenkins Essentials image.
I can see a tenuous link here, but I'm not sure I fully understand why this suggests Jenkins Essentials prioritization right now
?
| Labels | essentials |
| Link |
This issue relates to |
| Link | This issue blocks JENKINS-51008 [ JENKINS-51008 ] |
| Epic Link |
|
Added to JENKINS-50686 since we might be able to use JENKINS-50953 to update the contents of the BOM.
| Link |
This issue relates to |
| Labels | essentials | essentials evergreen |
| Labels | essentials evergreen | evergreen |
| Assignee | Jesse Glick [ jglick ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Remote Link | This issue links to "prototype repo (Web Link)" [ 23218 ] |
| Link | This issue is blocked by HOSTING-800 [ HOSTING-800 ] |
| Remote Link | This issue links to "prototype repo (Web Link)" [ 23218 ] |
| Remote Link | This issue links to "jenkinsci/bom repo (Web Link)" [ 23223 ] |
| Component/s | bom [ 25623 ] | |
| Component/s | plugin-pom [ 21982 ] |
| Link |
This issue relates to |
| Link | This issue is blocked by INFRA-2183 [ INFRA-2183 ] |
| Link |
This issue is blocked by |
| Link | This issue relates to JENKINS-49651 [ JENKINS-49651 ] |
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Resolved [ 5 ] |
| Link |
This issue depends on |
Add latest (baseline-compatible) versions of those plugins you are actually using in the test.
Do not use exclusions. Just declare test-scoped dependencies on any otherwise transitive dependencies that requireUpperBoundDeps complains about.