archive step does not fail on missing/invalid file patterns

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • 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

            Assignee:
            Andrew Bayer
            Reporter:
            R. Tyler Croy
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: