Closed chrisuehlinger closed 10 years ago
Alright, so here's the skinny. Someone who has push permission (probably PixelOrange) needs to go to the Travis CI website and sign in. They'll take you to a page with a list of your repositories. Go to DeltaBot and flick the On switch.
Then accept the pull request I'm about to make. The next time you push to this repository, Travis will run the tests (it sometimes take 15 minutes if it's feeling sluggish) and send you an email with the results. You can view more detailed diagnostic stuff on their website.
Closed due to issue #58
Since we're writing tests, we might as well put them to good use!
There's a tool called Travis CI that can build and test DeltaBot automatically every time we make a push to GitHub. If someone makes a change that breaks DeltaBot and causes a test to fail, Travis CI will catch it, and we can avoid pushing DeltaBot to production.
I've added a
.travis.yml
file to DeltaBot which tells Travis which tests need to be run. I've set it up so that every time I push to my fork, Travis builds and tests the code.Next, we need someone who has push permission on this repo to sign up with Travis and flick the on switch. I'll have more info on that in a bit.