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

"Do not update commit status" doesn't work

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • ghprb-plugin
    • None
    • Jenkins 1.651.3
      ghprb 1.33.0

    Description

      The Trigger Setup option "Do not update commit status" does not work. When I use this option, "Update commit status during build" is automatically added and therefore the status on Github is updated.

      See the screenshots:
      when_saved.png .. the state when I'm saving the configuration
      after_reload.png .. when I leave the configuration and get back to it, there's "Update commit status during build" added
      github_test_results.png .. the only workaround I found: rewrite the context to whatever (like "issue JENKINS-39449") and leave --none-- for URL. Still it clutters the list of test results.

      Attachments

        Activity

          mbocek Michal Bocek added a comment - - edited

          I think that one of the options for not updating the Github status could be entering

          --none--
          

          to the status context field within the "Update commit status during build" trigger option.

          mbocek Michal Bocek added a comment - - edited I think that one of the options for not updating the Github status could be entering --none-- to the status context field within the "Update commit status during build" trigger option.
          ericgoedtel Eric Goedtel added a comment - - edited

          Getting dinged by this, too. I want to start jobs from PRs but not necessarily update the status of the PR. Maybe that seem a little fringe but it is useful.

          Using Jenkins 2.7 and GHPRB 1.33.1

          ericgoedtel Eric Goedtel added a comment - - edited Getting dinged by this, too. I want to start jobs from PRs but not necessarily update the status of the PR. Maybe that seem a little fringe but it is useful. Using Jenkins 2.7 and GHPRB 1.33.1
          oeuftete oeuftete added a comment -

          If it helps in finding the source of the problem, when both the "Do not update" and "Update" options are set, any options set under "Update" are not used. For example, even if "Commit Status Context" is populated, the build will set the status context as "default".

          oeuftete oeuftete added a comment - If it helps in finding the source of the problem, when both the "Do not update" and "Update" options are set, any options set under "Update" are not used. For example, even if "Commit Status Context" is populated, the build will set the status context as "default".
          martinmine Martin added a comment -

          Also having this issue on 1.36.2.

          martinmine Martin added a comment - Also having this issue on 1.36.2.

          People

            bpatterson ben patterson
            mbocek Michal Bocek
            Votes:
            4 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated: