Deploying from Travis

[richardjgowers]

It looks like we could set it up so that after (successfully) pushing to master branch we could get travis to push to pypi for us.

https://docs.travis-ci.com/user/deployment/pypi/

Does anyone see any problems using this?

[kain88-de]

no that would be pretty awesome.

[orbeckst]

We could also update the doc deployment.

1. At the moment, devdocs are deployed with the maintainer/deploy_docs.sh script from travis

   mdanalysis/.travis.yml

   Line 113 in 8bab359

   - if [[ ${TRAVIS_PULL_REQUEST} == "false" ]] && [[ ${BUILD_DOCS} == "true" ]] && [[ ${TRAVIS_BRANCH} == ${GH_DOC_BRANCH} ]]; then

2. And the master docs are manually deployed by either @richardjgowers or me with the maintainer/deploy_master_docs.sh script (see also PR add sitemap.xml to sphinx docs #1890 on that process).

For pytng @kain88-de and @richardjgowers have used Travis gh-pages deployment in the .travis.yml file, which is cleaner than deploy_docs.sh.

[orbeckst]

Does anyone see any problems using this?

One possible issue is that you have one less chance to catch a buggy release before it gets out.

[richardjgowers]

So the only extra step I do that travis doesn't for a release is I build the source distribution, upload it to testpypi, then download and test that version of things. We could probably wrap that whole process into a script and then theoretically travis has replaced me!

[orbeckst]

The different automation options on travis are pretty cool... maybe

• build artifacts: perhaps we can use this to upload a tarball of the docs (docs tarball missing from 0.16.0 release #1353 )
• automatically tweet the release ;-) with Running commands after release

[IAlibay]

Deployment via CI is now done via gh actions.