Thanks for trying, Jody. My main concern is the loss of continuous integration and impact on Travis CI for pull requests. I am not submitting or merging pull requests today so am not yet personally affected.
As an aside, the Maven option that works for me is "-pl", which can be used to exclude a module by giving its path relative to the top-level pom. I use it to exclude app-schema oracle online tests. In the geogig case below, this would be: -pl '!geogig' However, I do not think that we should modify all the Jenkins and Travis CI builds as we will only have to change them all back, and community modules that do not compile are not permitted in the communityRelease profile. We should not need magic options to build. When do we expect to see a successful geogig-master build? If we are likely to get one in the next 12 hours, we should just wait, otherwise we should remove geogig from the communityRelease profile on all affected branches. Kind regards, Ben. On 24/03/17 15:00, Jody Garnett wrote: > Sigh it did not work, I escaped the bang and everything: > > mvn -f src/community/pom.xml -B -U -DskipTests > -PcommunityRelease,\!geogig clean install > -DconfigDirectory=../../../data -T2 -fae > > > Next step as you say is removing geogig from the communityRelease so you > can work today. > > -- > Jody Garnett > > On 23 March 2017 at 18:58, Jody Garnett <[email protected]> wrote: > >> No I changed the jobs to say -PcommunityRelease,!geogig >> >> -- >> Jody Garnett >> >> On 23 March 2017 at 18:21, Ben Caradoc-Davies <[email protected]> wrote: >> >>> Jody, >>> >>> do you mean removing geogig from the communityRelease profile? >>> >>> Kind regards, >>> Ben. >>> >>> >>> On 24/03/17 14:09, Jody Garnett wrote: >>> >>>> I am sorry Ben, it does not seem to be a good day for build servers - the >>>> LocationTech build server was troubled earlier in the day (timing out >>>> when >>>> Erik was trying to reach it). >>>> >>>> I am going to go remove geogig from the ares build jobs as a temporary >>>> measure while this is resolved. >>>> >>>> -- >>>> Jody Garnett >>>> >>>> On 23 March 2017 at 17:54, Ben Caradoc-Davies <[email protected]> wrote: >>>> >>>> Erik, >>>>> >>>>> GeoServer builds on all branches (master, 2.11.x, 2.10.x, and 2.9.x) are >>>>> broken because the geogig-master build is failing and has not updated >>>>> the >>>>> 1.1-SNAPSHOT jars to include the most recent API changes: >>>>> https://ci.locationtech.org/geogig/job/geogig-master/ >>>>> >>>>> Travis CI correctly identified that these pull requests would cause the >>>>> GeoServer builds to fail. One of these checks had failed and three were >>>>> still pending at the time that you merged these pull requests: >>>>> https://github.com/geoserver/geoserver/pull/2183 >>>>> https://github.com/geoserver/geoserver/pull/2186 >>>>> https://github.com/geoserver/geoserver/pull/2185 >>>>> https://github.com/geoserver/geoserver/pull/2184 >>>>> >>>>> Once the geogig-master build has been fixed, please restart all the >>>>> failing GeoServer Jenkins builds and all the Travis CI branch builds and >>>>> pull request builds that failed because of this outage. I can help with >>>>> this step. >>>>> >>>>> Kind regards, >>>>> >>>>> -- >>>>> Ben Caradoc-Davies <[email protected]> >>>>> Director >>>>> Transient Software Limited <http://transient.nz/> >>>>> New Zealand >>>>> >>>>> >>>> >>> -- >>> Ben Caradoc-Davies <[email protected]> >>> Director >>> Transient Software Limited <http://transient.nz/> >>> New Zealand >>> >> >> > -- Ben Caradoc-Davies <[email protected]> Director Transient Software Limited <http://transient.nz/> New Zealand ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
