Skip to content
This repository has been archived by the owner on Sep 16, 2024. It is now read-only.

runbot_travis2docker: does not seem to work on OCA runbot #105

Closed
gurneyalex opened this issue Nov 7, 2016 · 43 comments
Closed

runbot_travis2docker: does not seem to work on OCA runbot #105

gurneyalex opened this issue Nov 7, 2016 · 43 comments

Comments

@gurneyalex
Copy link
Member

I probably got some configuration wrong.

I'm using docker 1.6.2 (from jessie-backports), the user running odoo is a member of the docker group (but odoo is not running inside docker).

Test repository is https://runbot.odoo-community.org/runbot/repo/github-com-vauxoo-dev-runbot-branch-remote-name-grp-feature2-232

Setup:

screenshot from 2016-11-07 17-39-14
I get empty builds or skipped builds, docker ps says nothing, and docker images is also empty.

Weird line in the logs:

2016-11-07 16:23:12,856 4580 INFO openerp-oca-runbot openerp.addons.runbot_travis2docker.models.runbot_build: Dockerfile without TESTS=1 env. Skipping builds [3271674]
@gurneyalex
Copy link
Member Author

@moylop260 your feedback is very welcome on this. Thanks for your help.

@moylop260
Copy link
Contributor

moylop260 commented Nov 7, 2016

What is your travisfile2dockerfile --version?

@lasley
Copy link
Contributor

lasley commented Nov 7, 2016

The Travis file needs to be upgraded to the new version. This error is saying there is no "TESTS=1" in the matrix, which is defaulted so doesn't hurt Travis.

Happens all the time on our instance, which is why you see me submitting new Travis files quite often. You can see the transition on our web repo. Skipped are all before merge of OCA/web#447 or OCA/web#448

Although @moylop260 comment maybe alludes to this being fixed in a newer T2D version?

@moylop260
Copy link
Contributor

@gurneyalex
I'm using the following runbot.repo configuration:
docker

It's building here:
http://runbot.vauxoo.com/runbot/repo/https-github-com-vauxoo-dev-runbot-branch-remote-name-grp-feature2-git-90

I don't see the url in the image of your first comment but could change it by:
https://github.com/vauxoo-dev/runbot_branch_remote_name_grp_feature2.git

NOTE: The docker version is too old this could get new errors by old bug but Its is other matter.

@moylop260
Copy link
Contributor

@lasley
Thanks for the information.

For this case we are using a .travis.yml file upgraded:

https://github.com/vauxoo-dev/runbot_branch_remote_name_grp_feature2/blob/ac681dcb4cfcbb8df9c26ed8cadf8e4c837f21be/.travis.yml#L21-L27

@lasley
Copy link
Contributor

lasley commented Nov 7, 2016

Yup that Travis should definitely not be exhibiting this issue 😦

@gurneyalex
Copy link
Member Author

@moylop260

$ bin/travisfile2dockerfile --version
travisfile2dockerfile 3.0.8

@moylop260
Copy link
Contributor

moylop260 commented Nov 8, 2016

@gurneyalex
Could you share me a screenshot of runbot.repo record but without edition mode, please? (To show the full url)

@moylop260
Copy link
Contributor

@gurneyalex
Copy link
Member Author

@moylop260 I think the problem comes from gurneyalex/odoo-extra@92b578a which is installed on our instance : the screenshot shows the configured URL (without the https:// prefix which is added by that patch, and your addon expects a full URL.

@moylop260
Copy link
Contributor

@gurneyalex Thanks for the information
Fix #106

@gurneyalex
Copy link
Member Author

@gurneyalex
Copy link
Member Author

@moylop260 at lease 1 build worked. Are the failures on the other branches expected ?

@moylop260
Copy link
Contributor

moylop260 commented Nov 14, 2016

Yeah, we have currently the following issue
OCA/maintainer-quality-tools#384 (Installing just base show that error)

Showing in travis too the same error:
travis-build-OCA/maintainer-quality-tools#384

Then it is not a runbot or travis2docker error. It is a MQT expected fail.
borrar

IMHO we are ready (We don't have real projects installing just base)

@moylop260
Copy link
Contributor

We could use a "technical" real repository like as server-tools

I'm testing it from custom instance using all the patches and It is working fine:

server-tools

@gurneyalex
Copy link
Member Author

gurneyalex commented Nov 15, 2016

Yesterday I enabled docker builds for

  • rma (5 instances running on docker at the moment)
  • server-tools (7 instances)

@gurneyalex
Copy link
Member Author

gurneyalex commented Nov 15, 2016

I just enabled

  • account-financial-tools
  • web
  • website

For now all of them have the tests disabled (same for rma and server-tools).

cc @moylop260 @lasley

@lasley
Copy link
Contributor

lasley commented Nov 15, 2016

Hmmm looks like the new version isn't appending the log to DB. I admittedly haven't updated my Runbot since before the code sprint, so I haven't functionally tested our improvements outside of local. I'll update today and see what's wrong.

@lasley
Copy link
Contributor

lasley commented Nov 15, 2016

Fix is in #107 - seems my PEP8ing after test and before PR ended up changing the end result of the .format. My bad on that, I was going a lot of directions during the code sprint

@moylop260
Copy link
Contributor

To see the logs we need a log.warning or a log.error into of a build.
But I don't found the first one with this log.

How are you checking this issue?

@moylop260
Copy link
Contributor

I found a warning in a runbot build but is not enabled for docker.
The branch 8.0 of https://runbot.odoo-community.org/runbot/repo/github-com-oca-l10n-switzerland-125

@gurneyalex
Could you help us to enable it in this project in order to confirm a issue with the logs?

@gurneyalex
Copy link
Member Author

gurneyalex commented Nov 16, 2016

added

  • carrier-delivery
  • product-*
  • stock-*
  • community-data
  • l10n-switzeland (cc @moylop260 I triggered a rebuild of the 8.0 branch)

@moylop260
Copy link
Contributor

I saw in stock-* project the following error (and fix): OCA/maintainer-quality-tools#386

@moylop260
Copy link
Contributor

moylop260 commented Nov 17, 2016

I saw in l10n-switzerland project the following error (and fix): Vauxoo/docker-odoo-image@3eaae03

(This change require run the following command in the oca server: `docker pull vauxoo/odoo-80-image-shippable-auto`)

TODO: Use the parameter --pull from runbot-addons to auto-pull the big image in each change.

@moylop260
Copy link
Contributor

TODO: Use the parameter --pull from runbot-addons to auto-pull the big image in each change.

Fixed from #109

@lasley
Copy link
Contributor

lasley commented Nov 21, 2016

Gotta love the edge cases that crop up when launching at scale 😉

@lasley
Copy link
Contributor

lasley commented Nov 22, 2016

@gurneyalex - We made some changes that will resolve the issues we've been seeing. Edit: it may only be this issue now that I think about it

Would you mind doing a pip install git+https://github.com/Vauxoo/travis2docker.git to grab the new version of T2D that includes Vauxoo/travis2docker#77?

We'll also need to update the runbot addon to the new version merged in #109.

@gurneyalex
Copy link
Member Author

I'm sorry I can't today. I'll try hard tomorrow.

@gurneyalex
Copy link
Member Author

@lasley @moylop260 I've just updated the runbot as requested

@moylop260
Copy link
Contributor

Thank you
T2d upgrade is required too
pip install git+https://github.com/Vauxoo/travis2docker.git
Please

@gurneyalex
Copy link
Member Author

@moylop260 I did this. Running 99680477d329aee2e54b9cf512531479cd118920 (which is on 3.0.8).

@gurneyalex
Copy link
Member Author

maybe I'm catching an outdated version. Can you make a 3.0.8 release and publish it on pypi ? It's way easier for me due to the way the runbot is deployed to use published documented versions rather than github heads.

@moylop260
Copy link
Contributor

I'll do it
Thank you

@moylop260
Copy link
Contributor

Someone is wrong
All builds are skipping
I'll check it

@moylop260
Copy link
Contributor

moylop260 commented Nov 23, 2016

With the following environment:

  • runbot-addons
~/runbot-addons (9.0-OCA-installation)$ git log -r -2
commit 33e5a2abb43cbd24b738d79d18964de7c3f17997
Merge: 251dc63 092e6f8
Author: Alexandre Fayolle <[email protected]>
Date:   Wed Nov 23 15:01:53 2016 +0100

    Merge remote-tracking branch 'origin/9.0' into 9.0-OCA-installation

commit 092e6f889b252f82cc2abd1bfb87f6443a37bf5b
Merge: 8044166 b0a5635
Author: Pedro M. Baeza <[email protected]>
Date:   Mon Nov 21 18:30:03 2016 +0100

    Merge pull request #109 from vauxoo-dev/9.0-oca-pull-img-moy

    [REF] runbot_travis2docker: Auto pull image for long-term updates
  • travis2docker
pip install --upgrade travis2docker==3.0.9
travisfile2dockerfile --version
travisfile2dockerfile 3.0.9
  • Result:

It's not skipped
screen shot 2016-11-23 at 12 15 16 pm

Do you have a logger error?

@moylop260
Copy link
Contributor

moylop260 commented Nov 24, 2016

@gurneyalex The odoo-extra have the patch of the https// applied yet, right? (I don't have other idea)

@moylop260
Copy link
Contributor

@gurneyalex Tell me if I can help...

@gurneyalex
Copy link
Member Author

I'm sorry I was away yesterday. I just updated the runbot. I'll monitor carefully the builds in the coming hours

@gurneyalex
Copy link
Member Author

@moylop260 Things seem to be a bit better. My build on OCA/web#498 was correctly processed.

@lasley
Copy link
Contributor

lasley commented Nov 25, 2016

@gurneyalex - I rebuilt all of the website builds that were skipped, and we seem good to go. And in even better news, OCA/website#284 now works so that means the RVM install is working too!

@moylop260
Copy link
Contributor

I saw in stock-* project the following error (and fix): OCA/maintainer-quality-tools#386

I rebuilt https://runbot.odoo-community.org/runbot/build/3273461 and now is working

I saw in l10n-switzerland project the following error (and fix): Vauxoo/docker-odoo-image@3eaae03

I rebuilt https://runbot.odoo-community.org/runbot/build/3273217 and now is working
(We have other unrelated error fixed here: OCA/l10n-switzerland#284)

@moylop260
Copy link
Contributor

@gurneyalex
Could we enable travis2docker in other projects?

@gurneyalex
Copy link
Member Author

@moylop260 I just enabled travis2docker on all projects.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants