-
New Feature
-
Resolution: Unresolved
-
Major
-
None
We know that certain types of failures are only going to occur on certain kinds of jobs. Especially when a mulit-line can is required, it is ideal if we an limit what jobs are scanned for a particular cause. Obvious ways to limit a job scanning are as follows:
- By job label.
- By Name (regex pattern match against name)
- By job Type (maven, free style, etc.)
- By what folder or view the job appears in.
Some of these ideas are harder to implement than others and probably deserve their own ticket. The first two are easy and likely give the most ROI.
I assume that the main driver for this idea is to spend less time and resources on scanning?
Sounds like a good idea and I agree, the obvious place to start is with the easy implementations e.g. job name.