Open timja opened 6 years ago
JENKINS-51032 would enable this.
jglick The file (broken symlink) is already in the 'excludes' for the 'archiveArtifacts'. If JENKINS-51032 is a solution then we'd have to exclude the same file (pattern) twice?
[Originally depends on: JENKINS-51032]
The archiveArtifacts step appears to be fingerprinting files which should be in the excludes set, which causes build failure if the files cannot be fingerprinted. (In this case – a broken symlink).
The archiveArtifacts step should not be processing files in the excludes set beyond the required name-pattern check.
We have a multi-architecture build, and archive the build results by first stashing them for each platform, and unstashing them into platform-specific subdirectories.
Our archive step is then (originally from the Pipeline Syntax generator):
where the broken symlink is a library-name in '${env.PROJECT_HOME}/lib'.
The step results in the following exception which fails the build (although the stage is not marked as a failure?):
Note that I have tried a number of excludes patterns to try to get rid of this error – although other projects with similar structure but without the broken symlink compete successfully.
Workaround: Another step before the archive to explicitly remove the symlinks.
Originally reported by simon_watts, imported from: archiveArtifact fingerprinting excluded files