Jenkins nested view vs nested folder structure ?

[user_dev]

I am trying to understand the use case of having a nested folder structure in Jenkins to manage the different set of jobs. Previously I have been using nested view plugin to achieve that. But with folder structure in place what advantage it brings over nested view and subviews. Please explain.

[Brian Ray]

To name a few advantages, you can associate credential stores and Pipeline shared libraries with folders so that they are visible only to the jobs they contain. Through the Role Strategy plugin, you can also assign various privileges--and not simply read privileges--to jobs inside different folders.

I don't think you can do any of those things views.

Note: these advantages have nothing to do with how deeply the folders are nested.

Brian

[Brian Ray]

We use both in our primary Jenkins environment, though folders are the primary organizing mechanism.

The views are treated more like convenient "favorites" lists of jobs.

Brian