Contributors mailing list archives
contributors@odoo-community.org
Browse archives
Re: Issues with Travis
by
Acsone SA/NV, Stéphane Bidoul
Hi Holger,
Yes that approach can work too.
TBH, I was hoping to take the occasion of moving out of travis to simplify things a little bit.
A few weeks ago I had progressed with my experiment and these days we are testing it in the Shopinvader organization.
It looks like this:
- docker images with Odoo pre-installed that are rebuilt nightly with the latest Odoo (inspired from the latest runbot Dockerfile template)
- 3 very simple scripts to install addons and their dependencies, initialize the test database and run tests
- a minimalist GitHub action that orchestrates the thing (example a in Shopinvader repo)
It's lean, seems to work well and is pretty fast, as the installation step is reduced to the minimum (i.e. downloading the docker image).
In terms of the general mechanics, I have only one open question: can we rely on the Odoo exit code to detect test failure or do we still need a log parser ?
And the missing part is the small step that pushes .pot updates to git after test success.
If people agree, the rough next steps I would propose would be as follow:
- move the oca-ci repo with the container images to OCA
- add OCB builds of the oca-ci containers
- update oca-addons-repo-template with the test workflow for the 14.0 branches
- deploy it to the 14.0 branches, in parallel with Travis, and configure the merge bot to ignore the GitHub actions failures: this step will let people test it, find corner cases etc
- when all good and when runbot is ready to work without runbot_travis2docker, remove travis on the 14.0 branch
- think about older branches: the concept will work, I'm sure (I've tested 10, 12, 13, 14 and 8 should work too), but the deployment has to be organized
-sbi
On Wed, Feb 17, 2021 at 10:57 PM Holger Brunn <mail@hunki-enterprises.com> wrote:
> (some ideas in an example here > https://github.com/acsone/mis-builder/pull/3). I'm working on something more in line with current MQT in https://github.com/hbrunn/social/actions/runs/576195231 which looks pretty promising to me. Speed is an issue here, but I think this can be improved with more caching. Where should we discuss which way to go? Maybe better on an issue on MQT? -- Your partner for the hard Odoo problems https://hunki-enterprises.com_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
