Use Travis CI for Atom packages

[mcolyer]

We want to encourage development best practices for our 3rd party package authors. Currently we don't CI our Atom packages, however we should now that we have apm test.

While we could use janky internally, I talked with @kevinsawicki and we think it would be better to use Travis so that when things become public we have an easily replicable CI setup for our 3rd party package developers to use.

It should be fairly straightforward once we have a private account on travis-ci.com. I think we just need to set something like this each package's .travis.yml.

language: objective-c
before_script: <download/install atom>
script: open -a Atom --args -f -t --spec-directory `pwd`

Useful links

• I found this when I was researching caching assets
  implement directory caching travis-ci/travis-build#138

[kevinsawicki]

🚢

[mcolyer]

⚡ 🎊 ⚡

[jasonrudolph]

If I wanted to see the detailed Travis build results for an Atom package, how can I do so? I can't use my own GitHub account to sign into Travis, because I don't want to give Travis access to private repos in the GitHub org.

[kevinsawicki]

@jasonrudolph Unfortunately for now you have to use the private travis repo.

The credentials for it are in the Shared-Developers folder in LastPass.

[jasonrudolph]

@kevinsawicki: Got it. Thanks!

[kevinsawicki]

@jasonrudolph There is now a doc with more details: https://github.com/atom/atom/blob/master/docs/setting-up-travis.md

[lock]

This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!