"Commit status build result" uses wrong context

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major
    • Component/s: ghprb-plugin
    • None
    • Environment:
      Jenkins 1.649, GHPRB plugin 1.30.4

      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.

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

              Created:
              Updated: