Yes, please, Erik. As discussed in my other email, unless you expect a successful geogig-master build in the next few hours, please remove geogig from the communityRelease profile on all affected branches.
Kind regards, Ben. On 24/03/17 16:13, Erik Merkle wrote: > My apologies. I merged the changes in GeoServer before I realized the > LocationTech build server wasn't properly building GeoGig. Trying to get > things in too eagerly. I will not do that again. > > If the geogig module hasn't already been removed from the communityRelease > list, I can make that change now, until the LocationTech build servers are > functioning again. > > > Again, my sincerest apologies, > > Erik Merkle > Software Engineer | Boundless <http://boundlessgeo.com/> > > <http://d32wfbeasdaw38.cloudfront.net/img/Boundless_Logo.png> > > On Thu, Mar 23, 2017 at 9:00 PM, Jody Garnett <[email protected]> > 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
