-
Bug
-
Resolution: Not A Defect
-
Minor
-
None
Support for unstable is in my opinion really important. In our situation a build job should be indicated unstable when any warnings, e.g. inspect warnings from resharper, are introduced. As a developer I would like to be notified with a yellow unstable marker if I introduced any into the system.
When checking the console log I see the following information:
// code placeholder [Pipeline] stage [Pipeline]{ (Declarative: Post Actions) [Pipeline] echo UNSTABLE [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline Posting build status of SUCCESSFUL to Jenkins2 InstanceFinished: UNSTABLE
However in Bitbucket Server I see a green successful indicating the build is OK.
Environment:
- Atlassian Bitbucket v6.10.2
- [Jenkins 2.236
Multibranch Pipeline|http://eyeonair.nl/] - Bitbucket Server Integration 1.1.0
[JENKINS-62915] Support for build status unstable
| Description | Original: Support for unstable is in my opinion really important. In our situation a build job should be indicated unstable when any warnings, e.g. inspect warnings from resharper, are introduced. As a developer I would like to be notified with a yellow unstable marker if I introduced any into the system. |
New:
Support for unstable is in my opinion really important. In our situation a build job should be indicated unstable when any warnings, e.g. inspect warnings from resharper, are introduced. As a developer I would like to be notified with a yellow unstable marker if I introduced any into the system. When checking the console log I see the following information: [Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] echoUNSTABLE[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // node[Pipeline] End of PipelinePosting build status of SUCCESSFUL to Jenkins2 InstanceFinished: UNSTABLE However in Bitbucket Server I see a green successful indicating the build is OK. |
| Description |
Original:
Support for unstable is in my opinion really important. In our situation a build job should be indicated unstable when any warnings, e.g. inspect warnings from resharper, are introduced. As a developer I would like to be notified with a yellow unstable marker if I introduced any into the system. When checking the console log I see the following information: [Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] echoUNSTABLE[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // node[Pipeline] End of PipelinePosting build status of SUCCESSFUL to Jenkins2 InstanceFinished: UNSTABLE However in Bitbucket Server I see a green successful indicating the build is OK. |
New:
Support for unstable is in my opinion really important. In our situation a build job should be indicated unstable when any warnings, e.g. inspect warnings from resharper, are introduced. As a developer I would like to be notified with a yellow unstable marker if I introduced any into the system. When checking the console log I see the following information: {code:java} // code placeholder [Pipeline] stage [Pipeline]{ (Declarative: Post Actions) [Pipeline] echo UNSTABLE [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline Posting build status of SUCCESSFUL to Jenkins2 InstanceFinished: UNSTABLE {code} However in Bitbucket Server I see a green successful indicating the build is OK. |
| Description |
Original:
Support for unstable is in my opinion really important. In our situation a build job should be indicated unstable when any warnings, e.g. inspect warnings from resharper, are introduced. As a developer I would like to be notified with a yellow unstable marker if I introduced any into the system. When checking the console log I see the following information: {code:java} // code placeholder [Pipeline] stage [Pipeline]{ (Declarative: Post Actions) [Pipeline] echo UNSTABLE [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline Posting build status of SUCCESSFUL to Jenkins2 InstanceFinished: UNSTABLE {code} However in Bitbucket Server I see a green successful indicating the build is OK. |
New:
Support for unstable is in my opinion really important. In our situation a build job should be indicated unstable when any warnings, e.g. inspect warnings from resharper, are introduced. As a developer I would like to be notified with a yellow unstable marker if I introduced any into the system. When checking the console log I see the following information: {code:java} // code placeholder [Pipeline] stage [Pipeline]{ (Declarative: Post Actions) [Pipeline] echo UNSTABLE [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline Posting build status of SUCCESSFUL to Jenkins2 InstanceFinished: UNSTABLE {code} However in Bitbucket Server I see a green successful indicating the build is OK. Environment: * Atlassian Bitbucket v6.10.2 * [Jenkins 2.236|http://eyeonair.nl/] * [Bitbucket Server Integration|https://plugins.jenkins.io/atlassian-bitbucket-server-integration] 1.1.0 |
| Description |
Original:
Support for unstable is in my opinion really important. In our situation a build job should be indicated unstable when any warnings, e.g. inspect warnings from resharper, are introduced. As a developer I would like to be notified with a yellow unstable marker if I introduced any into the system. When checking the console log I see the following information: {code:java} // code placeholder [Pipeline] stage [Pipeline]{ (Declarative: Post Actions) [Pipeline] echo UNSTABLE [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline Posting build status of SUCCESSFUL to Jenkins2 InstanceFinished: UNSTABLE {code} However in Bitbucket Server I see a green successful indicating the build is OK. Environment: * Atlassian Bitbucket v6.10.2 * [Jenkins 2.236|http://eyeonair.nl/] * [Bitbucket Server Integration|https://plugins.jenkins.io/atlassian-bitbucket-server-integration] 1.1.0 |
New:
Support for unstable is in my opinion really important. In our situation a build job should be indicated unstable when any warnings, e.g. inspect warnings from resharper, are introduced. As a developer I would like to be notified with a yellow unstable marker if I introduced any into the system. When checking the console log I see the following information: {code:java} // code placeholder [Pipeline] stage [Pipeline]{ (Declarative: Post Actions) [Pipeline] echo UNSTABLE [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline Posting build status of SUCCESSFUL to Jenkins2 InstanceFinished: UNSTABLE {code} However in Bitbucket Server I see a green successful indicating the build is OK. Environment: * Atlassian Bitbucket v6.10.2 * [Jenkins 2.236 Multibranch Pipeline|http://eyeonair.nl/] * [Bitbucket Server Integration|https://plugins.jenkins.io/atlassian-bitbucket-server-integration] 1.1.0 |
| Assignee | Original: Kristy Hughes [ khughes ] |
| Resolution | New: Not A Defect [ 7 ] | |
| Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Hi Frank, thanks for your report.
The behaviour you are describing is working as intended- unstable is not a build type in Bitbucket Server, so we translate unstable warnings as green builds. The change to support "unstable" builds in Bitbucket Server is not currently on our roadmap, and we don't feel it is likely to occur in the near future, so I am going to CWD this ticket for now.