Oh! One more thing that I forgot. It's only building the main toolkit tests (ocw/tests) and the backend tests (ocw-ui/backend/tests) at the moment. I still need to add in the frontend tests. Working on it!
-- Joyce On Thu, May 22, 2014 at 10:38 AM, Michael Joyce <[email protected]> wrote: > Hi all, > > I've set up a job on a Jenkins instance that we have running at JPL for us > to try out the Github Pull Request Builder Plugin [1]. Whenever a pull > request comes in on our Github mirror Jenkins should automatically build > the pull request and post whether tests have failed or not in the comments. > If it doesn't recognize a user name it will ask if their pull request is > safe to build and test. I can whitelist everyone so it doesn't bother > everyone about this. There are a few other cool commands that it responds > too: > > add to whitelist - Add the user's Github name to the build whitelist so it > won't ask for permission again > ok to test - Confirm that the PR is ok for Jenkins to build > test this please - Ask Jenkins to (re)test the PR > > There are still some things left to do. I need to add all the PMC members > to the admin list so they can issue commands. I also need to find a way to > push the build results to a public facing Jenkins instance so everyone can > view them. At the moment, the build results aren't viewable since the > Jenkins instance that this is running on is private. I also want to play > with the notification messages since it's a bit annoying having the > intermediary build steps be listed as Failing. > > Try it out and let me know what you guys think! If you want to see what it > looks like in action, check out [2]. I'll be setting it to check our pull > requests in just a little bit (it's still checking my personal repo at the > moment for testing). > > [1] http://s.apache.org/Swm > [2] https://github.com/MJJoyce/climate/pull/5 > > -- Joyce >
