We use several multibranch jobs for one repository. And the statuses of PR in github from different jobs are mixed. The context for github status hardcoded and can't be changed. It would be very convinient keep job name in context string.

          [JENKINS-46119] Use the job name in context string

          Yo-An Lin added a comment -

          Do not do this. There was an issue specifically requesting that the context string not include details like a job name, and that was fixed. The reason is that GitHub has features whereby you can control various workflows by specifying approved status context strings, and they need to be an exact match.

          quote from a comment of the closed PR.

          Yo-An Lin added a comment - Do not do this. There was an issue specifically requesting that the context string not include details like a job name, and that was fixed. The reason is that GitHub has features whereby you can control various workflows by specifying approved status context strings, and they need to be an exact match. quote from a comment of the closed PR.

          Yo-An Lin added a comment -

          jglick how about using pipeline property to define the context ? so that users can customize the context from their own pipeline script

          Yo-An Lin added a comment - jglick how about using pipeline property to define the context ? so that users can customize the context from their own pipeline script

          Viacheslav Dubrovskyi added a comment - IMHO the issue can be closed, because it's possible to set context with https://github.com/steven-foster/github-scm-trait-notification-context How to use it look to  https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/jenkinsci-users/uS8qhyDLDWs/5KKSN1uTBwAJ

          And where will this be documented? Why is the resolution not to roll this override functionality into the plugin? Do we expect that people who run afoul of this will locate this bug, and hopefully that repo and google group will be accessible to them?

          Robert Rodrigues added a comment - And where will this be documented? Why is the resolution not to roll this override functionality into the plugin? Do we expect that people who run afoul of this will locate this bug, and hopefully that repo and google group will be accessible to them?

          Note that the url in the pom.xml does not resolve.
          https://wiki.jenkins-ci.org/display/JENKINS/Github+Custom+Notification+Context+SCM+Behaviour

          However, further searching found this: https://plugins.jenkins.io/github-scm-trait-notification-context

          So, is installing that plugin the correct way to resolve this?

          Robert Rodrigues added a comment - Note that the url in the pom.xml does not resolve. https://wiki.jenkins-ci.org/display/JENKINS/Github+Custom+Notification+Context+SCM+Behaviour However, further searching found this: https://plugins.jenkins.io/github-scm-trait-notification-context So, is installing that plugin the correct way to resolve this?

          Yo-An Lin added a comment -

          dubrsl why is this closed? I don't think this issue should be resolved by installing a plugin. the context customization feature should be self-contained since IT IS THE GitHub Source Plugin.

          Yo-An Lin added a comment - dubrsl why is this closed? I don't think this issue should be resolved by installing a plugin. the context customization feature should be self-contained since IT IS THE GitHub Source Plugin.

          c9s I made this issue because there was no solution. Now solution exist. So I decided to close it. Feel free to reopen it.

          Viacheslav Dubrovskyi added a comment - c9s  I made this issue because there was no solution. Now solution exist. So I decided to close it. Feel free to reopen it.

          Fabian Holler added a comment -

          Reopening the issue, it's not fixed,
          the Github Source plugin should support to customize the context string

          Fabian Holler added a comment - Reopening the issue, it's not fixed, the Github Source plugin should support to customize the context string

          Yo-An Lin added a comment -

          Yo-An Lin added a comment - I sent a PR for the property support https://github.com/jenkinsci/github-branch-source-plugin/pull/206

          Liam Newman added a comment -

          Liam Newman added a comment - Turns out this is implemented here: https://github.com/jenkinsci/github-scm-trait-notification-context-plugin

            Unassigned Unassigned
            dubrsl Viacheslav Dubrovskyi
            Votes:
            5 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: