How do other package devs out there do CI for their packages? I’ve seen some packages with Travis-CI configurations that seem to download a private script in order to run their tests. Is that the only way to run specs on a service like Travis? Am I missing something obvious?
The Atom team is working on a way to get Atom packages working with Travis. Some people have found some workarounds at the moment, but we are trying to get an official solution sorted out.
Awesome, I’ll be keeping an eye out for this.
Very interested in hearing from anyone who has implemented a Travis workaround, until the official solution is released. My package requires external tools (e.g. go, goimports, and golint) so I will likely have to deviate from the ‘official’ solution anyway to bootstrap those.
Hurray: https://travis-ci.org/joefitzgerald/go-plus (!)…
A few extra tips:
- Travis only allows one language per build
- When you need more than one language (e.g. go-plus requires go), you have to bootstrap that language manually (e.g.: https://github.com/joefitzgerald/go-plus/blob/master/travis-bootstrap.sh)
- … And then modify the .travis.yml file to use it: https://github.com/joefitzgerald/go-plus/blob/master/.travis.yml
Thought that might help others who execute external processes from their package