-
Bug
-
Resolution: Unresolved
-
Major
-
None
Hi there.
The bug has been captured, but I don't know is expected or not.
When I try to get a job nested in a folder via a direct lower-cased URL, it could return the job itself (HTTP code: 200), and sometimes(more often) Jenkins returns an error (HTTP code: 404). Fixing URL to the proper case fixes the issue.
The original name convention:
- Folders are always starting with a capital letter,
- Jobs could be in camel-case.
Some examples to get direct config.xml file for "job-type" Folder (XML files are cut, full versions are attached to the ticket):
https://jenkins/job/Folder1/config.xml
<?xml version='1.1' encoding='UTF-8'?> <com.cloudbees.hudson.plugins.folder.Folder plugin="cloudbees-folder@6.714.v79e858ef76a_2">
...
</com.cloudbees.hudson.plugins.folder.Folder>
https://jenkins/job/folder1/config.xml
<?xml version='1.1' encoding='UTF-8'?> <com.cloudbees.hudson.plugins.folder.Folder plugin="cloudbees-folder@6.714.v79e858ef76a_2">
...
</com.cloudbees.hudson.plugins.folder.Folder>
https://jenkins/job/folder1/job/Folder2/config.xml
<?xml version='1.1' encoding='UTF-8'?> <com.cloudbees.hudson.plugins.folder.Folder plugin="cloudbees-folder@6.714.v79e858ef76a_2">
...
</com.cloudbees.hudson.plugins.folder.Folder>
https://jenkins/job/folder1/job/folder2/config.xml
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>
<title>Error 404 Not Found</title>
</head>
...
</html>
System information is attached.
Probably similar issue is https://issues.jenkins.io/browse/JENKINS-67695
