Skip to content
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

Split pypi and docker travis tasks #480

merged 1 commit into from Jul 7, 2019


None yet
2 participants
Copy link

commented May 19, 2019

Resolves #478

This should work, but because this is a change that'll only really be testable on a) this repo, b) master branch, this might fail fast if I didn't get the configurations right.

Looking at #478 it should just be as simple as splitting out the docker and pypi processes into separate jobs, but it might end up being more complicated than that, depending on what pre-processes the pypi deployment needs, and how travisci treats deployment steps without scripts in general.


This comment has been minimized.

Copy link

commented May 20, 2019

Thanks for this - looks like exactly what I wanted. I'll test this next time I ship a minor release.

@simonw simonw added this to the Datasette 0.29 milestone Jul 7, 2019

@simonw simonw merged commit d950480 into simonw:master Jul 7, 2019

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed

simonw added a commit that referenced this pull request Jul 7, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.