-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
-
Pipeline - December
I know the archive step is deprecated, but many users still use it, and are frustrated when it doesn't fail appropriately on user errors. (I can point somebody at CloudBees to some internal support tickets if they need more convincing )
node {
archive 'nonexistent.txt'
}
Results in no failure, warning, just a silent success:
Started by user admin [Pipeline] node Running on master in /var/jenkins_home/workspace/vlad-the-archiver [Pipeline] { [Pipeline] archive [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline Finished: SUCCESS
- relates to
-
JENKINS-31931 archive step sets result to FAILURE but does not fail the job
- Resolved
-
JENKINS-38005 Using archiveArtifacts with a non-matching pattern silently fails the build
- Resolved
-
JENKINS-45200 Archiving artifacts fails, but build step is shown with a green dot
- Resolved
- links to