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

Hyperlinks quietly fail when JenkinsLocationConfiguration incorrect

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • Jenkins ver. 1.642, Workflow Plugin 1.12

      When the Jenkins site is accessed via short name, e.g.: http://jenkins instead of http://jenkins.domain.tld, the "Click here to forcibly terminate running steps" link fails silently. Opening the developer tools in the browser and checking the console shows the following error in Chrome:

      XMLHttpRequest cannot load http://jenkins.domain.tld:8080/job/${ProjectName}/branch/${BranchName}/9/term. Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://jenkins:8080' is therefore not allowed access. The response had HTTP status code 405.
      

      If this behavior can't be "fixed" (one could argue it's not broken), notifying the end-user of the error and referring them to the URL specified in the JENKINS_URL variable seems like a potential improvement.

          [JENKINS-32192] Hyperlinks quietly fail when JenkinsLocationConfiguration incorrect

          Jesse Glick added a comment -

          A warning gets printed to the Jenkins log but it should probably be shown in the build log.

          Jesse Glick added a comment - A warning gets printed to the Jenkins log but it should probably be shown in the build log.

          Jesse Glick added a comment -

          A fix of JENKINS-31661 would make this less relevant.

          Jesse Glick added a comment - A fix of JENKINS-31661 would make this less relevant.

          This could also happen if access to Jenkins is provided through different domains (that do not match the Jenkins Root URL).
          Note that using the Proceed / Abort button (from the link "Paused for Input" and also at $BUILD_URL/input) if not affected by this.

          Allan BURDAJEWICZ added a comment - This could also happen if access to Jenkins is provided through different domains (that do not match the Jenkins Root URL). Note that using the Proceed / Abort button (from the link "Paused for Input" and also at $BUILD_URL/input ) if not affected by this.

            Unassigned Unassigned
            bgshacklett Brian G. Shacklett
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: