Major When using folders (plugin), the search returns two results for a unique job: one with the job name and one with the folder plus the job name.
The second one works fine, not the first one.
When the searched phrase exactly matches a job name, you are redirected to that job instead of getting a list of results. As a consequence, searching for a job contained in a folder by its exact name will lead to a 404 page.
For instance, in the attached screenshot, searching for "addons_nuxeo-drive-server-7.10" which is contained in the "7.10" folder:
- hitting enter lead to 404
- waiting for the suggested results returns an unusable "addons_nuxeo-drive-server-7.10" and a working "7.10 addons_nuxeo-drive-server-7.10".
Note also that the both results work fine if the current page is the containing folder. From https://qa.nuxeo.org/jenkins/job/7.10/ , both the "relative path" "addons_nuxeo-drive-server-7.10" and the "folder relative or absolute 
path" "7.10 addons_nuxeo-drive-server-7.10" will work.
It is not clear if "7.10 addons_nuxeo-drive-server-7.10" is an absolute or relative, full or partial path... What happens with a job contained in sub folders...?
- duplicates
-
JENKINS-35459 Duplicated elements with incorrect URL when using the search on DashBoard View
-
- Resolved
-
- is related to
-
-
- Resolved
-
- links to
[JENKINS-35158] search box provides 404 and duplicates results for jobs in folders
Julien Carsique
created issue -
Julien Carsique
made changes -
| Component/s | New: cloudbees-folder-plugin [ 18137 ] |
Julien Carsique
made changes -
| Environment |
New:
Jenkins 1.642.2 Folders Plugin 5.11 |
I confirm the functionality is still unsupported. Moreover, the extension engine for Search Factories is not designed well for such nested searches
Julien Carsique
added a comment - Depending on how much time is required to properly fix that feature, it could be relevant to first add a post filtering as a workaround: displaying invalid URLs is confusing and, moreover, the redirect to 404 in case of exact match is a bigger issue: users complain that the job is missing or that the URL is broken...
Julien Carsique
added a comment - Depending on how much time is required to properly fix that feature, it could be relevant to first add a post filtering as a workaround: displaying invalid URLs is confusing and, moreover, the redirect to 404 in case of exact match is a bigger issue: users complain that the job is missing or that the URL is broken... I can re-produce sometimes the issue on your instance, but not on a fresh instance. Without a re-producible scenario on fresh instance I find hard to understand why the issue is happening and to fix it.
As I said, on a fresh instance this issue is not re-producible using the same core version you are using and with latest Jenkins bits.
| Component/s | Original: cloudbees-folder-plugin [ 18137 ] |
What version of Jenkins is this?