On Tue, Dec 19, 2017 at 5:28 PM, Ben Caradoc-Davies <[email protected]>
wrote:
> Torben,
>
> one tiny buglet is that the Jenkins geoserver-release job still prints an
> ares URL for the location of the release artifacts at the end of its log.
> For example:
> https://build.geoserver.org/view/geoserver/job/geoserver-rel
> ease/194/consoleText
> "build complete, artifacts available at http://ares.boundlessgeo.com/g
> eoserver/release/2.11.4"
>
> DIST_HOST=ares.boundlessgeo.com is set in build/properties, and I
> considered changing it, but this is also used for things like an ssh
> private key filename. As you were the last person seen fixing the build
> infrastructure (according to git), I was wondering if you had an opinion on
> whether it is safe to change this? Perhaps we could try just before the
> next GeoServer release, and see if it still works.
Looking in the build scripts, the only place besides that message where
DIST_HOST is used is by upload_installer, which in turn is only used by the
mac and windows build scripts.
The current windows build manually sets DIST_HOST, and the mac build can't
upload to the proper location anyways due to auth issues.
So, yes, changing DIST_HOST to build.geoserver.org should be fine, and I
don't anticipate it to cause any issues.
Torben
>
> Kind regards,
> Ben.
>
> On 19/12/17 09:46, Ben Caradoc-Davies wrote:
>
>> https://build.geoserver.org/geoserver/release/2.11.4/
>>
>> There is no Windows EXE.
>>
>>
> --
> Ben Caradoc-Davies <[email protected]>
> Director
> Transient Software Limited <https://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
