[JIRA] (JENKINS-56813) Job filter: exclude disabled jobs does not work

1 view
Skip to first unread message

jenkins@mockies.de (JIRA)

unread,
Mar 29, 2019, 2:01:03 PM3/29/19
to jenkinsc...@googlegroups.com
Christoph Vogtländer created an issue
 
Jenkins / Bug JENKINS-56813
Job filter: exclude disabled jobs does not work
Issue Type: Bug Bug
Assignee: Sven Schoenung
Components: view-job-filters-plugin
Created: 2019-03-29 18:00
Environment: Windows 2012 Server
Jenkins ver. 2.150.3
Priority: Minor Minor
Reporter: Christoph Vogtländer

When defining a job filter on a view, using the "Job-Status" filter with "Disabled" and type set to "Exclude matching", will still show disabled jobs.

E.g. define two filters:

  1. All jobs (or regular expression where the expression includes some disabled jobs)
  2. Job-Status: Disabled, Filter-type: Exclude matching

Including disabled jobs seems to work fine.

Strangely, when using two "Job-status" filters, the exclude filter works as expected:

E.g.:

  1. Job-status: disabled, Filter-type: include matching
  2. Job-status: disabled, Filter-type: exclude matching

will result in an empty list which is correct.

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

jglick@cloudbees.com (JIRA)

unread,
Apr 1, 2020, 1:21:04 PM4/1/20
to jenkinsc...@googlegroups.com
Jesse Glick resolved as Not A Defect
 

To create a view showing all enabled jobs, add a Job Statuses Filter with Disabled checked and select Include Unmatched - Add jobs that don't match this filter. Do not select jobs or check the regular expression filter option. Or you can use the core built-in filter without using this plugin. See JENKINS-51143 for a fuller explanation.

Using a GUI to define a boolean predicate is not great, and the particular way this is handled in Jenkins list views is especially confusing.

Change By: Jesse Glick
Status: Open Resolved
Resolution: Not A Defect
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages