-
Notifications
You must be signed in to change notification settings - Fork 98
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
Test only supported Odoo versions #189
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The idea look great 👍 ! I'm always OK to reduce the impact of the CI when tests are unnecessary.
About the selection of the version, 13.0 is not a good choice for the time being (and maybe 12.0)
See :
- last V10 commits : https://github.com/odoo/odoo/commits/10.0 : May 18, 2021. (~2 years ago, 🆗)
- last V11 commits : https://github.com/odoo/odoo/commits/11.0 : Jan 20, 2022. (14 monthes ago, 🆗)
- last V12 commits : https://github.com/odoo/odoo/commits/12.0 : Oct 13, 2022 (6 monthes ago, 👍 / 👎 )
- last V13 commits : https://github.com/odoo/odoo/commits/13.0 : Mar 13, 2023 (~10 days ago, totally 🚫 )
as a safe choice, I would therefore propose the following rule:
We can remove the odoo "X.0" branch from the OCA CI, and use only OCB if there is no commit on the "X.0" branch for one year.
So for the time being : 10.0 and 11.0. (and remove 12.0 in October 2023, if no new commits are pushed).
What do you think ?
047327e
to
53d481f
Compare
src/.github/workflows/{% if ci == 'GitHub' %}test.yml{% endif %}.jinja
Outdated
Show resolved
Hide resolved
Thanks for having a look!
I have restored
I would keep excluding
|
53d481f
to
f8d770c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for me makes sense. But I'm not expert of that repo, so other review are welcome.
thanks for the changes !
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. @sbidoul can you please confirm that the makepot change should behave as expected?
I think it would be more flexible to add a copier question to enable odoo and/or ocb tests. |
Good idea, that would be more flexible for sure, I should look up how to do that.
|
I think we can have a question such as "Which Odoo flavor to test?" with 3 possible answers: odoo/OCB/both. |
Right, I forgot that each template is used only for one version at a time 😅 ok then I'll look up how to use the questions to do this. |
Good initiative here. |
f8d770c
to
a54d5da
Compare
🤔 sorry for the multiple review requests, apparently I can't re-request review from both @yajo and @legalsylvain. Anyway, I re-requested the reviews because something changed: now the user can choose what to enable, let me know what you think 😄 |
@SirTakobi does it enable makepot in case OCB only is selected? |
Yes because |
0934527
to
aeb59b9
Compare
@SirTakobi we must ensure to not run makepot twice. So it should appear in OCB jobs only it the flavor is OCB. |
Looking at the code changes, I think it will only be run once; of the three possible choices:
Have you noticed some case in the code that I'm missing? |
Ah, yes, sorry I misunderstood. 👍 |
1 similar comment
Ah, yes, sorry I misunderstood. 👍 |
Thanks! Would you please apply this into one or two repos before we do a release? So we can see it works in the real world. Update to latest unreleased change with:
|
Done in OCA/l10n-italy#3241 |
@@ -76,6 +76,15 @@ ci: | |||
- GitHub | |||
help: Which CI system to use ? | |||
|
|||
odoo_test_flavor: | |||
type: str | |||
default: Both |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to set the default value to OCB for Odoo < 13 ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes that might be useful
but honestly I don't know how to do that, is that even possible? I mean, this is not a jinja template
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We already have default: "https://github.com/{{ org_slug }}/{{ repo_slug }}"
so we probably can put any python expression in there?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, you can do that.
Yes that might be useful
…On Tue, Mar 28, 2023 at 11:23 AM Stéphane Bidoul ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In copier.yml
<#189 (comment)>
:
> @@ -76,6 +76,15 @@ ci:
- GitHub
help: Which CI system to use ?
+odoo_test_flavor:
+ type: str
+ default: Both
Do we want to set the default value to OCB for Odoo < 13 ?
—
Reply to this email directly, view it on GitHub
<#189 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AYHLQYGSE3LRMHAE257GCQDW6KUZXANCNFSM6AAAAAAWFKKRPQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Implementing what suggested in
Originally posted by @pedrobaeza in odoo/odoo#115782 (comment)
The issue fixed in the linked PR is blocking many good PRs in
12.0
out there.Here I allow to choose if tests should be executed in Odoo/OCB.
I don't know how to test this locally so I just wrote what seemed appropriate, any feedback is appreciated.
I tried removing the old
.copier-answers
from a repository andcopier /path/to/oca-addons-repo-template .
but it isn't using the edited template that I have locally.