Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New command to list jobs failing by view #13

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

gjolly
Copy link
Contributor

@gjolly gjolly commented Apr 20, 2023

This is way faster than relying on regexp and is super useful to quickly identify failing jobs

@@ -103,6 +103,11 @@ def _parser():
parser_jobs_failing.add_argument('pattern', metavar='pattern', help='the Jenkins job name(s) (regex)')
parser_jobs_failing.add_argument('--max-score', '-m', default=0, type=int, help='the maximum health score to look for')
parser_jobs_failing.set_defaults(func=jobs_failing)
# jobs failing by view
parser_jobs_failing_by_view = subparsers.add_parser(
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could that be included in jobs-failing eg. with jentool jobs-failing --use-view my-view-name ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So it's not that simple because get_jobs and get_jobs_info_regex do not take the same parameters nor return the same values. For example, get_jobs_info_regex doesn't let you filter by views and it returns the score in the info dict while get_jobs doesn't.

This is way faster than relying on regexp and is super useful to quickly
identify failing jobs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants