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

Syncing from upstream odoo/runbot (18.0-upgrade-refactoring-xdo) #820

Open
wants to merge 12 commits into
base: 18.0-upgrade-refactoring-xdo
Choose a base branch
from

Conversation

bt-admin
Copy link

bt_gitbot

Xavier-Do and others added 12 commits February 21, 2025 10:52
This allows to configure a custom trigger to use the base commits.
This can be usefull to test a config on a branch that has some changes
to ensure it works proprely.
- Fix the model on parse_logs action window.
- Add a server action on build to open its errors
- Fix a bad indentation
This commit adds a `common_qualifiers` field on build error. Its purpose
is mainly to find similary qualified errors and similary qualified error
contents. This field is computed by finding qualifiers in common in all
the qualifiers of the error contents linked to the error.

A new `unique_qualifiers` is also added for the same kind of puprpose.
This field is computed by finding non contradictory qualifiers of the
linked error contents.

The fields can be used in 4 tabs added on the build error form.
Makes it possible to filter on host on the load_info view.
Monitoring was also adapted to have links to filtered load_info page.
When adding an internal link in discord or other platform, a preview of
the login page is given. This is not usefull nor elegant.

This commit proposes to remove the logo and give useful information
instead
The initial way to configure upgrades was working fine and automatically
but does not alway match the reality of what should be supported.

Saying, upgrade from the last main version and last intermediate
(for 18, from 17.0 and 17.4) we may also want to test from 17.2 because
for some reason there are many people in 17.2 taht will need to upgrade
in 18.0. But the transition 17.2->17.3 doesn't make sense anymore
after a while since people will go in 18 imediatly at some point.

This matrix can be generated automatically from the parameters and new
versions should appear automatically, but it is possible to tweak the
values on demand.
Since only reference_batch from the same category are stored, it makes
senses to limit the complement trigger to the same category.
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.

4 participants