Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-35453

Allow disabling the default commit status notifier

XMLWordPrintable

      In JENKINS-33151, giving users the option to disable the default commit status notifier was raised (in lieu of more complex configuration, such as the ability to change the context string, which is hard-coded to 'Jenkins': https://github.com/jenkinsci/github-branch-source-plugin/blob/master@%7B2016-06-08%7D/src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubBuildStatusNotification.java#L78)

      I think there's probably a use case for this, and it would allow users with more complicated status logic (such as in that ticket) to implement their own, and just opt out of the default one.

          [JENKINS-35453] Allow disabling the default commit status notifier

          Dominic Scheirlinck created issue -
          Jesse Glick made changes -
          Link New: This issue is related to JENKINS-33151 [ JENKINS-33151 ]

          Jesse Glick added a comment -

          Cf. comment in JENKINS-26522.

          Jesse Glick added a comment - Cf. comment in JENKINS-26522 .
          Jesse Glick made changes -
          Link New: This issue is related to JENKINS-26522 [ JENKINS-26522 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 171750 ] New: JNJira + In-Review [ 184452 ]
          Dominic Scheirlinck made changes -
          Link New: This issue is related to JENKINS-36574 [ JENKINS-36574 ]

          Alex Ehlke added a comment -

          Just to chime in with one use case: we're incrementally rolling out Jenkinsfile for CI, and so we'd prefer to disable the commit status update while we're still prototyping. We want to be able to have Jenkinsfile run in parallel with our existing CI to build all branches, to test it at scale, but since it's still unproven for us we wouldn't want any issues to result in GitHub pull requests being marked as failed as we roll it out.

          We have workarounds, just wanted to provide one use case since you seemed uncertain about the value of this.

          Alex Ehlke added a comment - Just to chime in with one use case: we're incrementally rolling out Jenkinsfile for CI, and so we'd prefer to disable the commit status update while we're still prototyping. We want to be able to have Jenkinsfile run in parallel with our existing CI to build all branches, to test it at scale, but since it's still unproven for us we wouldn't want any issues to result in GitHub pull requests being marked as failed as we roll it out. We have workarounds, just wanted to provide one use case since you seemed uncertain about the value of this.

          Mike Robinson added a comment -

          In my case, I want to send a multiple github statuses, with context equal to the pipeline stage, so we can use protected branches, but only lock out failing lint and unit testing stages, not our experimental stages or deploy stages.

          I believe this would be a helpful for that sort of workflow.

          Mike Robinson added a comment - In my case, I want to send a multiple github statuses, with context equal to the pipeline stage, so we can use protected branches, but only lock out failing lint and unit testing stages, not our experimental stages or deploy stages. I believe this would be a helpful for that sort of workflow.

          Dmytro Baikov added a comment -

          +1 This feature would be very useful for us!

          We also have a need to send customized notifications to github with different context depending on the current build stage.

          Dmytro Baikov added a comment - +1 This feature would be very useful for us! We also have a need to send customized notifications to github with different context depending on the current build stage.
          Jesse Glick made changes -
          Remote Link New: This issue links to "PR 110 (Web Link)" [ 15451 ]

            vlatombe Vincent Latombe
            dominics Dominic Scheirlinck
            Votes:
            13 Vote for this issue
            Watchers:
            28 Start watching this issue

              Created:
              Updated:
              Resolved: