Hi,
the 2.7.2 release job is currently failing.
The first failure was caused by the removal of the src artfact, without a
corresponding
change in the release scripts, that were still expecting it. I believe I
fixed it.
Now instead it's failing to launch the win installer build:
starting
Andrea
It looks like the first one is the Windows build, and the second is the OS
X build. It turns out that boundless recently updated the OS X build
server, and http://199.19.86.219:8080
http://199.19.86.219:8080/job/geoserver-installer/buildWithParameters?TAG=2.7.2token=buildme
no longer
On Wed, Jul 22, 2015 at 7:28 PM, Torben Barsballe
tbarsba...@boundlessgeo.com wrote:
Andrea
It looks like the first one is the Windows build, and the second is the OS
X build. It turns out that boundless recently updated the OS X build
server, and http://199.19.86.219:8080
Go ahead and kick it, but I think the build server pulls in
build.properties from the current git revision, so you will need to use the
2.7.x revision that has this change:
e0d32d1c0053b786aba2aa458b3d839634d5d49a
Torben
On Wed, Jul 22, 2015 at 10:29 AM, Andrea Aime andrea.a...@geo-solutions.it
On Tue, Jul 21, 2015 at 5:49 PM, Robert Coup robert.c...@koordinates.com
wrote:
Hi folks,
Just wondering about whether Travis could run for the stable branch as
well as master?
Travis is used exclusively to vet pull requests, it's not authoritative in
terms of full build.
In other words,
See http://ares.opengeo.org/jenkins/job/geoserver-master-nightly/703/
--
Started by timer
Building in workspace
http://ares.opengeo.org/jenkins/job/geoserver-master-nightly/ws/
Checkout:geoserver-master /
See http://ares.opengeo.org/jenkins/job/geoserver-master-nightly/701/
--
[...truncated 7331 lines...]
[INFO]
[INFO]
See http://winbuild.geo-solutions.it/jenkins/job/GeoServer-Master/1887/changes
--
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload
See
http://winbuild.geo-solutions.it/jenkins/job/GeoServer-Master/org.geoserver$gs-wms/1887/
--
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you
See
http://winbuild.geo-solutions.it/jenkins/job/GeoServer-Master/org.geoserver$gs-main/1888/
--
[...truncated 1827 lines...]
Tests run: 48, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.961 sec
Running
See
http://winbuild.geo-solutions.it/jenkins/job/GeoServer-Master/org.geoserver$gs-main/1889/
--
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you
See http://winbuild.geo-solutions.it/jenkins/job/GeoServer-Master/1888/changes
Changes:
[daniele.romagnoli] Fixing pom related to GEOT-5148 (NetCDF 4.6.2 upgrade)
since UCAR changed scope of a dependency from compile to runtime
--
[...truncated 2864
Title: Message Title
Daniele Romagnoli created an issue
See http://winbuild.geo-solutions.it/jenkins/job/GeoServer-Master/1890/changes
--
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload
GeoTools / GeoServer Meeting 2015-07-21
===
Attending
-
Ben Caradoc-Davies
Kevin Smith
Jody Garnett
Andrea Aime
Torben Barsballe
Agenda
--
- Backports for XXE vulnerability
- Release schedule
- CITE test upgrade status report
Actions
---
-
GeoTools / GeoServer committee meeting on Skype at 19:30 UTC on Tuesday:
http://www.timeanddate.com/worldclock/fixedtime.html?msg=GeoTools+%2F+GeoServer+Meetingyear=2015month=7day=21hour=19min=30sec=0ah=1
--
Ben Caradoc-Davies b...@transient.nz
Director
Transient Software Limited
Andrea
I see you already kicked it with the old parameters, so I cancelled your
build and re-ran against the new revision. The only change from the
previous version is the build.properties file, so this should ostensibly
pass cite tests etc.
Torben
On Wed, Jul 22, 2015 at 11:04 AM, Torben
On Tue, Jul 21, 2015 at 6:18 PM Niels Charlier ni...@scitus.be wrote:
Hi Kevin and Gabriel,
I have a few questions regarding the jdbc resource store and the
resource store API in general that I'd like to hear your opinion on.
Including the mailing list because others might have thoughts on
18 matches
Mail list logo
