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

400 upon opening direct link of project in a GitHub organization project

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Not A Defect
    • Component/s: blueocean-plugin
    • Labels:
      None
    • Environment:
      Jenkins: 2.23, Blue Ocean: 1.0.0-b14
    • Similar Issues:

      Description

      I created a job of type "GitHub organization" named "inspectIT-GitHub" and added a the GitHub project "inspectIT" to it. The problem is, that I cannot use the links from the browser directly (or pressing F5), I do get a 400 back from Jenkins. If I open the links directly from blue ocean, it seems to be working fine. You can take a look at the problem in our running system:

      This is the base blue ocean url: http://jenkins.inspectit.rocks/blue/pipelines
      This is one of the links that is not working: http://jenkins.inspectit.rocks/blue/organizations/jenkins/inspectIT-GitHub%2FinspectIT/activity

      The standard pipeline test I created works on the other hand. So it could be related to this job type.

        Attachments

          Activity

          Hide
          jamesdumay James Dumay added a comment -

          Daniel Beck Stephen Connolly wouldn't this also be an issue in Jenkins Classic too? I suspect this isn't a Blue Ocean problem.

          Show
          jamesdumay James Dumay added a comment - Daniel Beck Stephen Connolly wouldn't this also be an issue in Jenkins Classic too? I suspect this isn't a Blue Ocean problem.
          Hide
          danielbeck Daniel Beck added a comment -

          Yes. It's misconfiguration of the reverse proxy. As I wrote above, the reverse proxy monitor used to detect this, but doesn't anymore.

          Show
          danielbeck Daniel Beck added a comment - Yes. It's misconfiguration of the reverse proxy. As I wrote above, the reverse proxy monitor used to detect this, but doesn't anymore.
          Hide
          danielbeck Daniel Beck added a comment -

          Unless we're rewriting this to "make RPM detect this again", this is Not A Defect.

          Show
          danielbeck Daniel Beck added a comment - Unless we're rewriting this to "make RPM detect this again", this is Not A Defect.
          Hide
          jamesdumay James Dumay added a comment -

          Unfortunately the way we URL encode things like branch names and organization names you do have to make this config change to Tomcat for it to work correctly. Tomcat isn't the recommended way of deploying Jenkins and most people use Jetty.

          Show
          jamesdumay James Dumay added a comment - Unfortunately the way we URL encode things like branch names and organization names you do have to make this config change to Tomcat for it to work correctly. Tomcat isn't the recommended way of deploying Jenkins and most people use Jetty.
          Hide
          danielbeck Daniel Beck added a comment -

          The rev proxy mon issue is tracked as JENKINS-31068.

          Show
          danielbeck Daniel Beck added a comment - The rev proxy mon issue is tracked as JENKINS-31068 .

            People

            • Assignee:
              Unassigned
              Reporter:
              pabouil Patrice Bouillet
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: