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

Pipeline Model Definition Post Action Order

    Details

    • Similar Issues:

      Description

      The post.always action should be the last action run in a stage or pipeline. At present it will run BEFORE the post.success, aborted, and failure actions which doesn't make much sense.

      Example:

      I want to clean the workspace at the end of a stage regardless of status, and I want to archive some files on success. The logical way to achieve this is to clean the workspace in the post.always and archive the files on post.success. This is not possible in the current plugin.

       

      I know there are ways to get round this 'feature' but they are not exactly intuitive.

      Attached a simple pipeline to demonstrate the issue.

       

        Attachments

          Issue Links

            Activity

            rayalexander Ray Alexander created issue -
            rayalexander Ray Alexander made changes -
            Field Original Value New Value
            Description The post.always action should be the last action run in a stage or pipeline. At present it will run BEFORE the post.success, aborted, and failure actions which doesn't make much sense.

            *Example:*

            I want to clean the workspace at the end of a stage and I want to archive some files on success. The logical way to achieve this is to clean the workspace in the post.always and archived the files on post.success. This is not possible in the current plugin.

             

            I know there are ways to get round this 'feature' but they are not exactly intuitive.

            Attached a simple pipeline to demonstrate the issue.

             
            The post.always action should be the last action run in a stage or pipeline. At present it will run BEFORE the post.success, aborted, and failure actions which doesn't make much sense.

            *Example:*

            I want to clean the workspace at the end of a stage regardless of status, and I want to archive some files on success. The logical way to achieve this is to clean the workspace in the post.always and archive the files on post.success. This is not possible in the current plugin.

             

            I know there are ways to get round this 'feature' but they are not exactly intuitive.

            Attached a simple pipeline to demonstrate the issue.

             
            abayer Andrew Bayer made changes -
            Link This issue duplicates JENKINS-41519 [ JENKINS-41519 ]
            abayer Andrew Bayer made changes -
            Status Open [ 1 ] Resolved [ 5 ]
            Resolution Duplicate [ 3 ]
            bitwiseman Liam Newman made changes -
            Status Resolved [ 5 ] Closed [ 6 ]

              People

              • Assignee:
                abayer Andrew Bayer
                Reporter:
                rayalexander Ray Alexander
              • Votes:
                2 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: