CI: Move PyPI deployment to Circle

[effigies]

Closes #2313.

Changes proposed in this pull request

• Moves PyPI deployment to CircleCI

The Travis builds are a little weird in that, on tagging, the first to successfully complete will upload to PyPI, while the rest will fail. This seems unnecessary, and we might as well use the dependencies allowed by Circle 2.0 workflows.

This will need @satra's PyPI credentials stored properly in Circle before it makes sense to merge.

Testing everything but the twine upload.

[codecov-io]

Codecov Report

Merging #2587 into master will increase coverage by 0.3%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master    #2587     +/-   ##
=========================================
+ Coverage   67.27%   67.57%   +0.3%     
=========================================
  Files         335      335             
  Lines       42612    42612             
  Branches     5269     5269             
=========================================
+ Hits        28669    28797    +128     
+ Misses      13228    13134     -94     
+ Partials      715      681     -34

Flag	Coverage Δ
#smoketests	50.74% <ø> (+1.34%)	⬆️
#unittests	65.05% <ø> (ø)	⬆️

Impacted Files	Coverage Δ
nipype/utils/profiler.py	43.1% <0%> (-1.15%)	⬇️
nipype/interfaces/nipy/preprocess.py	45.79% <0%> (ø)	⬆️
nipype/interfaces/freesurfer/preprocess.py	66.27% <0%> (ø)	⬆️
nipype/interfaces/dynamic_slicer.py	17.47% <0%> (ø)	⬆️
nipype/pipeline/engine/utils.py	82.47% <0%> (+0.22%)	⬆️
nipype/interfaces/base/core.py	89.7% <0%> (+0.29%)	⬆️
nipype/utils/filemanip.py	79.24% <0%> (+0.94%)	⬆️
nipype/interfaces/fsl/base.py	87.77% <0%> (+1.11%)	⬆️
nipype/interfaces/io.py	54.47% <0%> (+1.32%)	⬆️
nipype/utils/config.py	66.29% <0%> (+1.65%)	⬆️
... and 5 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0498267...6de3c38. Read the comment docs.

[satra]

@effigies - just let me know whenever my credentials are required.

alternatively, @chrisfilo can you add @effigies and @mgxd to pypi as maintainers. i think you created that one.

[effigies]

You can set the TWINE_USERNAME and TWINE_PASSWORD environment variables in the Circle project whenever.

[satra]

@effigies - done

@effigies and @mgxd - if you send me your pypi usernames, i can add you as maintainers of the nipype project.

[effigies]

@satra cjmarkie

[mgxd]

@satra mgxd

[effigies]

@satra Are you good with merging this?

[satra]

for tags - should we only do master?

[effigies]

What's the goal you're trying to achieve? I assume not to push a package every time master is updated.

[satra]

i think i may be misunderstanding how circle bit works - i thought the tags section should look only for tags applied to the master branch, since tags could potentially be applied on any branch. i'll read up on my train ride in a bit.

[effigies]

So by default Circle will build on all branches and no tags. In order to restrict it from some branches, you can match with ignore and only, so here I'm saying don't run this on any branches. And then to run on all tags (regardless of branch) we use only: /.*/.

Which is to say, this job will be run iff we have a tag.