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

Unable to authorize blueocean with github

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Blocker
    • Resolution: Fixed
    • Component/s: blueocean-plugin
    • Labels:
      None
    • Environment:
      Blueocean: 1.22.0
      Jenkins: 2.222.1

      Running on Amazon linux 2. Issue occuring on both Chrome and Safari
    • Similar Issues:
    • Released As:
      1.23.0

      Description

      NOTE FROM MAINTAINER: 

      This issue has been filed with the github-api maintainer: https://github.com/github-api/github-api/issues/780

      Rolling back to github-api 1.106 addresses this issue in the short term. 

      Grab the 1.106. version of the plugin from  

      http://updates.jenkins-ci.org/download/plugins/github-api/

      Then go to manage plugins > Advance > Upload Plugin and upload the 1.106 plugins and install it. All dependencies and indirect dependencies will also be satisfied with this version.

       

      When trying to create a pipeline with blueocean, I enter my personal access token and choose connect. I get the following logged to console.

       

      Unhandled Rejection: "Error: fetch failed: 500 for http://<ip>:8080/blue/rest/organizations/jenkins/scm/github/validate/?apiUrl=https://api.github.com\n at FetchFunctions.checkStatus (http://<ip>:8080/adjuncts/43befe0e/io/jenkins/blueocean/blueocean-core-js.js:54923:25)"

       

      Not really sure how to debug this. There is no sign of it in jenkins logs. This only occurs when I enter a valid personal access token. If I enter gibberish, it correctly tells me it's an invalid token.

       

       

       

        Attachments

          Issue Links

            Activity

            stevepkr84 Steve Parker created issue -
            dnusbaum Devin Nusbaum made changes -
            Field Original Value New Value
            Remote Link This issue links to "github-api/github-api Issue #780 (Web Link)" [ 24845 ]
            bitwiseman Liam Newman made changes -
            Description When trying to create a pipeline with blueocean, I enter my personal access token and choose connect. I get the following logged to console.

             

            Unhandled Rejection: "Error: fetch failed: 500 for http://&lt;ip&gt;:8080/blue/rest/organizations/jenkins/scm/github/validate/?apiUrl=https://api.github.com\n at FetchFunctions.checkStatus (http://&lt;ip&gt;:8080/adjuncts/43befe0e/io/jenkins/blueocean/blueocean-core-js.js:54923:25)"

             

            Not really sure how to debug this. There is no sign of it in jenkins logs. This only occurs when I enter a valid personal access token. If I enter gibberish, it correctly tells me it's an invalid token.
            When trying to create a pipeline with blueocean, I enter my personal access token and choose connect. I get the following logged to console.

             

            Unhandled Rejection: "Error: fetch failed: 500 for http://&lt;ip&gt;:8080/blue/rest/organizations/jenkins/scm/github/validate/?apiUrl=[https://api.github.com\n|https://api.github.comn/] at FetchFunctions.checkStatus (http://&lt;ip&gt;:8080/adjuncts/43befe0e/io/jenkins/blueocean/blueocean-core-js.js:54923:25)"

             

            Not really sure how to debug this. There is no sign of it in jenkins logs. This only occurs when I enter a valid personal access token. If I enter gibberish, it correctly tells me it's an invalid token.

            NOTE FROM MAINTAINER: 

            This issue has been filed with the github-api maintainer: [https://github.com/github-api/github-api/issues/780]

            Rolling back to github-api 1.106 addresses this issue in the short term. 

             

             
            bitwiseman Liam Newman made changes -
            Description When trying to create a pipeline with blueocean, I enter my personal access token and choose connect. I get the following logged to console.

             

            Unhandled Rejection: "Error: fetch failed: 500 for http://&lt;ip&gt;:8080/blue/rest/organizations/jenkins/scm/github/validate/?apiUrl=[https://api.github.com\n|https://api.github.comn/] at FetchFunctions.checkStatus (http://&lt;ip&gt;:8080/adjuncts/43befe0e/io/jenkins/blueocean/blueocean-core-js.js:54923:25)"

             

            Not really sure how to debug this. There is no sign of it in jenkins logs. This only occurs when I enter a valid personal access token. If I enter gibberish, it correctly tells me it's an invalid token.

            NOTE FROM MAINTAINER: 

            This issue has been filed with the github-api maintainer: [https://github.com/github-api/github-api/issues/780]

            Rolling back to github-api 1.106 addresses this issue in the short term. 

             

             
            NOTE FROM MAINTAINER: 
            {quote}This issue has been filed with the github-api maintainer: [https://github.com/github-api/github-api/issues/780]

            Rolling back to github-api 1.106 addresses this issue in the short term. 

            Grab the [1.106|http://updates.jenkins-ci.org/download/plugins/github-api/1.106/github-api.hpi]. version of the plugin from  

            [http://updates.jenkins-ci.org/download/plugins/github-api/]

            Then go to manage plugins > Advance > Upload Plugin and upload the 1.106 plugins and install it. All dependencies and indirect dependencies will also be satisfied with this version.
            {quote}
             

            When trying to create a pipeline with blueocean, I enter my personal access token and choose connect. I get the following logged to console.

             

            Unhandled Rejection: "Error: fetch failed: 500 for http://&lt;ip&gt;:8080/blue/rest/organizations/jenkins/scm/github/validate/?apiUrl=[https://api.github.com\n|https://api.github.comn/] at FetchFunctions.checkStatus (http://&lt;ip&gt;:8080/adjuncts/43befe0e/io/jenkins/blueocean/blueocean-core-js.js:54923:25)"

             

            Not really sure how to debug this. There is no sign of it in jenkins logs. This only occurs when I enter a valid personal access token. If I enter gibberish, it correctly tells me it's an invalid token.

             

             

             
            bitwiseman Liam Newman made changes -
            Assignee Liam Newman [ bitwiseman ]
            bitwiseman Liam Newman made changes -
            Released As 1.23.0
            Resolution Fixed [ 1 ]
            Status Open [ 1 ] Resolved [ 5 ]

              People

              Assignee:
              bitwiseman Liam Newman
              Reporter:
              stevepkr84 Steve Parker
              Votes:
              6 Vote for this issue
              Watchers:
              11 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: