-
Improvement
-
Resolution: Unresolved
-
Major
-
None
The artifacts are now archived in a structure resembling default Maven2 repo layout, however the metadata is missing.
When trying to use a pipeline build artifacts as a maven repository you will:
- get [WARNING] Checksum validation failed, no checksums available because no checksum files are present
- range resolution won't work because of the missing maven-metadata.xml
What works now is: downloading a single release version of an artifact.
There is a simple workaround: use deploy goal together with file protocol URL, e.g. -DaltDeploymentRepository=file::default::file://$WORKSPACE/.m2repo
Problem is that it's tedious to add this to every build and you have to remember to archive the artifacts manually.
[JENKINS-45405] Add Maven metadata when auto-archiving artifacts
Jakub Bochenski
created issue -
Jakub Bochenski
made changes -
| Summary | Original: Add Maven when auto-archiving artifacts | New: Add Maven metadata when auto-archiving artifacts |
Jakub Bochenski
made changes -
| Description |
Original:
The artifacts are now archived in a structure resembling default Maven2 repo layout, however the metadata is missing. When trying to use a pipeline build artifacts as a maven repository you will: - get warnings {{[WARNING] Checksum validation failed, no checksums available}} because no checksum files are present - range resolution won't work because of the missing {{maven-metadata.xml}} What works now is downloading a single release version of an artifact. There is a simple workaround: use {{deploy}} goal together with file protocol URL, e.g. {{-DaltDeploymentRepository=file::default::file://$WORKSPACE/.m2repo}} Problem is that it's tedious to add this to every build and you have to remember to archive the artifacts manually. |
New:
The artifacts are now archived in a structure resembling default Maven2 repo layout, however the metadata is missing. When trying to use a pipeline build artifacts as a maven repository you will: - get {{[WARNING] Checksum validation failed, no checksums available}} because no checksum files are present - range resolution won't work because of the missing {{maven-metadata.xml}} What works now is: downloading a single release version of an artifact. There is a simple workaround: use {{deploy}} goal together with file protocol URL, e.g. {{-DaltDeploymentRepository=file::default::file://$WORKSPACE/.m2repo}} Problem is that it's tedious to add this to every build and you have to remember to archive the artifacts manually. |
| Assignee | Original: Alvaro Lobato [ alobato ] |