-
Bug
-
Resolution: Unresolved
-
Critical
-
None
If(in declarative mode && last stages are parallel && you have a post{} pipeline block) {
you don't see any of the post-build output, it's missing
}
Suggestion:
Good DX would be; if in declarative mode, and you have defined a post{} pipeline block, then to create a stage named Post Build or something. It's consistent, predictable, very clear and clickable.
[JENKINS-50449] Post build steps appear in previous stage's steps
Description |
Original:
pipeline { agent { label '!master' } // run on slaves only stages { stage('Some stage') { steps { echo 'SOME MAIN STAGE' } } stage('Some stage 2') { steps { echo 'SOME MAIN STAGE' } } stage('Some stage 3') { steps { echo 'SOME MAIN STAGE' } } } post { always { script { echo "THIS IS POST TRIGGER STAGE" } } success { script { echo "THIS IS SUCCESS" } } } } |
New:
{code} pipeline { agent { label '!master' } // run on slaves only stages { stage('Some stage') { steps { echo 'SOME MAIN STAGE' } } stage('Some stage 2') { steps { echo 'SOME MAIN STAGE' } } stage('Some stage 3') { steps { echo 'SOME MAIN STAGE' } } } post { always { script { echo "THIS IS POST TRIGGER STAGE" } } success { script { echo "THIS IS SUCCESS" } } } } {code} |
Description |
Original:
{code} pipeline { agent { label '!master' } // run on slaves only stages { stage('Some stage') { steps { echo 'SOME MAIN STAGE' } } stage('Some stage 2') { steps { echo 'SOME MAIN STAGE' } } stage('Some stage 3') { steps { echo 'SOME MAIN STAGE' } } } post { always { script { echo "THIS IS POST TRIGGER STAGE" } } success { script { echo "THIS IS SUCCESS" } } } } {code} |
New:
As per the screenshot below, the pipeline's post{} section isn't visible, you have to find one of the stages in the main pipeline and see some steps appended onto it. This is confusing DX As per classic Jenkins, there's a section rendered `Declarative: Post Actions` and you can drill down into there. I am expecting to see a section on BO with the same. What's the intent behind this ? {code} pipeline { agent { label '!master' } // run on slaves only stages { stage('Some stage') { steps { echo 'SOME MAIN STAGE' } } stage('Some stage 2') { steps { echo 'SOME MAIN STAGE' } } stage('Some stage 3') { steps { echo 'SOME MAIN STAGE' } } } post { always { script { echo "THIS IS POST TRIGGER STAGE" } } success { script { echo "THIS IS SUCCESS" } } } } {code} |
Description |
Original:
As per the screenshot below, the pipeline's post{} section isn't visible, you have to find one of the stages in the main pipeline and see some steps appended onto it. This is confusing DX As per classic Jenkins, there's a section rendered `Declarative: Post Actions` and you can drill down into there. I am expecting to see a section on BO with the same. What's the intent behind this ? {code} pipeline { agent { label '!master' } // run on slaves only stages { stage('Some stage') { steps { echo 'SOME MAIN STAGE' } } stage('Some stage 2') { steps { echo 'SOME MAIN STAGE' } } stage('Some stage 3') { steps { echo 'SOME MAIN STAGE' } } } post { always { script { echo "THIS IS POST TRIGGER STAGE" } } success { script { echo "THIS IS SUCCESS" } } } } {code} |
New:
As per the screenshot below, the pipeline's post{} section isn't visible, you have to find one of the stages in the main pipeline and see some steps appended onto it. This is confusing DX As per classic Jenkins, there's a section rendered `Declarative: Post Actions` and you can drill down into there. I am expecting to see a section on BO with the same. PS: I never seen the `success` output only the always{} output What's the intent behind this ? {code} pipeline { agent { label '!master' } // run on slaves only stages { stage('Some stage') { steps { echo 'SOME MAIN STAGE' } } stage('Some stage 2') { steps { echo 'SOME MAIN STAGE' } } stage('Some stage 3') { steps { echo 'SOME MAIN STAGE' } } } post { always { script { echo "THIS IS POST TRIGGER STAGE" } } success { script { echo "THIS IS SUCCESS" } } } } {code} |
Description |
Original:
As per the screenshot below, the pipeline's post{} section isn't visible, you have to find one of the stages in the main pipeline and see some steps appended onto it. This is confusing DX As per classic Jenkins, there's a section rendered `Declarative: Post Actions` and you can drill down into there. I am expecting to see a section on BO with the same. PS: I never seen the `success` output only the always{} output What's the intent behind this ? {code} pipeline { agent { label '!master' } // run on slaves only stages { stage('Some stage') { steps { echo 'SOME MAIN STAGE' } } stage('Some stage 2') { steps { echo 'SOME MAIN STAGE' } } stage('Some stage 3') { steps { echo 'SOME MAIN STAGE' } } } post { always { script { echo "THIS IS POST TRIGGER STAGE" } } success { script { echo "THIS IS SUCCESS" } } } } {code} |
New:
As per the screenshot below, the pipeline's post{} section isn't visible, you have to find one of the stages in the main pipeline and see some steps appended onto it. This is confusing DX As per classic Jenkins, there's a section rendered `Declarative: Post Actions` and you can drill down into there. I am expecting to see a section on BO with the same. What's the intent behind this ? {code} pipeline { agent { label '!master' } // run on slaves only stages { stage('Some stage') { steps { echo 'SOME MAIN STAGE' } } stage('Some stage 2') { steps { echo 'SOME MAIN STAGE' } } stage('Some stage 3') { steps { echo 'SOME MAIN STAGE' } } } post { always { script { echo "THIS IS POST TRIGGER STAGE" } } success { script { echo "THIS IS SUCCESS" } } } } {code} |
Issue Type | Original: Improvement [ 4 ] | New: Bug [ 1 ] |
Priority | Original: Major [ 3 ] | New: Critical [ 2 ] |
Description |
Original:
As per the screenshot below, the pipeline's post{} section isn't visible, you have to find one of the stages in the main pipeline and see some steps appended onto it. This is confusing DX As per classic Jenkins, there's a section rendered `Declarative: Post Actions` and you can drill down into there. I am expecting to see a section on BO with the same. What's the intent behind this ? {code} pipeline { agent { label '!master' } // run on slaves only stages { stage('Some stage') { steps { echo 'SOME MAIN STAGE' } } stage('Some stage 2') { steps { echo 'SOME MAIN STAGE' } } stage('Some stage 3') { steps { echo 'SOME MAIN STAGE' } } } post { always { script { echo "THIS IS POST TRIGGER STAGE" } } success { script { echo "THIS IS SUCCESS" } } } } {code} |
New:
If(in declarative mode && last stages are parallel && you have a post{} pipeline block) { you don't see any of the post-build output, it's missing } Suggestion: Good DX would be; if in declarative mode, and you have defined a post{} pipeline block, then to create a stage named Post Build or something. It's consistent, predictable, very clear and clickable. |
Attachment | Original: Screen Shot 2018-03-28 at 11.21.48.png [ 41996 ] |
coervivek sophistifunk are you the best guys to talk to about this ?