Contributors mailing list archives
Re: Prevent 2 modules from testing together in OCA repo.by
Acsone SA/NV, Stéphane Bidoul
In general you should avoid modifying repo-level dotfiles such as .travis.yml manually, so they can be kept in sync with the template automatically.
The correct way to test some modules independently from others is to run "copier update" and answer the rebel_module_groups question.
This will generate the correct Travis configuration and will be compatible with the future GitHub actions config too.
So, for example, if you answer ["a", "b,c"], it will create 3 groups to test
- a alone
- b and c only
- all the modules in the repo except a, b, c
On Sat, Jul 17, 2021 at 5:57 PM Kitti Upariphutthiphong <email@example.com> wrote:
Yes, this is exactly what I am looking for.Thank you Kevin!On Sat, Jul 17, 2021 at 8:12 PM Kevin Khao <firstname.lastname@example.org> wrote:Hi Kitti,Here is an example of how I did it.https://github.com/OCA/purchase-workflow/pull/1213/files#diff-6ac3f79fc25d95cd1e3d51da53a4b21b939437392578a35ae8cd6d5366ca5485R23On Sat, Jul 17, 2021 at 7:27 AM Kitti Upariphutthiphong <email@example.com> wrote:Hello,When we have 2 module that's will failed when tested together. In OCA repo, are there ways to ensure not to run tests together?I remember it is about setting in travis.yaml? but can't find the sample. (Also in the future if we move to github action, how to?Thank you,
Ecosoft Co. Ltd., Kitti Upariphutthiphong