Skip to end of metadata
Go to start of metadata

Plugin Information

View Nested View on the plugin site for more information.

This plugin is up for adoption. Want to help improve this plugin? Click here to learn more!

View type to allow grouping job views into multiple levels instead of one big list of tabs.

This plugin adds a new view type that can be selected when adding job views. This view does not show any jobs, but rather contains another set of views. By default, clicking on the view tab for a nested view shows a list of the subviews it contains (with folder icons). You can also configure a default subview to bypass this intermediate page and jump directly to that default view. Now the view tabs across the top show the views in this nested view, and the job list is for this default subview. This streamlines the navigation between views, but makes it harder to find the Edit View link for the nested view itself. Once a default subview has been assigned, navigate to the edit page by first clicking the plus ("+") icon in the view tabs (for adding a new subview) and then find the Edit View link in the sidepanel.

Note, that starting from 1.10 columns Status and Weather are switched off by default because of issues with performance, but if you'd like to have them, just edit your view and add respective columns.


Change Log

Version 1.14 (November 23, 2013)
Version 1.13 (November 5, 2013)
  • Fixed view results to be gray if no jobs were run in subviews yet (issue #17040)
  • Fixed deleting of subviews (it didn't save on disk) (issue #20382)
Version 1.12 (October 30, 2013)
  • Fixed view results (aggregating of subviews and jobs) to follow the correct priority - if at least one job is red, then the view will be red (issue #19716)
Version 1.11 (September 25, 2013)
  • Fixed creation of subviews if Nested View is the default one (JENKINS-17041)
  • Support checking duplicate names with jenkins 1.512 or newer (JENKINS-18053)
Version 1.10 (April 7, 2013)
  • Added an ability to remove or add Weather and Status columns which speeds up nested views (JENKINS-17352)
Version 1.9 (August 16, 2012)
  • Improved performance and accuracy when computing worst result and health for large views
  • add support for hierarchical job model (ex : cloudbees folder plugin)
  • display grey icon when no nested content has been built
Version 1.8 (Jul 28, 2011)
  • Properly check for duplicate names within the current nested view when creating a new view (in Jenkins 1.416 or newer).
  • Ignore disabled project when calculating worst build result in a nested view. (JENKINS-8922)
Version 1.7 (Feb 25, 2011)
  • Rerelease 1.6 to properly set required Jenkins version.
Version 1.6 (Feb 16, 2011)
  • Show status icon for each view, representing the worst result of any job in that view. (JENKINS-7124)
  • Fix link in empty nested view to be a link instead of raw HTML. (JENKINS-7862)
Version 1.5 (Oct 20, 2010)
  • Update to work with Hudson 1.381 or higher. (JENKINS-7815)
  • Calculate view-health for a nested view by recursing into its subviews. (JENKINS-7125)
  • Export nested view details via Remote API. (JENKINS-7489)
  • Don't allow setting a default subview for a nested view that is the Hudson default view, as this prevents access to other top level view tabs. (JENKINS-7362)
Version 1.4 (Jul 12, 2010)
  • Update to work with Hudson 1.366 or higher.
Version 1.3 (Jun 16, 2010)
  • Sort subviews alphabetically. (JENKINS-6757)
  • Russian translation.
Version 1.2 (May 27, 2010)
Version 1.1 (Mar 22, 2010)
  • Spanish translation.
Version 1.0 (Jan 21, 2010)
  • Initial release.

9 Comments

  1. Unknown User (st3@holometric.de)

    just switched to the lasted version with the weather icons and it looks great! nice work!

  2. My only issue with this is with the default view; when you go into a subfolder, you can't nagivate back to the folder level without going up one level higher than necessary. You can with your browser back button of course but would be nicer if it was built-in.

  3. A couple of months ago I made some modifications to the nested-view plugin, built it and installed it on my Jenkins without problems. Now I made some minor changes (just layout in one of the .jelly files) but I cannot build anymore: 

    \jenkins\tmp\nested-view\src\main\java\hudson\plugins\nested_view\NestedView.java:[71,7] hudson.plugins.nested_view.NestedView is not abstract and does not override abstract method getViewActions() in hudson.model.ViewGroup 

    I have refreshed all my .m2 repo etc. 

    any idea what I'm doing wrong ? 

    thanks, 
    Miguel

    1. See https://github.com/jenkinsci/jenkins/blob/da4ddde7564a15f6e8d9ee83f8499b7369dbe24b/core/src/main/java/hudson/model/ViewGroup.java#L139
      It is an API in newer Jenkins versions that hasn't yet been added in nested-view plugin. You can compile against an older Jenkins version, or implement the new API (or wait until I add this, which I'll do shortly).

  4. Great plugin, thanks for your work!

    Two things am I missing:

    1. It would be very nice, if there are configurable columns in the nested view, at least a description column.
    2. Is it possible to implement a count column which summarize the number of containing sub items?
  5. The ability to attach existing Nested View to a new one (after creating it) would be very nice with GUI (without at first time would be appreciate too).

    Great job and thanks for your work !

  6. Hi,

    I find the description a bit hard to understand, can't really see how the plugin works and how views/sub-views can be related and how they can be used to group jobs.

    In particular, I'd like to see at once how it compares to or differs from the Cloudbees Folders plugin. 

    Maybe adding some screenshots could make it clearer?

    As they say, a picture is worth a thousand words! ;-)

    1. i agree, anyone able to provide quick comment on how to use this?

      :D

  7. I've been using this plugin for years.  As we've scaled, our Java heap usage has grown to ridiculous sizes.  As I'm investigating, there are multiple causes.  One is this plugin.  If you select Weather, this plugin seems to load all jobs' metadata (env vars, VIEW_MAP, paths to files on Jenkins job's folders) for all history.  For us, it was 6 GB of strings after initializing Jenkins in the Java heap.  Don't use weather.  In retrospect, that never really told us anything useful.  Aggregate status, however, is a quick way for someone to manually check for infrastructure failures that aren't automatically handled.