David, Good point. All pending patches from contributors must be throughly tested and not break any existing UTs and ITs: "mvn clean install" - should succeed successfully.
I have created a *PreCommit-ATLAS-Build-Test job* in Jenkins to validate patches. https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/build?delay=0sec It has options to test your patch by building atlas with UTs and ITs. You can provide Review Board ID/ JIRA issue number or upload your local patch and test your patches. Thanks, Sarath Subramanian On Fri, Jan 19, 2018 at 1:16 AM, David Radley <[email protected]> wrote: > Hi all, > It is concerning that the master build is pretty much always unsuccessful > on the nightly build. > > It would appear that contributors are not running the tests - which is > understandable as they have been unable to run due to the maven build not > being set up to run them after Janus came in. Even before the Janus > change, the build was not working consistently. > > I appeal to all contributors to verify their changes using a build that > runs all the tests prior to sending in a patch. If the build continues to > be broken, then may be we should consider changing the process so that the > committer who updates the code, should run a build running all the tests. > > I am looking forward to the Atlas master build mostly working with > occasional breaks, rather than mostly broken with occasional successes, > > all the best, David. > > > > > Unless stated otherwise above: > IBM United Kingdom Limited - Registered in England and Wales with number > 741598. > Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU >
