Closed bak1an closed 8 years ago
Good catch!
Sadly this seems to be a side effect of the way we use tox on Travis-CI and I'm not sure if they would ever add a "all-passed" condition since the conditions are evaluated per environment.
Yeah, it seems that there are no easy solution to this. People are doing hacks for this but I am not sure if it is worth it in this particular case.
Most likely the person that is about to push a new release is going to spin off the tox
command locally before creating tag anyway.
Ough, messy. I'd rather not have to maintain a big Travis config, to be honest, so we'll have to live with the imperfect. We can revisit when Travis-CI has fixed this.
At the moment every build in matrix (for tagged commits of course) attempts to do the deployment.
Example: https://travis-ci.org/jazzband/django-hosts/builds/96972410
As we can see
#101.1
has deployed the release to PyPI, while other six builds in the matrix failed to do so with:This seems to be easy to fix using conditional releases. We just need to select one tox env that will be responsible for deploying.
More accurate solution would be to deploy only when all builds are finished. However, I have not found the solution for this yet.
The similar procedure can be done for other repositories under jazzband.