If you look at the executors, they are all named apollo; the URL is just
build ;)
[image: Inline image 1]
On Fri, Oct 6, 2017 at 11:57 AM, Jody Garnett <[email protected]>
wrote:
> I thought it was named "build" :)
>
> --
> Jody Garnett
>
> On 6 October 2017 at 10:02, Torben Barsballe <[email protected]>
> wrote:
>
>> Excellent.
>>
>> I believe it is named apollo internally. We just need to start using the
>> name, so that everyone knows what we are talking about when someone says
>> "apollo".
>>
>> Torben
>>
>> On Fri, Oct 6, 2017 at 9:55 AM, Ian Turton <[email protected]> wrote:
>>
>>> OK I've pushed the release job on new build (we should name that
>>> machine) - I'll see how it goes
>>>
>>> Ian
>>>
>>> On 6 October 2017 at 17:54, Torben Barsballe <
>>> [email protected]> wrote:
>>>
>>>> All 2.12.x cite tests now passing on ares. Jody posted the revision
>>>> info above, but here it is again:
>>>>
>>>> version = 2.12-SNAPSHOT
>>>> git revision = bc18e09993a30c93f37b7e33e7c54c32b17e014b
>>>> git branch = origin/2.12.x
>>>> build date = 06-Oct-2017 15:52
>>>> geotools version = 18-SNAPSHOT
>>>> geotools revision = 3f5dbf634c4a6b24476643cc7cf7d2b22747fcf5
>>>> geowebcache version = 1.12-SNAPSHOT
>>>> geowebcache revision = 5b516f3adc0f82e42f342ba83b5fc9a353d575d2/5b516
>>>>
>>>>
>>>> Torben
>>>>
>>>> On Fri, Oct 6, 2017 at 9:52 AM, Torben Barsballe <
>>>> [email protected]> wrote:
>>>>
>>>>> Ian
>>>>>
>>>>> Looking at the 2.11 cite tests on the new build server, they are
>>>>> failing (although reporting success) for a different reason than the jar
>>>>> (curl:
>>>>> (7) Failed to connect to localhost port 11010 - looks like an issue
>>>>> starting up geoserver or the cite server). So I expect once we get
>>>>> the jar for the 2.12.x cite tests, they will just be failing in a
>>>>> different
>>>>> way. It seems like each time one of the cite test issues get fixed, there
>>>>> is another one underneath.
>>>>>
>>>>> Torben
>>>>>
>>>>> On Fri, Oct 6, 2017 at 9:42 AM, Ian Turton <[email protected]> wrote:
>>>>>
>>>>>> Thanks Torben
>>>>>>
>>>>>> I think all the cite tests on the new build server need is one jar
>>>>>> installed
>>>>>>
>>>>>> Cheers
>>>>>>
>>>>>> Ian
>>>>>>
>>>>>> On 6 October 2017 at 17:27, Torben Barsballe <
>>>>>> [email protected]> wrote:
>>>>>>
>>>>>>>
>>>>>>> On 6 October 2017 at 09:00, Torben Barsballe <tbarsballe@boundles
>>>>>>> sgeo.com> wrote:
>>>>>>>
>>>>>>>> Running the cite tests on ares and the build on the new build
>>>>>>>> server works fine, from past experience.
>>>>>>>
>>>>>>>
>>>>>>> On Fri, Oct 6, 2017 at 9:23 AM, Jody Garnett <[email protected]
>>>>>>> > wrote:
>>>>>>>
>>>>>>>> Can we run cite tests on ares to verify the revision numbers, and
>>>>>>>> then make the release on build.geoserver.org ?
>>>>>>>>
>>>>>>>>
>>>>>>> Yes
>>>>>>>
>>>>>>>
>>>>>>> Torben
>>>>>>>
>>>>>>>
>>>>>>>> --
>>>>>>>> Jody Garnett
>>>>>>>>
>>>>>>>> On 6 October 2017 at 09:00, Torben Barsballe <
>>>>>>>> [email protected]> wrote:
>>>>>>>>
>>>>>>>>> Hi Ian,
>>>>>>>>>
>>>>>>>>> It looks like the cite tests on the new build server still need a
>>>>>>>>> bit more work before they are functional; Jody, Nick, Justin, and Ben
>>>>>>>>> seem
>>>>>>>>> to be arranging something to look into that; but that probably won't
>>>>>>>>> be in
>>>>>>>>> time for the release.
>>>>>>>>>
>>>>>>>>> Given that, best bet is probably to use ares. I was hoping we
>>>>>>>>> could avoid creating the 2.12 jobs on ares as well, but I guess that
>>>>>>>>> is not
>>>>>>>>> going to be the case. I've created a 2.12.x nightly on ares, and
>>>>>>>>> kicked off
>>>>>>>>> another batch of cite tests.
>>>>>>>>>
>>>>>>>>> Running the cite tests on ares and the build on the new build
>>>>>>>>> server works fine, from past experience.
>>>>>>>>>
>>>>>>>>> Torben
>>>>>>>>>
>>>>>>>>> On Fri, Oct 6, 2017 at 3:32 AM, Ian Turton <[email protected]>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> As I said in another message the cite-tests currently don't run
>>>>>>>>>> on the new build server. I just tried to run the cite tests on ares
>>>>>>>>>> but
>>>>>>>>>> that won't work as there is no geoserver-12.x build configured. I'm
>>>>>>>>>> loathe
>>>>>>>>>> to set up a complete 2.12.x build on ares as we are trying to move
>>>>>>>>>> away
>>>>>>>>>> from it and I'm not sure what the possible interactions are.
>>>>>>>>>>
>>>>>>>>>> So if someone with a fixed IP address can fix the new build
>>>>>>>>>> server up that would be great as currently all the cite tests
>>>>>>>>>> currently
>>>>>>>>>> claim to be passing but are in fact failing.
>>>>>>>>>>
>>>>>>>>>> cheers
>>>>>>>>>>
>>>>>>>>>> Ian
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Ian Turton
>>>>>>>>>>
>>>>>>>>>> ------------------------------------------------------------
>>>>>>>>>> ------------------
>>>>>>>>>> Check out the vibrant tech community on one of the world's most
>>>>>>>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>>>>>>>> _______________________________________________
>>>>>>>>>> GeoTools-Devel mailing list
>>>>>>>>>> [email protected]
>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ------------------------------------------------------------
>>>>>>>>> ------------------
>>>>>>>>> Check out the vibrant tech community on one of the world's most
>>>>>>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>>>>>>> _______________________________________________
>>>>>>>>> GeoTools-Devel mailing list
>>>>>>>>> [email protected]
>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Ian Turton
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> Ian Turton
>>>
>>
>>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
