-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Use deployment primitives from travis #843
Conversation
This looks good to me ping @containous/traefik |
Needs a rebase |
@errm if you are talking about multi-commit, maintainers can merge by squashing commits ;) |
No just the branch was stale... |
Ping @containous/traefik, we need a review on this ;) |
@guilhem needs a rebase. How could we test that though ? |
@guilhem are you sure that the behavior is the same in the case of a pull request ( |
Yeah looks like the behaviour from |
@errm @emilevauge Yes, I didn't replicated https://travis-ci.org/containous/traefik/jobs/181516876#L1946 |
humm... |
@emilevauge I think I've found the problem. |
@emilevauge but https://travis-ci.org/containous/traefik/jobs/182320106#L2085 fail :) Travis Job you point was after merging so inside a "secure" branch (master) |
But maybe we want to have a rolling docker for each commit pushed inside "master" |
Yes, check the merge build, not the pull request build: https://travis-ci.org/containous/traefik/jobs/182236245#L2087 |
@emilevauge should be ok. Plus:
|
@guilhem I don't think creating a Docker image by commit is a good idea. Usually, we need to atomically take the whole pull request to get it working. Could you rollback to the old behavior? |
@emilevauge docker image is pushed not by commit, but with "latest" commit (the merged if there is one). |
Oops, you right ;) |
gentleping @containous/traefik |
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 🐸
@guilhem could you rebase and squash your commits 👼
@vdemeester done :) |
@guilhem do you know why tests are failing ? |
@emilevauge no idea. can you try to re-run failing tests? |
@guilhem I relaunch the tests 2 times and still the same result :'( |
@emilevauge I think bug come from Solutions can be:
|
it works with docker 1.10 and 1.12 |
@guilhem we agree with @vdemeester to remove Docker 1.9 support :) |
@emilevauge I'm in holiday right now, but I will do this for Monday before meetup ;) |
fast_finish: true | ||
include: | ||
- env: DOCKER_VERSION=1.10.3 | ||
- env: DOCKER_VERSION=1.12.5 |
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.
Should be 1.12.6
👼
We could also add 1.13.0
but let's do that in a follow-up 👼
@vdemeester rebased, squashed, fixed etc |
only on 1 environment that was working before :( |
@vdemeester, any idea on what's going on here ? |
Hum I don't see in the failed build but it might be a weirdiness with how the test is written — if the run is particularly slow it might fail 😓 . I'll take a look. |
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.
OMG it's green 🙄
OSS is 10% inspiration, 90% restarting failed CI builds until they randomly work
— Nolan Lawson https://twitter.com/nolanlawson/status/802309792349855744
LGTM
Thanks a lot @guilhem 👍
Need advice on this.
I may go further to improve building