2013/6/3 Andrea Aime <andrea.a...@geo-solutions.it>: > On Mon, Jun 3, 2013 at 8:53 PM, Frank Warmerdam <warmer...@pobox.com> wrote: >> >> Simone, >> >> Is the proposed process that we commit changes and then check in with he >> windows Jenkins build an hour or two later to see if we broke them? Or is >> there a way to pre-test on windows? Or will we be automatically notified if >> our change breaks the tests? > > > The workflow would be the same as the linux build server: it checks at fixed > intervals if the code changed (once per hour?),
It's trivial to set up a Github Service Hook to run on commit to make Jenkins do a build, just running a "mvn test" or "mvn integration-test" should be sufficient to notify the developer (you could still do a daily "mvn install" if needed) Also it's not that hard to make jenkins run builds of branches by filter eg origin/issue** or origin/feature** giving a developer the chance to fix things before merging. It's a bit more work to get jenkins to run a build for every pull request (like travis does), but possible, giving people to fix before merging. ping me directly if you need a hand setting up. Mark -- Disclaimer; This message is just a reflection of what I thought at the time of sending. The message may contain information that is not intended for you or that you don't understand. ------------------------------------------------------------------------------ How ServiceNow helps IT people transform IT departments: 1. A cloud service to automate IT design, transition and operations 2. Dashboards that offer high-level views of enterprise services 3. A single system of record for all IT processes http://p.sf.net/sfu/servicenow-d2d-j _______________________________________________ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
