Skip to content

Add support to fetch a single success job by setting a flag #101

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

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

Conversation

Shilpa-Gokul
Copy link
Collaborator

This change is useful when you have to find a success job in a particular release to qualify that the release image is proper. Hence adding a new flag to support fetching one success job and ignoring all others

shilpagokul@Shilpas-MacBook-Pro ci-monitoring-automation % python3 CI_JobHistory.py -h
usage: CI_JobHistory.py [-h] [--zone ZONE] [--job_type {p,z,pa}] [--filter FILTER] [--fetch_one_success_job]

Get the job history

options:
  -h, --help            show this help message and exit
  --zone ZONE           specify the lease/zone
  --job_type {p,z,pa}   Specify the CI job type (Power(p) or s390x(z) or Power Auxillary(pa)), default is p
  --filter FILTER       Specify the filter string to fetch jobs (Example heavy build / libvirt / powervs / upgrade / 4.14 / 4.15 / 4.16 / 4.17/ 4.18 )
  --fetch_one_success_job
                        Set this flag to check job runs until one success job is found
shilpagokul@Shilpas-MacBook-Pro ci-monitoring-automation %
shilpagokul@Shilpas-MacBook-Pro ci-monitoring-automation % python3 CI_JobHistory.py --filter 4.18 --fetch_one_success_job
1  4.17 to 4.18 upgrade
2  4.18 libvirt
3  4.18 libvirt multi
4  4.18 powervs capi
5  4.18 heavy build
6  4.18 heavy build multi
7  4.18 agent
8  4.18 to 4.19 upgrade
9  All the above
Select the required ci's serial number with a space 2
Please select one of the option from Job History functionalities:
1. Check Node Crash
2. Brief Job information
3. Detailed Job information
4. Failed testcases
5. Get builds with testcase failure
6. Get testcase failure frequency
7. Get build based on release
Enter the option: 7
Enter the release: 4.18.0-rc.8
Enter the next release (provide latest if no next release): latest
Checking runs from 2025-02-06 19:47:41 to 2025-02-12 13:34:11.501246
--------------------------------------------------------------------------------------------------
4.18 libvirt
1 Job link:https://prow.ci.openshift.org//view/gs/test-platform-results/logs/periodic-ci-openshift-multiarch-master-nightly-4.18-ocp-e2e-ovn-remote-libvirt-ppc64le/1889320486635048960
Nightly info- registry.ci.openshift.org/ocp-ppc64le/release-ppc64le:4.18.0-0.nightly-ppc64le-2025-02-11-142433
Lease Quota- libvirt-ppc64le-2-0
All nodes are in Ready state
No crash observed
All conformance testcases passed
Failed monitor testcases:
1. API LBs follow /readyz of kube-apiserver and stop sending requests before server shutdowns for external clients
All symptom_detection testcases passed


2 Job link:https://prow.ci.openshift.org//view/gs/test-platform-results/logs/periodic-ci-openshift-multiarch-master-nightly-4.18-ocp-e2e-ovn-remote-libvirt-ppc64le/1889229981142224896
Nightly info- registry.ci.openshift.org/ocp-ppc64le/release-ppc64le:4.18.0-0.nightly-ppc64le-2025-02-11-082433
Lease Quota- libvirt-ppc64le-1-2
All nodes are in Ready state
No crash observed
ERROR


3 Job link:https://prow.ci.openshift.org//view/gs/test-platform-results/logs/periodic-ci-openshift-multiarch-master-nightly-4.18-ocp-e2e-ovn-remote-libvirt-ppc64le/1889138935813115904
Nightly info- registry.ci.openshift.org/ocp-ppc64le/release-ppc64le:4.18.0-0.nightly-ppc64le-2025-02-11-022433
Lease Quota- libvirt-ppc64le-1-2
No crash observed
Build Passed
Found a passed job, hence ignoring subsequent jobs

3/13 deploys succeeded
1/13 e2e tests succeeded
--------------------------------------------------------------------------------------------------
shilpagokul@Shilpas-MacBook-Pro ci-monitoring-automation %

@ppc64le-cloud-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Shilpa-Gokul

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants