Skip to content

kci config: Implement pipeline job forecasting tool #2920

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

nuclearcat
Copy link
Member

Often we need to know, what builds and tests will be triggered on each checkout. We can add option to kci to "forecast" these builds, for example:
./kci config forecast -c ../kernelci-pipeline/config

@nuclearcat
Copy link
Member Author

Moved from kernelci/kernelci-pipeline#1225

@nuclearcat nuclearcat force-pushed the add-config-forecast branch 3 times, most recently from 0cd7c25 to c037b8a Compare July 3, 2025 10:28
Often we need to know, what builds and tests will be triggered on
each checkout. We can add option to kci to "forecast" these builds,
for example:
./kci config forecast -c ../kernelci-pipeline/config

Signed-off-by: Denys Fedoryshchenko <[email protected]>
@nuclearcat nuclearcat force-pushed the add-config-forecast branch from c037b8a to bb7a15a Compare July 3, 2025 10:31
for checkout in checkouts:
checkout["kbuilds"] = []
# iterate over events (jobs)
jobs = merged_data.get("scheduler", [])
Copy link
Collaborator

Choose a reason for hiding this comment

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

Does it include configs from different scheduler files such as scheduler-cip.yaml and scheduler-chromeos.yaml?

continue
job_name = job.get("job")
job_kind = merged_data.get("jobs", {}).get(job_name, {}).get("kind")
if job_kind == "kbuild":
Copy link
Collaborator

Choose a reason for hiding this comment

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

From the PR description, it looks like tests forecast will also be part of this PR. Maybe it's still under development?

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