-
Notifications
You must be signed in to change notification settings - Fork 25
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
Automated bisection base coverage #260
Comments
@VinceHillier Here's the Jenkins settings section from "jenkins_options": {
"url": "https://bot.staging.kernelci.org/",
"user": "bisection",
"bisect": "lava-bisection",
"token": "<TOKEN>",
"bisection-git-trees": ["gtucker"]
}, Similarly, please add this item in the file used in production before doing the Monday update: "bisection-git-trees": ["kernelci", "mainline", "next", "stable", "stable-rc"] The same list of trees is already configured in the Jenkins The bisection Jenkins runner appears to have been enabled again already in I think that's all that's needed, we should then start to see bisections for these trees only in the Jenkins queue when regressions get detected. Probably we could artificially create one on the |
Dedicated VM enabled, jenkins showing node status online, will check tomorrow if any jobs queued |
OK at least one bisection job completed in production about 8h ago:
|
After reducing the costs when moving to the new Azure subscription, automated bisections were disabled in order to keep costs in a safe zone. We've now evaluated the costs of running the dedicated VM for bisections again and have agreed on a way forward by only enabling it on mainline, linux-next, stable and stable-rc trees.
The plan is to have this done for next Monday's production update:
The text was updated successfully, but these errors were encountered: