Syncing from upstream odoo/runbot (18.0-min-max-version-xdo) #819
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adds the missing field `config_data` to trigger's form view.
`target="new"` had the very confusing behavior of updating the same tab within the same browser context (tab). The commit replaces all `target="new"` occurences with `target="_blank"` within the runbot templates. See: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/a#target
The previous fix in c9e8e13 was not enough, while preventing a crash of the view, the view was empty.
bundle_id is not computed anymore
When the reference build for some build is not done yet a message is logged with a link to the referenced build, however due to a typo in the message the markdown was badly formatted.
- Add dropdown-toggle to the github tool button so that it doesn't appear as if a button should be following it. - Add default btn classes to category icons, the button would otherwise be displayed as just an icon. - Add a gap between the two toolbars. - Add d-empty-none in case we have no category to display to remove the useless gap.
Allows searching branch through pr url or full branch name. Also fixes a crash when searching invalid values.
While it's useful to have a clickable link to the fixing pull request on the runbot error list, we cannot display the entire url as it takes too much space. So a static text `View PR` is used. As this static text is of limited use, this commit adds a new widget that displays a shortened URL for the github pull request only showing the repo and the PR number.
Supports the format (?owner)/repo#id in the `_search_dname` method.
`record._cr` is being deprecated in odoo/odoo#193636 this commit replaces the old `._cr` with `env.cr`.
Exceptions and their followups are managed by their managers, this will prevent having to create a custom filter to get our own exceptions.
The current qualifying implementation is based solely on error content. With this commit the fields on which the regular expression will apply can be choosen with checkboxes. It defaults to the `content` field.
Removes auto tags from a build if the build's branches match the build error's fixing branch.
fix typos, and grammatical mistakes
fix URL to change the master password.
The row_number window function is quite unoptimized as it requires reading the whole table. Using lateral join and / or distinct makes better use of existing indexes.
Looks like bu.database_ids[1:].sorted('name') was breaking the prefech
set leading to one query per build. Fiwing it by sorting without slicing
the ignoring the first record.
~230 ms improvement over 1.7 second
The corresponding fields are stored on the build, no need to read the params.
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
Just as useful as tracking the test-tags itself.
Before this commit: The only way to have details on the builds was to use the embed one2many widget in the build error form view. This was pretty inconvenient for complicated search as there is no way to filter the records or group them After this commit: A list view now exist for the model `runbot.build.error.link` allowing to filter and group on convenient fields. This list view can be accessed on the runbot build error through a smart button
Xavier-Do
force-pushed
the
18.0-min-max-version-xdo
branch
from
c3220bd to
6ec1d4e
Compare
Xavier-Do
force-pushed
the
18.0-min-max-version-xdo
branch
from
6ec1d4e to
9377df5
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
bt_gitbot