tags:

I had tow motivations of getting rid of the All view

  1. The All view is quite annoying don't you think? After using Hudson for a while you have tens/hundreds of jobs lined up in a huge list - who needs that right.
  2. I wanted a "hidden jobs section" - Jobs no one but myself (and who ever needs access to it) can see.

 

In order to get rid of it (the All view) simply:

  1. Create a new view call it "xyz" and add what ever you want to it - and there are quite a few plugins you can adopt for see examples below,
  2. Navigate to hudson >> configure hudson (http://[hudson_url]/hudson/configure) and chenge the default view to your "xyz" view.
  3. Select the All view in Hudson's home page and you should be able to delete it.

 

View Enhancement plugins:

  • Last Failure Version Column Plugin — Adds a column showing last failed version that can be configured in views.
  • Cron Column Plugin — View column showing the cron trigger expressions that can be configured on a job.
  • Maven Info Plugin — Adds columns configurable in views to show info about Maven jobs.
  • View Job Filters — Manage multiple views and hundreds of jobs much more easily. This plug-in provides more ways to include/exclude jobs from a view, including filtering by SCM path, and by any job or build status type, as well as "chaining" of filters and negating filters.
  • Job Type Column Plugin — Adds column showing job type that can be configured in views.

I'm sure there are others ...

 

Hope you find this useful I know I did

4

Comments

I left out the obvious - you can also edit hudson config.xml - but then you need to reload hudson, which isn't fun doing when you waiting on builds to complete in the middle of the day (or night) so ...

I agree that the "All" view can get cluttered and useless, and it is indeed a good practice to follow your suggestion; But in some cases, you have more then one group or users which are interested in different jobs. What you need then is to create a custom view for each group/user.   There is an open issue for this feature at Hudson (http://issues.hudson-ci.org/browse/HUDSON-5318) which, when resolved, will give the option to set a default view at the user level.

I agree, altough please rememmber my motivation was to "hide" some jobs, and not see that long list of builds.   What you are referring too is also a "must" and, let me add to your CR the ability to set a permission on who can view a certain view's content - that will be even greater than a view per group / user.   BTW, dosen't the Personal View Plugin answer your need ?! - this will require a first time configuration per user of course.   My 2 cents, HP

You wouldn't happen to have a view plugin that nests jobs (not the views) would you?     IE you have a top job that calls lower level jobs and they call others, etc.  Nesting them would allow to visually see the hierarchy of the flow.