Details
-
Improvement
-
Status: Fixed but Unreleased (View Workflow)
-
Minor
-
Resolution: Not A Defect
Description
The following pipeline does not trigger the post section:
pipeline {
agent any
stages {
stage('Test') {
when {
expression { return false; }
}
steps {
echo 'working'
}
post {
always {
echo 'post'
}
}
}
}
}
I expected this to actually echo 'post' and for post to also have a 'skipped' option. Would love to see those.
Attachments
Issue Links
- relates to
-
JENKINS-49944 support some handling for skipped stages
-
- Open
-
Activity
Omer van Kloeten
created issue -
| Field | Original Value | New Value |
|---|---|---|
| Resolution | Not A Defect [ 7 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
Omer van Kloeten
added a comment - abayer thanks for the quick reply. I did not mean this was a defect, just different than what I expected.
It could be a good idea to add something in the docs about this.
Omer van Kloeten
added a comment - abayer thanks for the quick reply. I did not mean this was a defect, just different than what I expected.
It could be a good idea to add something in the docs about this. 
Andreas Klemp
made changes -
| Link | This issue relates to JENKINS-49944 [ JENKINS-49944 ] |
I would also add, that being able to something when a stage is skipped would be useful. An example might be to update a CI reporting system (such as Github's commit status checks) that a stage is not being waited for (indefinitely) but rather has been skipped.
Could we have this This is reopened as an RFE for some such kind of functionality rather than having to re-invent when processing inside the stage since it's not possible to reflect the skipped status of a stage at that point?
Brian J Murrell
added a comment - - edited I would also add, that being able to something when a stage is skipped would be useful. An example might be to update a CI reporting system (such as Github's commit status checks) that a stage is not being waited for (indefinitely) but rather has been skipped.
Could we have this This is reopened as an RFE for some such kind of functionality rather than having to re-invent when processing inside the stage since it's not possible to reflect the skipped status of a stage at that point? Brian J Murrell
added a comment - Reopening as RFE. Brian J Murrell
made changes -
| Resolution | Not A Defect [ 7 ] | |
| Status | Resolved [ 5 ] | Reopened [ 4 ] |
Brian J Murrell
added a comment - Re-closing as I did not see the related issue JENKINS-49944 on this one.
Brian J Murrell
added a comment - Re-closing as I did not see the related issue JENKINS-49944 on this one. Brian J Murrell
made changes -
| Resolution | Not A Defect [ 7 ] | |
| Status | Reopened [ 4 ] | Fixed but Unreleased [ 10203 ] |
post on a stage is part of the stage. So if the stage is skipped due to when, that includes the post.