[JIRA] (JENKINS-54157) Unstable builds are marked as FAILED in Bitbucket
Title: Message Title Adrian Wyssmann commented on JENKINS-54157 Re: Unstable builds are marked as FAILED in Bitbucket I've implemented the change, PR is pending: https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/148 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54157) Unstable builds are marked as FAILED in Bitbucket
Title: Message Title Adrian Wyssmann updated an issue Jenkins / JENKINS-54157 Unstable builds are marked as FAILED in Bitbucket Change By: Adrian Wyssmann Currently unstable builds in Jenkins are marked as failed in Bitbucket and I don't see a way how to configure it differently [https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/8c2c20f4443c11798a032a9f03523c73befd6296/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/BitbucketBuildStatusNotifications.java#L119] !https://user-images.githubusercontent.com/15034009/47202372-364a1e80-d37d-11e8-9436-8918dde5af5d.png!There may be reasons why an unstable build still may be considered as "successful" in Bitbucket, even so the Jenkins build is unstable - i.e. you have a threshold set which allows certain tests to be failing but still consider the Jenkins test as not failed. The plugin should respect that.As such builds are considered failed, the code cannot be merged if the merge checks are available.The best solution would be to have a parameter "[ ] consider UNSTABLE builds as SUCCESS" where you can define the behavior - per team folder- jenkins wide Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email
[JIRA] (JENKINS-54157) Unstable builds are marked as FAILED in Bitbucket
Title: Message Title Adrian Wyssmann updated an issue Jenkins / JENKINS-54157 Unstable builds are marked as FAILED in Bitbucket Change By: Adrian Wyssmann Currently unstable builds in Jenkins are marked as failed in Bitbucket and I don't see a way how to configure it differently!https://user-images.githubusercontent.com/15034009/47202372-364a1e80-d37d-11e8-9436-8918dde5af5d.png! There may be reasons why an unstable build still may be considered as "successful" in Bitbucket, even so the Jenkins build is unstable - i.e. you have a threshold set which allows certain tests to be failing but still consider the Jenkins test as not failed. The plugin should respect that.As such builds are considered failed, the code cannot be merged if the merge checks are available.The best solution would be to have a parameter "[ ] consider UNSTABLE builds as SUCCESS" where you can define the behavior- per team folder- jenkins wide Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54157) Unstable builds are marked as FAILED in Bitbucket
Title: Message Title Adrian Wyssmann created an issue Jenkins / JENKINS-54157 Unstable builds are marked as FAILED in Bitbucket Issue Type: Bug Assignee: Unassigned Components: bitbucket-branch-source-plugin Created: 2018-10-19 07:04 Environment: - Jenkins 2.138.1 - Bitbucket Branch Source Plugin 2.2.12 - Bitbucket Server 5.9.0 Priority: Minor Reporter: Adrian Wyssmann Currently unstable builds in Jenkins are marked as failed in Bitbucket and I don't see a way how to configure it differently Add Comment
