[JIRA] (JENKINS-62133) Resource Root URL shows 404 validation error in configure screen

7 views
Skip to first unread message

fred.vogt@gmail.com (JIRA)

unread,
Apr 30, 2020, 6:19:03 PM4/30/20
to jenkinsc...@googlegroups.com
Fred Vogt created an issue
 
Jenkins / Bug JENKINS-62133
Resource Root URL shows 404 validation error in configure screen
Issue Type: Bug Bug
Assignee: Unassigned
Attachments: Screen Shot 2020-04-30 at 15.06.40.png, Screen Shot 2020-04-30 at 15.08.29.png, Screen Shot 2020-04-30 at 15.09.29.png
Components: core
Created: 2020-04-30 22:18
Environment: Jenkins 2.234, AWS ec2 instance running jenkins container.

Jenkins URL: https://jenkins-backend.dev.cicdenv.com/
Resoure Root URL: https://builds-backend.dev.cicdenv.com/

Both DNS names go to an AWS ALB with host routing rules.

jenkins:
  crumbIssuer:
    standard:
      excludeClientIPFromCrumb: true

JenkinsLocationConfiguration.get().url = ...
ResourceDomainConfiguration.get().url = ...
Priority: Minor Minor
Reporter: Fred Vogt

It seems that something is wrong in how this validation is performed.

This is reproduceable running locally with:

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo

fred.vogt@gmail.com (JIRA)

unread,
Apr 30, 2020, 6:22:02 PM4/30/20
to jenkinsc...@googlegroups.com
Fred Vogt updated an issue
Change By: Fred Vogt
Environment: Jenkins 2.234 , local or AWS ec2 instance running jenkins container.


Jenkins URL: https://jenkins-backend.dev.cicdenv.com/
Resoure Root URL: https://builds-backend.dev.cicdenv.com/

Both DNS names go to an AWS ALB with host routing rules.

jenkins:
  crumbIssuer:
    standard:
      excludeClientIPFromCrumb: true

JenkinsLocationConfiguration.get().url = ...
ResourceDomainConfiguration.get().url = ...

fred.vogt@gmail.com (JIRA)

unread,
Apr 30, 2020, 6:23:02 PM4/30/20
to jenkinsc...@googlegroups.com
Fred Vogt commented on Bug JENKINS-62133
 
Re: Resource Root URL shows 404 validation error in configure screen

Jenkins 2.234, AWS ec2 instance running jenkins container.

Jenkins URL: https://jenkins-backend.dev.cicdenv.com/
Resoure Root URL: https://builds-backend.dev.cicdenv.com/

Both DNS names go to an AWS ALB with host routing rules.

jenkins:
crumbIssuer:
standard:
excludeClientIPFromCrumb: true

The server/resource root URLs are set in groovy hooky scripts:


JenkinsLocationConfiguration.get().url = ...
ResourceDomainConfiguration.get().url = ...

fred.vogt@gmail.com (JIRA)

unread,
Apr 30, 2020, 6:26:02 PM4/30/20
to jenkinsc...@googlegroups.com
Fred Vogt edited a comment on Bug JENKINS-62133
Jenkins 2.234, AWS ec2 instance running jenkins container.

Jenkins URL: https://jenkins-backend.dev.cicdenv.com/
Resoure Root URL: https://builds-backend.dev.cicdenv.com/

Both DNS names go to an AWS ALB with host routing rules.

jenkins:
  crumbIssuer:
    standard:
      excludeClientIPFromCrumb: true

The server/resource root URLs are set in groovy hooky scripts:
JenkinsLocationConfiguration.get().url = ...
ResourceDomainConfiguration.get().url = ...


I haven't used a separate resource root url before.
https://github.com/jenkinsci/jenkins/pull/4239

I put a custom logo override into userContent and it is working which leads me to believe the resource root url setting is working, however the check against /instance-identity/ is failing in the configure page.
Reply all
Reply to author
Forward
0 new messages