Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

Plugin Information

View View Job Filters on the plugin site for more information.

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.

What is the "View Job Filters" plugin?

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.

How do I get started?

  • Install the plugin
  • If needed, create a new view (besides the All view) by clicking the "+" tab
  • If editing an existing view, click the "Edit View" link (won't be available for the "All" view)
  • You will see the following button in the "Job Filters" section. Click it to select and add the filter type(s) you want.

Regular Expression Job Filter

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.

  • Include/Exclude options - ability to either add jobs or filter out jobs based on the expression, or the negation of the expression
  • Job name - allows you to filter out jobs when you have naming conventions.  Also allows you to "narrow down" other filters, or to match the negation of an expression
  • Job description - if you use descriptions, this may help you get what you want
  • SCM Configuration - this one is perhaps the best bang for the buck - put in something like "./my-office-name/." to automatically include all jobs that are organized under source control already by office.
  • Maven Configuration - looks at all your Maven goals, including freestyle projects, matrix (multi-configuration) projects, Maven projects, and Maven extra steps.
  • Email Recipients - a great way to organize views by "who cares about this job".  Will look in either the standard email publisher or the extended email publisher
  • Job Schedule - searches the chron spec and description to group jobs by when they run - for example "weekend jobs"
  • Node/Slave Label - matches against the Label Expression under the "Restrict where this project can be run" option

Filter by Relevance to Logged-in User

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.

Filter by Job Statuses

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.

Filter by Build Statuses

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.

Filter by Build Trend

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 latest build was
  • At least one build was
  • All builds were
  • Completed, Started, Stable, Unstable, Failed, Not Stable
  • Triggered by Timer, SCM, User, Remote, Upstream Job, CLI

The different "how far back to check" types include, "Days", "Hours" and "Builds".

Filter by SCM Type

Filter by the Jobs in Other Views

Filter by Job Parameterization

Use Regular Expressions to include or exclude parameterized jobs based on their build parameters.
Match the parameter name, build value, or description. Alternately, you may opt to depend on the default configured value.

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.

User Permissions for Jobs

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.

Filter jobs that have enabled project-based security

This filters on whether a job is secured through the "Project-based Matrix Authorization Strategy".

Upstream/Downstream Jobs Filter

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").
The options provided allow you to choose exactly which types of related jobs to show.

Note that filters are chained together, so using this filter builds off of the jobs included by previous filters. Remember that

  • This filter will not include any jobs if there are no jobs already selected
  • This filter (like most other filters) is capable of removing jobs that were already selected

Filter to Most Recent Jobs

Combine this filter with other filters to choose not only the exact types of jobs to show, but how many of them to show.

Showing All Jobs with the "All Jobs" Filter

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.

The Build Filter (Wrapper) Column.

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.


Version 1.x (Ideas)

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.

  • Retrofit existing filters to be default extensions (like the way columns work).  Justifications are
    • Allow for other views besides list view to more easily make use of them (for example, the status filter wasn't picked up by other views)
    • Minor benefit is that if you have hundreds of jobs, your view edit screen is cluttered by the list of jobs when all you wanted was a regex or a status.  So, you could delete any filters you don't want to see and they won't show up again.  Another strategy to handle this might simply be a checkbox titled "hide view list".  However, this would obscure the fact that often a job is added to a view accidentally by clicking the "new job" link while on that view.
  • Update other views to use the extension.  Currently only used by ListView.  Some views extend ListView (and do an include with jelly), so they can't be updated unless they update to newer ListView.  Not sure about other views - will need to take time and look at each.
  • Filter on other "descriptive" things besides job name.  Large organizations will have other things that distinguish jobs automatically, but Job name isn't always one of those things
    • Maven group id (not sure how practical this is)
    • SCM - add more scms besides cvs and svn - need to test and determine best way to make those scms "optional".
    • "java package" - could do by looking at file path?
  • More status filter options
    • Last time built - i.e. in the last X days (very useful for managing hundreds of jobs that should run nightly, but sometimes are misconfigured, etc.)
    • Number of days/builds stable
    • Build duration (e.g. for a "long running builds" view)
  • Other views filter improvements/fixes
    • Proper handle of deletes
    • ditto for renames
    • Don't allow a view to recursively include itself (currently doesn't break if you do, but it shouldn't even be an option)
  • Filter by scheduling types
    • Filter by all jobs that have polling and/or forced timed builds setup - e.g. "Manual Jobs" and "Scheduled Jobs"
      • And/or Filter by jobs last built manually/polled/forced
    • Filter by jobs that will soon be built (or SCM polled?)


Version 2.1.1 (Released November 9, 2018)

  • Fix: [JENKINS-43343] Regex filter now works with cron schedule for Pipeline jobs

Version 2.1.0 (Released November 4, 2018)

  • Feature: Regex Filter now supports full name, display name and full display name for jobs and folders
  • Feature: Introduces internationalization support and adds German as first supported language
  • Improvement: In-application help has been largely rewritten

Version 2.0.4 (Released October 19, 2018)

Version 2.0.3 (Released October 16, 2018)

  • Fix: prevent stack overflow when circular references in Other Views and Unclassified Views filter are detected
    • Display an error message identifying the circular view definition on the view config page
  • Fix: make mailermatrix-auth and matrix-project dependencies optional

Version 2.0.2 (Released September 18, 2018)

  • Fix: prevent StackOverflowException when more than one view uses UnclassifiedJobsFilter
  • Fix: validate regex in RegexJobFilter
  • Fix: ensure sorting in MostRecentJobsFilter is stable

Version 2.0.1 (Released September 13, 2018)

Version 2.0.0 (Released September 9, 2018)

New maintainer and first release in three years. This release merely puts the project on a newer foundation and updates some dependencies, but otherwise introduces no new features or bug fixes. Existing filters from pre-2.x versions should continue to work.

  • Minimal required Jenkins version increased to 1.625.3
  • Switch to Semantic Versioning
  • Project is now explicitly under the MIT License

Version 1.27 (Released August 21, 2015)

Switched from Subversion to GitHub so the changelog is tricky to determine.

Version 1.26 (Released August 14, 2013)

  • JENKINS-19191 (don't just consider build-trigger upstream, but all upstreams (including join))
  • JENKINS-19125 (Job SCM Configuration filter fails with CVS plugin disabled.)
  • JENKINS-18986 (Fencepost error in AbstractBuildTrendFilter.amount)

Version 1.23 (Released June 29, 2013)

  • JENKINS-18386 (more flexible job filter by parameter)
  • JENKINS-17597 (Poor performance using ParameterFilter)
  • JENKINS-17093 (Filter to show N jobs sorted by most recently completed)
  • JENKINS-18399 (possibility to filter jobs by "Restrict where this project can be run")

Version 1.22 (Released May 24, 2012)

  • Re-Fixed JENKINS-13781 (NPE in UserRelevanceView when no user is logged on)

Version 1.21 (Released May 23, 2012)

  • Improved Maven project support by implementing two enhancements
    • JENKINS-13846 (Upstream filter does not show all dependencies)
    • JENKINS-13850 (Unable to match emails for "Regular Expression Job Filter" on Match Value "Email recipients")

Version 1.20 (Released May 16, 2012)

  • Fixed JENKINS-13781 (NPE in UserRelevanceView when no user is logged on)
  • Improvement - JENKINS-13748 (Support for upstream/downstream jobs)

Version 1.19 (Released March 26, 2012)

  • Fixed JENKINS-13223 (Filter jobs that have enabled project-based security)

Version 1.18 (Released September 10, 2011)

Version 1.17.2 (Released September 8, 2011)

Version 1.17.1 (Released September 5, 2011)

  • Minor fix for Jenkins 1.427 compatibility issue with the introduction of "UserIdCause" (vs UserCause)

Version 1.17 (Released September 3, 2011)

  • Added User Relevance Filter (see documentation on this page)

Version 1.16 (Released August 16, 2011)

  • Fixed a bug with the way the regex filter handles multi-line descriptions (and trigger specs) JENKINS-10716

Version 1.15 (Released August 13, 2011)

  • added trigger types to the build trend filter. For example, create a view of all jobs that have not been triggered by an SCM change in a month.

Version 1.14 (Released August 10, 2011)

  • fixed regression in the regex filter. version 1.13 unintentionally requires git plugin to be installed, or regex on scm will cause an exception that cannot be recovered from through the hudson gui.

Version 1.13 (Released July 23, 2011)

  • add git
  • add chron to regex filter

Version 1.12

  • Added Matrix Job support to Regular Expressions Maven option
  • Fixed a bug in Regular Expressions Maven option

Version 1.11

Version 1.9

Version 1.8

  • Did not release properly due to Hudson infrastructure problems - all features scheduled for 1.8 are moved to 1.9

Version 1.7

  • Under-the-hoods performance improvements such as JENKINS-7956

Version 1.6

  • Add Maven support to regular expression filter
  • Fixed bug where filters take jobs out of order.  This is not a backwards compatible fix in terms of the way it displays, but fixes an obvious bug where the "Job" column shows it is sorted by name, but in fact the jobs are obviously not sorted by name.

Version 1.5

  • Fix JENKINS-7732 - "Job Views - Jobs not listed in other views filter"

Version 1.4

  • Fix JENKINS-7479 - "Create View Job Filter that includes/excludes Jobs by their Parameters"
  • Fix SCM Type localization bug
  • For "Other Views" filter, added handling of ViewGroups for nested views

Version 1.3

  • Fixed JENKINS-7432 - "Provide View Job Filter by Email Recipients"
  • Make SVN and CVS plugins optional instead of required

Version 1.2

  • Fixed JENKINS-7160 - "Provide View Filter for Current Jobs (Jobs build within the last x days)"
  • Added Build Trend Filter to provide filtering on what happened to the build in recent history (configurable).  See this page for details.

Version 1.1

  • Fixed JENKINS-6932 - "Allow to filter by SCM Branch" - applies to CVS only

Version 1.0 (initial release)

  • Filter on other "descriptive" things besides job name.  Large organizations will have other things that distinguish jobs automatically, but Job name isn't one of those things
    • SCM "URL" (only cvs and svn)
    • Job description field
  • More comprehensive status filter - would obsolete some other features/plugins, but this filter should be more useful/useable
    • Stable, Unstable, Failed, Aborted
    • In queue, never built, building
    • Disabled
  • Common include/exclude drop-down to make filters more easy to "chain"
  • All Jobs
  • Filter one view's jobs based on other view's jobs. 
    • Exclude - For example, View 1 will want all jobs with a certain regex, except for jobs already shown in View 2.  Then if View 2 changes what jobs it shows, View 1 is automatically updated.
    • Include - for a large organization, we might want "composite" views (not nested views) of the hierarchical parts of the organization


  1. Unknown User (c1test@yahoo.com)

    Hello there, are there plans to add filters base on job parameters, and/or fingerprints? Thanks.

    1. Unknown User (jacob_robertson)

      At this time, I am very happy to take any types of requests and make them a priority.

      For Job Parameters, I think I know what would make a lot of sense - just add job parameters as another type to allow the Regular Expression to match against.  That way, you could create a view that shows all jobs that are parameterized in similar ways.  If that's not quite what you meant, please provide your use case so I can more accurately provide that feature.  I will add it as a JIRA as well.

      For Fingerprints I really don't know what your expectation is.  It would be very useful if you could describe how you wanted to use this.  I have not used fingerprints myself, although I have played with them in Hudson and believe I understand how they work and their purpose.  Would you be creating a view that filters on the fingerprint configuration, or on the Recorded Fingerprints?  For example, if I create a fingerprint configuration on "**/foo-10.jar", and it results in a recorded fingerprint, I can see other jobs with fingerprinting that use that same fingerprint.  However, this is based on builds, not on the job itself.  But, I could imagine a view job filter that looks for any job with the latest (completed?) build that has any recorded fingerprint matching a regex of ".*/?foo-\d+\.jar" or some such thing.

      In any case, I can start working on these right away if you provide me a little more information.

    2. Unknown User (jacob_robertson)

      See the section on this page titled "Filter by Job Parameterization" and let me know if it meets your needs...

      1. Unknown User (c1test@yahoo.com)

        The job parameterization is perfect! Thanks for working on this so quickly. Yes, you are correct, I was thinking about filtering base on builds instead of the jobs.

  2. Unknown User (foch)

    Hello Jacob,

    would it be possible to have a filter by build and not by job? I have users that will launch Parametrized builds in parallel, with a different parameter to distinguish them. Then I would like to have a view that filters the builds based on this parameter. Your implementation merely filters based on the parameter of the last successful built, hence I can't use it as is, as one user would loose the job in his view when another user launches it with another parameter...

    Do you think that would be possible, or is it out of the scope of your plugin?

    Thanks and regards,


    1. Unknown User (jacob_robertson)

      Hi Julien,

      I would really like to implement this, and I think I need a little more discussion before I can do it.

      I am assuming the following two things

      • You have a parameterized job that is built two times by different users and those two builds might even be running in parallel
      • You have two different users that each are looking at a different view

      Based on that setup, here is how I'm interpreting your feature request:

      • User #1 configures their view's filters to include all jobs that have ever been run using a parameter (for example) of "ReleaseType=Financial"
      • User #2 configures their view's filters to include all jobs that have ever been run using a parameter (for example) of "ReleaseType=HumanResources"

      Let's say that there exists a few jobs (A, B, C) that currently aren't showing up in either user's views.  But then, User #1 builds jobs A and C, and for those build, sets the ReleaseType to Financial.  Suddenly both jobs A and C show up in User #1's view.

      Then (perhaps at the same time), User #2 builds jobs B and C, and for those builds sets the ReleaseType to HumanResources.  Suddenly both jobs B and C show up in User #2's view.

      However - this plugin does not try and filter out the builds for a job - it just filters out jobs for a view.  So if either User visits the job's list of builds, they will see all builds - it doesn't filter out the builds based on their parameters.

      Also, right now the plugin only looks at complete builds.  Do you have a requirement to also look at builds in progress?  So that if a build is in progress with the right parameterization, that might allow it to show up in a view.

      Okay - so I hope these questions and descriptions made sense.  If I'm way off on any/all of this, just let me know what I'm not understanding...

      1. Unknown User (foch)

        Hello Jacob,

        Yes I believe you are on the way on it :)
        Let me add that when User #2 builds job B and C, with the current implementation, B and C show up in User #2's view, and C is removed from User #1's view as the last successful parameter was HumanResources, which is disturbing for User #1.

        My only requirement would be yes to be able to look at builds in progress, that would be nice, as well as successful and failed builds, so that User #1 and #2 can see what is working, what is not.

        Thanks a lot for your time!


        1. Unknown User (jacob_robertson)

          Julien, try the newly released version 1.11 and see if it does what you want.  I think it will. (also, take a look at the new screenshot on this page under "Filter by Job Parameterization")

          There is one caveat - I don't see version 1.11 showing up yet in my Hudson Update Center - but it does show up if I'm running Jenkins.

          1. Unknown User (foch)

            Thanks Jacob!
            I gave your latest version a quick look, and it (almost) matches my needs! Both parameters "Match against any build in the build history, not just the last build" and "Match against builds in progress" are working :)
            The only drawback is that the view shows the latest result of all builds... For instance if User #1 starts Job1 and it works, then User #2 starts Job1 again with another parameter and it fails, it will appear as failed on User #1's view as well :( Is it possible to show the latest result of the given parameter only?
            Besides the Last Success and Last Failure shown are shared amongst all views. Would it be possible to filter them out?
            Thanks again for your time! This plugin is very valuable to my project!

            1. Unknown User (tgover)

              This plug-in looks really helpful for creating smart-views but I it would really help if in a given view it showed the latest build status that matched the job parameter.

              My use-case is that I have a standard set of test jobs that get run on multiple release and want to create a test view per software release.

              The release is passed as a parameter from the upstream build. This is also used by a post build groovy step in the plugin to label test release on the test job. Otherwise, on the build history for the test job you have no idea what release triggered the test unless you click on the build result.

              1. Unknown User (jacob_robertson)

                After numerous requests for this type of feature, I'm releasing the Build Filter (Wrapper) Column as a new feature for the View Job Filters plugin version 1.18. Please take a look at it, and provide any feedback you might have.

            2. Unknown User (jacob_robertson)

              After numerous requests for this type of feature, I'm releasing the Build Filter (Wrapper) Column as a new feature for the View Job Filters plugin version 1.18. Please take a look at it, and provide any feedback you might have.

              1. Unknown User (epaprasuna)

                I am using  Build Filter (Wrapper) Column with View Job filters V1.27. Using  "Filter by Job Parameterization" on parameter "TargetEnvironment=prod". Using Build Filter (Wrapper) Column selected columns "Last Success", "Last Failure", "last Duration". All the 3 columns are displayed as N/A. Build info is not displayed. 

                Do I need to set any other data to display above 3 columns?

  3. Unknown User (svaret)


    Could I filter jobs based on timestamp of job execution? That is, I would like to search for all jobs that ran between 9:00 and 9:30 2011-06-09 for example.

    Best regards


    1. Unknown User (jacob_robertson)

      That is not currently possible, but I am very interested in implementing this feature for you this weekend.

      To help me out, could you describe your actual business use case for this?  It seems a bit confusing to me, because such a view would be a temporary view, and it would be hard to maintain, which goes against the intent of this filter - making it easier to maintain lots of jobs and views.  I might be misunderstanding your need - which is why it would be crucial for you to describe how you would actually use this new feature in your day-to-day work.


  4. Unknown User (dougborg)

    Maybe I am missing a feature that already exists in this plugin or Jenkins/Hudson in general, but I would like to filter out disabled jobs. Is that possible now? It doesn't seem like it would be too hard to implement and would be useful to a large number of people. Thanks!

    1. Unknown User (dougborg)

      Ahha! I just found it in job statuses.. That was silly of me. Thanks for a great plugin!

      1. Unknown User (jacob_robertson)

        Glad you found it.  Let me know if you have any other comments or questions - I'm paying attention.

  5. Unknown User (rutt)

    I was trying to create a Regular Expression Job Filter with a match value of Job SCM configuration, but doing so always resulted in a java exception when trying to bring up or edit the view - the only way to get back to a working state was to manually edit the Jenkins config.xml. After more digging, it appeared installing Jenkins GIT plugin fixed the issue - is this an unintended depenency?

    1. Unknown User (jacob_robertson)

      I'll look into that.  I tried to test for that condition, but I'll take another look.

    2. Unknown User (jacob_robertson)

      Please upgrade to 1.14.  I have tested this fix, but it would also be nice if you could confirm that it fixes it.

      Thanks for reporting this regression!

      1. Unknown User (rutt)

        I removed the Git plugin and confirmed that I was still getting the same error.  Updated to 1.14 and things are working perfectly.  Thanks!

  6. Unknown User (josbraaksma)

    Hi Jacob,

    I seem to have trouble getting the Regular Expression Job Filter to work for Job Descriptions, I hope you can point me to what I might be doing wrong, or maybe there is a bug that needs resolution.

    On some projects I use the 'Project Description Setter' plugin to set the 'Project description' to "stream=some_stream1".

    In my View I added a 'Regular Expression Job Filter' to 'Include Matched' on 'Job Description' with regex ".*stream=some_stream1.*"

    However, the desired projects do not show up in the view. 

    Are the projects selected at creation time of the filter? In other words, is the filter static, rather than (my expected) dynamic?

    Do the projects need to be successfully build or are there other prerequisites for them to show up in the View? 

    Thanks for your time, 


    1. Unknown User (jacob_robertson)

      I was able to reproduce this - it is a bug with the way the regex filter handles multi-line descriptions.  I created a JIRA issue to track this.


      Look for a fix and a new release of the plugin some time today.

      1. Unknown User (josbraaksma)

        Hi Jacob,

        fix confirmed in v 1.16 :D

        Thanks a lot for your super quick response.

        cheers, Jos

  7. Unknown User (geertpeeters)

    Maybe stupid Question :

    When you define multiple job filter criteria, is it an OR or an AND operation?

    I specified a regular expression .*TEST.* for the job description which contains <div style="display:none">TEST TCL</div>

    that works fine. The jobs with TEST in the description do show up in my view.

    However, if I define an extra job filter with regular expression on job name being .*R11\.0\.1_.* I see all the jobs containing R11.0.1 in their name.

    I was expecting that only jobs containing the word TEST in their description AND R11.0.1 in their name would be shown.

    Apparently it is not the case

    Is this the expected behavior? It would be nice to be able to select the operator being AND/OR in a dropdown list.

    1. Unknown User (jacob_robertson)

      This is a good question, and since you're not the first person to ask, I've started a wiki page that tries to answer this question. Take a look, and see if it answers your questions, and let me know.


  8. Unknown User (damianshameer)


    This thread has been silent for a while but for my sake I hope Jacob still monitors it.

    I followed the instruction above to create a simple view however i'm getting no result in my view.

    My Jenkins instance consists several teams, with one team having many project. My goal is to create a view for each team's project.

    For example, the PRDB team has 5 projects

    PRDB-App1, PRDB-App2, PRDB-App3, PRDB-App4

    I created a new view, selected Job Filter--> Regular Expression:

    Regular Expression: PRDB*

    Match Value: Job Name

    Match Type: Included Match - Add jobs that match this filter.

    This is fairly simple and should work but it is NOT.

    What am i doing wrong? Please assist.




    Jenkins 1.42 installed

    1. Unknown User (jacob_robertson)

      Hi Damian,

      I have two comments regarding your issue.

      First, for what you're trying to accomplish the View Job Filters plugin seems like overkill because there is already a Jenkins core facility of "Use a regular expression to include jobs into the view" that lets you check a box and enter a regex to filter jobs. Of course, if you want additional smart filtering this plugin has a lot to choose from.

      Second, your regular expression you show is probably not correct. What that expression says is to include all jobs that start with "PRD" and then have 0 to infinity "B"s. What you probably meant was "PRDB.*" which would match all jobs starting with "PRDB" and then containing 0 to infinity of any character.

      I hope this helps.


      1. Unknown User (damianshameer)


        "PRDB.*" works!



        PS. I installed the Job Filters plug-in because of the additional filtering functions..I will be exploring the more elaborate filtering options...i just wanted to start small ;-)

  9. Unknown User (kapilanarang)

    Need help here-

    I need to create multiple groups who can login only with their defined view with set of pattern matching jobs. Rest no view to other jobs in other view.
    Found this can be done by View Job filter but hard to track down the steps.What i did is created the group name "ABC" used Matrix-based security  adding group name. When i go to Manage Users-> ABC ->Configure -> Default View name ->which I want to assign something like "Trains". Its gives error- "A view with name Trains does not exist"
    Where Trains is already an existing View. So i can infer is that it is not able to View "Trains" . Where i tried to change in Trains View With Parametrized Job View.

    Can anyone  help where  i am going wrong?

  10. Unknown User (myjenkins911)

    Hi Can you please add a feature to hide views? It will be helpful if I can hide any view including the default "All" view. I do not want to delete or change the default "All" View.

    I am requesting this through a comment because "Enter a JIRA Ticket" link is not valid.



  11. Unknown User (famous_sdk)


     Is there any way to create a view filter programmatically? Either jenkins CLI or API?


  12. Unknown User (uny)

    Hi there,

    Is it possible to filter job view based on Upstream/Downstream jobs, and having the status ball (blue/red) to show the corresponding sub-job status to the MultiJob job (instead of showing the latest job status)? 

  13. Unknown User (ltenka)


    Not sure this is right forum to address - to seek your valuable suggestion.

    I have 7 views with each having 150+ jobs.

    Need to have dash board report for each view with in Jenkins.


    • ·         Number of total builds in the view
    • ·         Failed Builds
    • ·         Success Builds
    • ·         Pie chart with statistics
    •  consolidated count of all the job statistics with in the view

     This report needs to be saved weekly basis in a Pdf format and should be accessible via Jenkins.

     How do we do it with available plugins in Jenkins ?

    I have been trying with plugins

    • 1.       Global stat view
    • 2.       Dash board view

    Having No Luck yet !

    Looking forward for the favourable reply.

    What i did was ,

    applied DashBoard view plugin - and i have job filter view - to get build history of 1 day of jobs from the selected view.

    But it is gathering all history of selected jobs . could you please help

  14. Unknown User (gilk)


    I have a problem with the view

    Lets say I filter jobs by name and I have job x, when I run a build the job appear in the view BUT

    When two or more builds are running in concurrent and the last build end and the other build are still running the job is not shown in the view

    Is this a defect or something that I'm doing wrong.