• Type: Bug
• Resolution: Not A Defect
• Priority: Major
• Component/s: claim-plugin
• Labels:

  • claim

[JENKINS-54718] Claim plugin does not allow to claim unstable builds with declarative pipeline

Christoph Amshoff created issue - 2018-11-20 08:48

Christoph Amshoff made changes - 2018-11-20 08:50

Description

Original: We're not able to claim unstable builds any more (with declarative pipeline). For failed builds, it still works. I'm pretty sure it worked for unstable builds as well so I guess this is a regression. The plugin is called in post section, independant of build result: {{ post {}} {{  always {}} {{    step([$class: 'ClaimPublisher'])}} {{  }}} {{ }}} We're currently using:  * Jenkins 2.138.3  * Claim Plugin 2.15

New: We're not able to claim unstable builds any more (with declarative pipeline). For failed builds, it still works. I'm pretty sure it worked for unstable builds as well so I guess this is a regression. The plugin is called in post section, independant of build result: {{post {}} {{  {{always {}}}} {{ {{   step([$class: 'ClaimPublisher'])}}}} {{  }}} {{}}} We're currently using:  * Jenkins 2.138.3  * Claim Plugin 2.15

Christoph Amshoff made changes - 2018-11-20 08:50

Description

Original: We're not able to claim unstable builds any more (with declarative pipeline). For failed builds, it still works. I'm pretty sure it worked for unstable builds as well so I guess this is a regression. The plugin is called in post section, independant of build result: {{post {}} {{  {{always {}}}} {{ {{   step([$class: 'ClaimPublisher'])}}}} {{  }}} {{}}} We're currently using:  * Jenkins 2.138.3  * Claim Plugin 2.15

New: We're not able to claim unstable builds any more (with declarative pipeline). For failed builds, it still works. I'm pretty sure it worked for unstable builds as well so I guess this is a regression. The plugin is called in post section, independant of build result: {quote}post {     always {         step([$class: 'ClaimPublisher'])     }  } {quote} We're currently using:  * Jenkins 2.138.3  * Claim Plugin 2.15

Christoph Amshoff made changes - 2018-11-20 08:51

Description

Original: We're not able to claim unstable builds any more (with declarative pipeline). For failed builds, it still works. I'm pretty sure it worked for unstable builds as well so I guess this is a regression. The plugin is called in post section, independant of build result: {quote}post {     always {         step([$class: 'ClaimPublisher'])     }  } {quote} We're currently using:  * Jenkins 2.138.3  * Claim Plugin 2.15

New: We're not able to claim unstable builds any more (with declarative pipeline). For failed builds, it still works. I'm pretty sure it worked for unstable builds as well so I guess this is a regression. The plugin is called in post section, independant of build result:     We're currently using:  * Jenkins 2.138.3  * Claim Plugin 2.15

Christoph Amshoff made changes - 2018-11-20 08:52

Description

Original: We're not able to claim unstable builds any more (with declarative pipeline). For failed builds, it still works. I'm pretty sure it worked for unstable builds as well so I guess this is a regression. The plugin is called in post section, independant of build result:     We're currently using:  * Jenkins 2.138.3  * Claim Plugin 2.15

New: We're not able to claim unstable builds any more (with declarative pipeline). For failed builds, it still works. I'm pretty sure it worked for unstable builds as well so I guess this is a regression. The plugin is called in post section, independant of build result: {code:java} post {   always {     step([$class: 'ClaimPublisher'])   } } {code}  We're currently using:  * Jenkins 2.138.3  * Claim Plugin 2.15

Collapse comment: Christoph Amshoff added a comment - 2018-11-20 16:12

Christoph Amshoff added a comment - 2018-11-20 16:12

This issue was caused by another issue of the pipeline-maven-plugin version 3.5.15, which does not set the build status correctly (to UNSTABLE) when tests are failing (see JENKINS-54559).

Expand comment: Christoph Amshoff added a comment - 2018-11-20 16:12

Christoph Amshoff added a comment - 2018-11-20 16:12 This issue was caused by another issue of the pipeline-maven-plugin version 3.5.15, which does not set the build status correctly (to UNSTABLE) when tests are failing (see JENKINS-54559 ).

Christoph Amshoff made changes - 2018-11-20 16:12

Link

New: This issue duplicates JENKINS-54559 [ JENKINS-54559 ]

Christoph Amshoff made changes - 2018-11-20 16:12

Resolution		New: Not A Defect [ 7 ]
Status	Original: Open [ 1 ]	New: Closed [ 6 ]