What’s the use case differences for travisci and circleci? for fmriprep, travisci only does style checking and circleci does the “heavy” lifting. Is this about restrictions on the sizes of containers between the two services? Or is it something else? Thanks!
Circle lets you run longer and larger jobs.
1 Like
From @emdupre: I think the reason circleci is used there is you can set a custom docker container for the build environment and cache the image between builds.
For Travis CI, I usually see its build-matrix feature used most often-- like https://github.com/nilearn/nilearn/blob/master/.travis.yml
1 Like
From Chris Holdgraf: Yeah I’ve heard that Travis has a considerable amount of tech debt given that it’s older, while circle is newer and backed by more $$$ so may be a better long term bet
1 Like