Most of my personal OSS stuff has integration testing done using Travis-CI.
It's nice for letting external peeps know what state the repo is in, and does essentially the same job Jenkins does, which means it also needs to be "turned on" for the uber account. It looks like I may have access to do exactly that from my GitHub account, but I'm not sure.
One nice thing that Travis-CI provides that Jenkins doesn't is a simple success/failure image that can also show up on NPM. It can also easily test on multiple versions of Node.js, which is nice, too.
Most of my personal OSS stuff has integration testing done using Travis-CI.
It's nice for letting external peeps know what state the repo is in, and does essentially the same job Jenkins does, which means it also needs to be "turned on" for the uber account. It looks like I may have access to do exactly that from my GitHub account, but I'm not sure.
One nice thing that Travis-CI provides that Jenkins doesn't is a simple success/failure image that can also show up on NPM. It can also easily test on multiple versions of Node.js, which is nice, too.
So, do we switch to Jenkins or turn on Travis?