Moving feedstock generation to CircleCI (or other CI not used for building)

Currently we have a lot of issues using Travis CI to do feedstock generation. These range from regular backlogs of Travis CI in the middle of the day. Travis CIs relative slowness compared to other CI services. The fact that Mac and Linux builds share the same queue ( https://github.com/travis-ci/travis-ci/issues/6211 ). So if Mac builds get backed up, so do the Linux builds. Also, it puts us with an unnecessary matrix that may contribute to the slowness and could easily be absorbed into some if statement on CircleCI. Finally, as Travis CI restarts the job for the same build ID, we lose the log. This makes it very difficult to go back and figure out what went wrong. Other CIs like CircleCI don’t have this problem.

One alternative would be to switch to CircleCI for this functionality so it gets absorbed into our existing workers. This would also halve our Travis CI queue. Another alternative would be to use a CI that we don’t use for building so it doesn’t sit on any queue used for building. While a bit non-ideal for building, Wercker CI or some other CI would fit fine in this role too.

[pelson]

CircleCI is a pretty good option I’d say. I don’t think there was a reason I didn’t do this before - other than the fact that TravisCI was convenient. 👍

[jakirkham]

cc @jochym