Create smart views with exactly the jobs you want. Your smart views can automatically include or exclude jobs by using things like the SCM path or type, the job type, build statuses or trends or triggers, relevance to the logged-in user, email recipients, Maven configuration, job parameterization, and user permissions. Mix and match filters to narrow down to exactly what you want.
This plugin provides a number of filters that you can "chain" together to provide a much easier way to create views to organize hundreds of jobs. For each filter type, you can add multiple filters, and combine them with filters of other types. For example, you can create a view of all your nightly jobs except those not under any SCM. In a nutshell, this plugin provides the following:
Also, see this Cloud Bees write-up of the View Job Filters plugin.
With a large organization and hundreds of jobs, it will become very annoying and time-consuming to try to keep your views organized. The regular expression job filter can help, and there are multiple options to choose from to make it easier.
Create views that are most relevant to the logged-in user.
The "Name Matching" checkbox items are to allow you to get the name matching just right. The problem is that organizations often have different naming conventions that may not be consistent across version control, network logins, and email addresses. All of the options are checked by default so that this filter can make a thorough effort to find matching users.
The "Relevance Matching" options should be self explanatory. The point is to try and find all jobs that the logged in user cares about, based on their activity.
For the "How far back to check" value, use either "0" or blank to indicate you want to check all builds.
Note that not all combinations of criteria will make sense. Also take a look at the User permissions for Jobs filter.
This filter provides a number of options, and you can also add multiple of these filters, and choose different Match Types to include/exclude exactly the jobs you want. For example, you could create "Failed Jobs Only" and "Unstable Jobs Only" views, or make a more complicated view like the following example combination.
This filter gets a little more specific, and provides options to filter by the status of the job's builds. This example filters out (excludes) all jobs that have never built.
This filter is similar to the build status filter, but it takes into account the time in which the status changed.
The different Build trend types are
The different "how far back to check" types include, "Days", "Hours" and "Builds".
Use Regular Expressions to include or exclude parameterized jobs based on their build parameters.
For the name, value, and description - a blank indicates you do not care about that field - it behaves as if you had assigned it the regular expression ".*".
This filter works with String, Boolean, File, Choice, and Validating String parameter types.
Use this feature in tandem with security features such as the Standard matrix based security to create views that show different jobs depending on who is logged in.
This filters on whether a job is secured through the "Project-based Matrix Authorization Strategy".
This filter allows you to create a view consisting of jobs that are related through the concept of Upstream/Downstream (also called "Build after other projects are built" and "Build other projects").
that filters are chained together, so using this filter builds off of the jobs included by previous filters. Remember that
Combine this filter with other filters to choose not only the exact types of jobs to show, but how many of them to show.
The All Jobs view by default shows all jobs, but all other views require you to either select the jobs you want to include, or add a regex of ".*" to select all jobs always. This filter does this for you. This mostly useful if you're creating multiple "All Jobs" views, or replacing the default view, and would like to customize the columns, and would simply like to have each of those views show all jobs.
This column is an integral part of creating a smart view that shows just the jobs you want, and just the builds for those jobs that you want. Full documentation is found on the Build Filter (Wrapper) Column page.
These features are not entered as JIRA tickets because technically no one is requesting them. If you want one of these features, please Enter a JIRA Ticket and the feature will probably be added within a week.
Switched from Subversion to GitHub so the changelog is tricky to determine.
Skip to end of metadata Go to start of metadata