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 On Sunday, January 8, 2017 at 5:49:36 PM UTC-8, Brian Ray wrote: > > 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 > > On Thursday, December 29, 2016 at 9:29:44 AM UTC-8, user_dev wrote: >> >> 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. >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/530827ec-b0e9-4ede-bcc3-81af3b8ee488%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
