-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins ver. 1.462
When looking at the console output for the parent job of a matrix job is has links to the child jobs. i.e.:
Started by an SCM change Building remotely on foo in workspace /var/lib/jenkins/workspace/test Checkout:test / /var/lib/jenkins/workspace/test - hudson.remoting.Channel@2d172d60:foo Using strategy: Default Cloning the remote Git repository Cloning repository origin Fetching upstream changes from ssh://hudson@bar/private/test Commencing build of Revision 6a234803887ea65ea470c9198c4da18f3460c416 (origin/master) Checking out Revision 6a234803887ea65ea470c9198c4da18f3460c416 (origin/master) No change to record in branch origin/master Triggering x86_64,el6-lab Triggering x86_64,sles11-lab Triggering x86_64,el5-lab x86_64,el6-lab completed with result FAILURE x86_64,sles11-lab completed with result FAILURE x86_64,el5-lab completed with result FAILURE Notifying upstream projects of job completion Finished: FAILURE
The x86_64,{el
{5,6},sles11}-lab strings are all URLs however they are absolute URLs complete with node name in them (i.e. http://jenkins.example.com:8080/job/test/arch=x86_64,distro=el6-lab/) rather than relative URLs (i.e. /job/test/arch=x86_64,distro=el6-lab/).
You can imagine the problems this causes for all sorts of use-cases like domain rewriting, proxying, etc. It's just generally a bad idea to use absolute URLs when you are making a reference to the current namespace.