-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins 2.289.1 (LTS) and nested view plugin 1.20
-
Powered by SuggestiMate -
nested-view-1.27
The recent nested view plugin release (1.20) breaks the Jenkins search box.
I rolled back to 1.19 which solved the issue for me.
Jenkins pipelines and multibranch pipelines are no longer showing up in the search anymore.
Also a "search help" is displayed which usually not comes up.
Freestyle projects can be found but the "search help" is stills showing up.
- is blocked by
-
JENKINS-68222 Search for 'xxx' returned: 0
-
- Closed
-
- is duplicated by
-
JENKINS-66084 Pipeline jobs appear in Search Box suggestions but not Search Results page
-
- Closed
-
- is related to
-
JENKINS-66343 Search does not find any (existing) job for the term
-
- Fixed but Unreleased
-
- relates to
-
JENKINS-65920 search page lists 0 results with new modifiers in left-rail
-
- Closed
-
[JENKINS-65924] Nested view plugin breaks Jenkins search
Thanks for your quick response
I am fine with using 1.19 for now. We are probably going to move to the folders plugin in the future.
I just wanted to document this issue since it breaks things, even when having no nested views added to Jenkins.
same, broke search functionality - rolled back to 1.17 and search working again
Same issue with Jenkins 2.289.3 and version 1.20.
Rollback the Nested-View plugin to 1.19 solved the issue.
Unfortunately we have to remember the broken Nested-View each time we update the plugins...
Yah. sorry. I stil did not had time to split the plugin to two. It is om todo list, but time is enemy. Feel free to contribute.
I had added 1.19 brnach for case the non-spoiled plugin needs some work. But it is not solving your issue.
Hello good users of nested view.
I had not managed to split the plugin, but accidenatlly an CVE was found. I'm really sorry.
The jenkins automated update can follow only latest - 1.21 release, so for you I had published https://github.com/jenkinsci/nested-view-plugin/releases/tag/nested-view-1.19.1
With 1.19 - without the search modifications.
If you have publicly accessible jenkis, be sure you manually update to this release.
nested view plugin v1.22 is available. this release contains a bugfix for this issue
... with nested view plugin v1.21 i could reproduce the search error.
with the newest available nested view plugin v1.22 the search error is gone. the search feature works and produce search results
I see. 1.19 had no interaction with search at all, so the search was working as usual search, unless you expected the results to show nested views content.
In 1.20 I had implemented the search support, but obviously I had broken the integrations with default search and other searche implementations. I thought it is broken by design, and thought that I wil lnee dto split it up to different plugin.
In addition, I had a bug here where I was counting only with free style projects, which got fixed in this release. If that indeed fixed the original issue, it wouldbeawesome.
joschua_grube lanni2460 squawk ffelhoffer maecval - Had 1.22 indeed fixed the original issue for you?
judovana issue is not fixed. I've checked with the latest LTS Jenkins version (2.303.3) and the plugin version 1.22 and there is the same problem:
Supported keywords with an example -the modifier(s) must start with `-` and end with `:`: -r: regex. Regex will be used also if query contains .* -R: regex, but appended and prepended by .* -c: contains (default) -s: starts with -e: ends with -q: equals -Q: equals honoring case -a: and - query will be split on spaces, and all must match -o: or - query will be split on spaces, and at least one must match -p: match just name -f: match full path (default) -j: search only in jobs (default is in all -jw (-jvn)) -v: search only in views (default is in all) -jw (-jvn) -n: search only in nested views (default is in all -jw (-jvn)) -w: search only in views and nested views (default is in all -jw (-jvn)) -!: invert result -eg "-Rjo: dacapo sp[ei]c": will find all Jobs which Matches .*dacapo.* or .*sp[ei]c.*
... the problem is fixed in my setup with Jenkins 2.312 + nested view plugin v1.22
I doubt that jenkins version have any effect here at all. But I'm afraid two issues are being mixed here in single ticket.
First issue - the original one - is that nested view search implementation is actually not an search extension, but search replacement
Second issue was, that only free style projects were recognized by it. That is now fixed (by https://github.com/jenkinsci/nested-view-plugin/pull/31 maybe with help of https://github.com/jenkinsci/nested-view-plugin/pull/30)
Hi,
I confirmed that only freestyle jobs is listed in search result page.
However, autocompletion in the search input filed return all expected elements (folders, freestyle and pipeline).
Tested with Nested View Plugin 1.22 and two differents jenkins instance : LTS (2.303.3) and 2.321
Best regards
I can also confirm that I had issues with the search with versions 1.20 -> 1.22.
In my local jenkins installation I had jobs of type freestyle, multibranch pipelines, and Organization Folder. None of which was covered in the nested view.
It seems that search works with the old version 1.19.1
Jenkins version (docker image): jenkins/jenkins:2.319.1-jdk11
judovanaHope you still have plans to fix this 😊 What do we miss with versions 1.20 to 1.22? I guess search related stuff that's mostly non-functional anyway? I suggest to remove those versions from the jenkins plugin center unless there's any special reason to leave it available. I'm not sure about the git tags.
On the other hand, great work and thanks for this nice plugin. This really enhances jenkins usability for multiple dev-teams since each team can have their own configuration of views 👍
Hello!
You are right. The search was the only main thing added with 1.20
No I do not have intentions to revert it It is super cool search, it works on many setups (including mine). I'm actually depending on it. (10k+ jobs in aprox 100k nested views)
I have plans to fix that. While it is unfixed, I will keep 1.19.x live.
As for the fix. My current idea is to split nested viws and nested-view search to two plugins, Second depending on first. But I had still not found a proper time frame to o that.
Maybe I will find possible to make it conditional in the runtime. But I doubt it a bit - I have not found proepr way how to extend the search, so it more replacing the default search.
Better fix would be to extned the search correctly, but spent quite a time on that and ended as it is.
Secondly, there is small if/ifelse/ifelse on instanceof of the project types in the impl: https://github.com/jenkinsci/nested-view-plugin/blob/master/src/main/java/hudson/plugins/nested_view/NestedViewsSearch.java
Maybe something is missing somwhere there. But more likely I think I simply had removed the search extensions of pipelilines/orghanisation folder an others by my ungentle touch.
So going back to the split or experiemtns wit conditional enablement/disablement.
I can also reproduce the issue with Jenkins 2.319.2 + Nested view 1.22. Also looking forward to receiving a fix to this wonderful plugin
Hello!
I had released 1.23 + 1.19.2
The main motivation is https://github.com/jenkinsci/nested-view-plugin/pull/32
The search is still not fixed (but am on it right now (at least for a while)). So readers of this bug, if affected by removal of jenkins icons from core, pls update manually to: https://github.com/jenkinsci/nested-view-plugin/releases/tag/nested-view-1.19.2
Hello!
Spent a nice Saturday trying somehow amend the search, but that probably can not work by design.
I had stepped back a bit, and hopefully made the NestedViewSearch possible to disable.
Right now it is done by existence of ~/.nestedViewsSearch (note, the home of user which run the jenkins, not necessarily you , where the ~ is user home, or whatever java's System.getProperty("user.home"); return.
If the file do not exists, NestedView search will be used. If it does exists, then something, what I hope is default view, will be used.
With this, I had released the 1.24
If you, people in this bug confirm it fixed your issues, I will do it configurabel by jenkins way. Thanx!
Our Jenkins has a use for custom-view-tabs. custom-view-tabs has a dependency on nested-view, but we don't use nested-view features ourselves. The new nested view search is really not useful to us, and has meant the last several months the search box is completely unusable on our Jenkins instances.
So for our use case, the inclusion of it in this plugin has had a very negative impact, but we can't just uninstall nested-view either.
I'm also really not sure how the search is related to nested-view - it seems like a side-project that has been added to an existing single-purpose plugin. Would it not be better to separate it into a different plugin and leave nested-view to do its own thing well without interfering with the search facility?
dsainty If the current version still does not fix the issue (haven't tried it, but will do this week if I have the time) then I recommend that you manually install the 1.19.1 version of the nested-view-plugin where the search works as expected. The custom-views-plugin does not require any higher version of nested-view-plugin than 1.5, it is just the default behavior of jenkins that it installs the highest available version of the dependency unless prohibited I guess.. See my comment above at 2022-01-12 15:04.
judovana I will test your fix and let you know the results asap thanks for the heads-up.
For me the issue persists with version 1.24. Downgrading to 1.19 fixes the issue temporarily, but I am eagerly waiting for a fixed version 1.25.
Hi Alexander, on 1.24, had you created the file as described in https://issues.jenkins.io/browse/JENKINS-65924?focusedCommentId=420904&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-420904 please?
judovana Hi Jiri, no, I did not create that file. I created the file and tried again with 1.24 and now it is working fine. Thank you!
Does it? Cool! Pls, readers of this trhead, if you may..can.. really try. My setup is indeed working oposite - with the in-nestedviews search on, I can search, without I can not find a thing.
I will change it to some config checkbox in future.
judovana So yes, creating the file you check for does fix search. But of course the default state is completely unusable search, which is not very satisfactory...
Updated to "1.24" of "Nested View Plugin". This is NOT fixing the search problem. I hope there will be a fix soon...
hoppej on 1.24, had you created the file as described in https://issues.jenkins.io/browse/JENKINS-65924?focusedCommentId=420904&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-420904 please?
dsainty I hear you. My case is oposite - the search is broken without the nested view search.
Seeing the file had brought it back, I can now add proper jenkins swithch, and will. Still I think the defualt will be on, but having one click to disable it for ever should be enough
judovana: Thanks for the advice, creating the file brought the search back! (Nested view plugin 1.24)
I created it as admin in Jenkins Script console on "master" with code (should return "Result: true")
new File(System.getProperty("user.home"),'.nestedViewsSearch').createNewFile()
Will we see an update soon that fixes the search without needing .nestedViewsSearch? Either fixed by default or with an option to fix it? [Preferably the former]
We had the issue on our system:
- Jenkins 2.346.1
- behind a reverse proxy and with a `/ci/` path prefix
- Nested View plugin 1.21
After upgrading the plugin to 1.26, the issue no more happens and I haven't had to create the `.nestedViewsSearch` file.
That is weird. I had not changed anything, and The 'enhanced" search is stil there...
I have probably mixed up something sorry. I went here cause our search results linked back to jobs using a relative URL such as `../../../../../../../../../../../../../../job/`. Which is described at https://stackoverflow.com/questions/68279189/jenkins-searchbox-result-urls-incorrect and apparently prompted for the filing of this JENKINS-65924.
Hello!
I have finaly found some time and get rid of the file in favour of normal jenkins global config
hpi to test: https://github.com/jenkinsci/nested-view-plugin/releases/tag/nested-view-1.2.7-pre
If you got me some feedback that it is what was epxected, I will merge and do a proper release. TY, and really sorry for delay
1.27 with global settings allowing to turn this on/of was released today. hth
This problem is back for me. Disabled plugin & restarted, search works again. Re-enabled and restarted, search is broken. I tried that command below in between, no effect.
new File(System.getProperty("user.home"),'.nestedViewsSearch').createNewFile()
I'd love to have this plugin, but we NEED to have search. Any options?
Jenkins 2.426.3
Nested Views 1.33
UPDATE: I removed that file created above and used the System Config page (/manage/configure) to disable this setting, and it works. It would be nice to show this more explicitly in the README.
hello!
Sorry for troubles. The readme have: https://github.com/jenkinsci/nested-view-plugin?tab=readme-ov-file#search-extension which contains the necessary info. I had also mentioned the difference it in GH release. https://github.com/jenkinsci/nested-view-plugin/releases/tag/nested-view-1.27
Do you have any more ideas where to put that?
I'm not sure formatting options you have in the Readme or Release Notes, but a picture like I aattached could help others who hit this. And maybe use the term "System" settings, not "global", as that's the actual term that appears in Jenkins (at least in my English-language install, not sure if other localizations translate differently). Thanks, glad to have this back, I do love the plugin!
If anyone is struggling with the bug with the search: I am not sure how more recent versions perform, but today I can say that 1.26 (with jenkins 2.452.3) the search works fine without any .nestedViewsSearch file in the home directory.
This issue still exists on Jenkins 2.479.3 and nested view plugin version 1.36 . When Nested View is enabled no search results are shown (we have 95%+ only multibranch pipelines).
Furthermore, when the plugin is disabled from the Manage Jenkins --> System and I try to search for a job I am redirected to the login screen where my credentials are not accepted....and trust me I did not mess up my password
UPDATE: The issue still exists if you have configured multiple active directories (what was our case). When I removed the multiple AD directories (left just one) the search functionality went back to normal
a) If the issue us caused by ActiveDirectroy plugin, then I think it deserves new issue, which will pinpoint it, and we can then try to fix it
b) by disabled plugin, you mean disabled search only, or disable whole plugin? If the first, then it may be stillthis bug, more likely different one. Or is this disablement issue appearing only with AD?
c )to make it work with pipelines should be doable. There is one switch/case on type of items the search is crawling in (which was needed, so it knows that it have to crawl into nested view). I do not use pipelines, so I'm probably not person to fix it immediately
judovana Thanks for your prompt response! I will gather the relevant data + screenshots and I will create an issue.
Since I am new to the community should I assign it to you or leave it unassigned ?
hi! Thanx for report. I was afraid that this can happen. however had no reply (https://groups.google.com/g/jenkinsci-dev/c/ad0V0VUz5Kw/m/oeDxDvAbBQAJ) when I was asking before the release itself.
I see two options - to fix the search so it will work also with your case, or to split nested views to two plugins - nested-view as it was, and then plugin, extending nested views - nested-view-search.
For the first option - I was hoping jenkins is mixing the search engines. Obviously it is not or I made it wrongly. So long story short, you would need to look into the nested-views plugin, and chek it here. I use some if (instanceof) maybe just few extensions here may help.
If you are not willing to dig into it (which is fully acceptable, and I'm really sorry for broken plugin) then I will continue with split of the plugin to two. It wil lnto be asap, but will happen.