• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major

      As of today, the commit status updating of my multipipeline project stopped working, and I'm seeing the following error in the logs:

      Could not update commit status. Message: {"message":"Not Found","documentation_url":"https://developer.github.com/enterprise/2.8/v3"}
      

      The following changes were made since the last time things were working:

      • Upgraded all jenkins plugin (last update was ~2 weeks ago)
      • Re-created my scan credentials token as a "username/password" token since I'm unable to use my old "secret text" token since upgrading: see https://issues.jenkins-ci.org/browse/JENKINS-39086

      I think the token itself is okay. It has the 'repo:status' scope, and I'm able to manually create a commit statuses with it using the GH API via curl.

      Perhaps this is a recent regression causing the wrong HTTP request to be made for creating the commit status? Perhaps limited to GH Enterprise?

      I'm happy to provide more information, but I don't know how to get more debugging info on the actual http request that is causing the problem.

          [JENKINS-41750] commit status updating broken

          Felix Geisendörfer created issue -
          Felix Geisendörfer made changes -
          Description Original: As of today, the commit status updating of my multipipeline project stopped working, and I'm seeing the following error in the logs:

          {noformat}
          Could not update commit status. Mes
          sage: {"message":"Not Found","documentation_url":"https://developer.github.com/enterprise/2.8/v3"}
          {noformat}

          The following changes were made since the last time things were working:

          * Upgraded all jenkins plugin (last update was ~2 weeks ago)
          * Re-created my scan credentials token as a "username/password" token since I'm unable to use my old "secret text" token since upgrading: see https://issues.jenkins-ci.org/browse/JENKINS-39086

          I think the token itself is okay. It has the 'repo:status' scope, and I've been able to manually create a commit status using the GH API via curl.

          Perhaps this is a recent regression causing the wrong HTTP request to be made for creating the commit status? Perhaps limited to GH Enterprise?

          I'm happy to provide more information, but I don't know how to get more debugging info on the actual http request that is causing the problem.
          New: As of today, the commit status updating of my multipipeline project stopped working, and I'm seeing the following error in the logs:

          {noformat}
          Could not update commit status. Message: {"message":"Not Found","documentation_url":"https://developer.github.com/enterprise/2.8/v3"}
          {noformat}

          The following changes were made since the last time things were working:

          * Upgraded all jenkins plugin (last update was ~2 weeks ago)
          * Re-created my scan credentials token as a "username/password" token since I'm unable to use my old "secret text" token since upgrading: see https://issues.jenkins-ci.org/browse/JENKINS-39086

          I think the token itself is okay. It has the 'repo:status' scope, and I've been able to manually create a commit status using the GH API via curl.

          Perhaps this is a recent regression causing the wrong HTTP request to be made for creating the commit status? Perhaps limited to GH Enterprise?

          I'm happy to provide more information, but I don't know how to get more debugging info on the actual http request that is causing the problem.
          Felix Geisendörfer made changes -
          Description Original: As of today, the commit status updating of my multipipeline project stopped working, and I'm seeing the following error in the logs:

          {noformat}
          Could not update commit status. Message: {"message":"Not Found","documentation_url":"https://developer.github.com/enterprise/2.8/v3"}
          {noformat}

          The following changes were made since the last time things were working:

          * Upgraded all jenkins plugin (last update was ~2 weeks ago)
          * Re-created my scan credentials token as a "username/password" token since I'm unable to use my old "secret text" token since upgrading: see https://issues.jenkins-ci.org/browse/JENKINS-39086

          I think the token itself is okay. It has the 'repo:status' scope, and I've been able to manually create a commit status using the GH API via curl.

          Perhaps this is a recent regression causing the wrong HTTP request to be made for creating the commit status? Perhaps limited to GH Enterprise?

          I'm happy to provide more information, but I don't know how to get more debugging info on the actual http request that is causing the problem.
          New: As of today, the commit status updating of my multipipeline project stopped working, and I'm seeing the following error in the logs:

          {noformat}
          Could not update commit status. Message: {"message":"Not Found","documentation_url":"https://developer.github.com/enterprise/2.8/v3"}
          {noformat}

          The following changes were made since the last time things were working:

          * Upgraded all jenkins plugin (last update was ~2 weeks ago)
          * Re-created my scan credentials token as a "username/password" token since I'm unable to use my old "secret text" token since upgrading: see https://issues.jenkins-ci.org/browse/JENKINS-39086

          I think the token itself is okay. It has the 'repo:status' scope, and I'm able to manually create a commit statuses with it using the GH API via curl.

          Perhaps this is a recent regression causing the wrong HTTP request to be made for creating the commit status? Perhaps limited to GH Enterprise?

          I'm happy to provide more information, but I don't know how to get more debugging info on the actual http request that is causing the problem.
          James Dumay made changes -
          Assignee New: CloudBees Inc. [ cloudbees ]
          James Dumay made changes -
          Labels New: blueocean
          Andrew Bayer made changes -
          Labels Original: blueocean New: blueocean triaged-2018-11

            cloudbees CloudBees Inc.
            felixge Felix Geisendörfer
            Votes:
            2 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: