-
Bug
-
Resolution: Fixed
-
Blocker
-
None
When I run PCT for a plugin with old Pipeline plugin dependency (e.g. job-restrictions plugin), I hit the following issue:
[ERROR] Failed to execute goal on project job-restrictions: Could not resolve dependencies for project com.synopsys.arc.jenkinsci.plugins:job-restrictions:hpi:0.6: The following artifacts could not be resolved: org.jenkins-ci.plugins:workflow-step-api:jar:2.14, org.jenkins-ci.plugins:workflow-api:jar:2.24: Could not find artifact org.jenkins-ci.plugins:workflow-step-api:jar:2.14 in repo.jenkins-ci.org (https://repo.jenkins-ci.org/public/) -> [Help 1]
It happens, because the group ID has been changed to "org.jenkins-ci.plugins.workflow". PCT should be ideally able to handle it somehow.
Steps to reproduce:
1. Run docker run --rm -v maven-repo:/root/.m2 -v $(pwd)/out:/pct/out -e ARTIFACT_ID=job-restrictions -e VERSION=job-restrictions-0.6 -i jenkins/pct
2. Wait
[JENKINS-48742] PCT does not handle custom plugin groupIds when pulling plugin data from UC
| Epic Link |
New:
|
| Assignee | Original: Frédéric Camblor [ fcamblor ] |
| Assignee | New: Oleg Nenashev [ oleg_nenashev ] |
| Priority | Original: Minor [ 4 ] | New: Blocker [ 1 ] |
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
| Remote Link | New: This issue links to "https://github.com/jenkinsci/plugin-compat-tester/pull/58 (Web Link)" [ 19700 ] |
| Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
| Summary | Original: PCT does not handle groupId changes in plugins | New: PCT does not handle custom plugin groupIds when pulling plugin data from UC |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Review [ 10005 ] | New: Resolved [ 5 ] |