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

"Commit status build result" uses wrong context

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • ghprb-plugin
    • None
    • Jenkins 1.649, GHPRB plugin 1.30.4

    Description

      When setting up a custom Commit Status Context, the custom Commit Status Build Result messages are not respecting it, and post to GitHub as "default".

      That results in GitHub thinking there are 2 separate build processes, and one remains in "pending" state.

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          davidtanner David Tanner added a comment -

          Make sure that the context is being set as part of the trigger, and not as a build step, either pre or post.

          davidtanner David Tanner added a comment - Make sure that the context is being set as part of the trigger, and not as a build step, either pre or post.
          sabbasth Bastien Semene added a comment -

          IMHO this is not actually a trivial bug.

          If you use protected branches and filter mandatory checks by context this is a real pain.

          sabbasth Bastien Semene added a comment - IMHO this is not actually a trivial bug. If you use protected branches and filter mandatory checks by context this is a real pain.
          gtirloni Giovanni Tirloni added a comment -

          Jenkins 2.46.2 / GHPRB 1.36.2

          Commit Status Context set to "Jenkins" causes duplicated context.

          gtirloni Giovanni Tirloni added a comment - Jenkins 2.46.2 / GHPRB 1.36.2 Commit Status Context set to "Jenkins" causes duplicated context.

          People

            Unassigned Unassigned
            giuseppeiannello Giuseppe Iannello
            Votes:
            3 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated: