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

Cross-repo bisect: expose or push synthetic repositories #872

Open
xmo-odoo opened this issue Apr 18, 2024 · 0 comments
Open

Cross-repo bisect: expose or push synthetic repositories #872

xmo-odoo opened this issue Apr 18, 2024 · 0 comments
Labels

Comments

@xmo-odoo
Copy link
Collaborator

Thought I already had a task for this but couldn't find it so here goes: one thing that's really annoying when bisecting or bugdiving Odoo is it's hard to know what commits go together. With access to the runbot backend it's possible to check the staging heads but there's no easy way to feed that to bisect so you need to bisect by hand, and for large stagings the ganularity is low.

What should be achievable is to reify each staging / batch as a commit in a project-level repo, where each actual repo within the project is a submodule. This would have to be chained through the stagings (and batches) and thus somewhat expensive to compute, but afterwards it's just a matter of building the relevant commit(s) on the previous successful staging during staging.

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

No branches or pull requests

1 participant