Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-46180

archive step does not fail on missing/invalid file patterns

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • pipeline
    • 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

          [JENKINS-46180] archive step does not fail on missing/invalid file patterns

          R. Tyler Croy created issue -
          R. Tyler Croy made changes -
          Link New: This issue relates to JENKINS-38005 [ JENKINS-38005 ]
          Andrew Bayer made changes -
          Assignee New: Andrew Bayer [ abayer ]
          Andrew Bayer made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

          Andrew Bayer added a comment -

          So a legit question here - in JENKINS-31931, we decided to silently shrug and move on from missing/invalid file patterns and not fail the build. i.e., this is actually a deliberate choice. I'm wishy-washy as to whether we should change that.

          Andrew Bayer added a comment - So a legit question here - in JENKINS-31931 , we decided to silently shrug and move on from missing/invalid file patterns and not fail the build. i.e., this is actually a deliberate choice. I'm wishy-washy as to whether we should change that.
          Andrew Bayer made changes -
          Link New: This issue relates to JENKINS-31931 [ JENKINS-31931 ]

          R. Tyler Croy added a comment -

          We don't necessarily have to fail the build, but to provide the user with zero feedback that their expectations are not being met, is not okay IMHO.

          R. Tyler Croy added a comment - We don't necessarily have to fail the build, but to provide the user with zero feedback that their expectations are not being met, is not okay IMHO.
          Liam Newman made changes -
          Link New: This issue relates to JENKINS-45200 [ JENKINS-45200 ]
          James Dumay made changes -
          Sprint New: Pipeline - December [ 446 ]
          James Dumay made changes -
          Rank New: Ranked lower

            abayer Andrew Bayer
            rtyler R. Tyler Croy
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: