Hi,
I’m performing the 2.3.1 release, most of it is ok but the OSX installer was not generated, even after waiting a few hours since the “release” job was started.
As far as I know the .exe and .dmg artifacts are generated by a Hudson/Jenkins that is inside OpenGeo, I guess its build queue is stuck, or something like that?
Nothing I can do about it unfortunately, can someone from OpenGeo have a look?
Also, as usual, someone from OpenGeo is required to post the generated docs on the documentation site, following these steps:
http://docs.geoserver.org/latest/en/developer/release-guide/index.html#post-the-documentation
Cheers
Andrea
–
==
GeoServer training in Milan, 6th & 7th June 2013! Visit http://geoserver.geo-solutions.it for more information.
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
On Sat, Apr 20, 2013 at 6:35 PM, Andrea Aime
<andrea.aime@anonymised.com>wrote:
Hi,
I'm performing the 2.3.1 release, most of it is ok but the OSX installer
was not generated, even after waiting a few hours since the "release" job
was started.
As far as I know the .exe and .dmg artifacts are generated by a
Hudson/Jenkins that is inside OpenGeo, I guess its build queue is stuck, or
something like that?
Nothing I can do about it unfortunately, can someone from OpenGeo have a
look?
Unfortunately this also resulted in the extensions not being uploaded,
which I did that right now manually, and the release not being tagged
in github.
In order to perform this last step I fear that, again, direct (ssh) access
to the build server is required, given that the checkout
(with all the version number changes) is available only on the build server
itself.
I know I could replay manually all the work that went into making the
release locally and go from there, but it would take quite
some time, going on the server and running manually the last two commands
of the release_publish.sh script is a lot quicker.
Cheers
Andrea
--
GeoServer training in Milan, 6th & 7th June 2013! Visit
http://geoserver.geo-solutions.it for more information.
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------
Not sure what the issue is but i just built it manually and updated a mac installer. Still looking into the underlying issue.
···
On Sun, Apr 21, 2013 at 3:34 AM, Andrea Aime <andrea.aime@anonymised.com> wrote:
On Sat, Apr 20, 2013 at 6:35 PM, Andrea Aime <andrea.aime@anonymised.com> wrote:
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Hi,
I’m performing the 2.3.1 release, most of it is ok but the OSX installer was not generated, even after waiting a few hours since the “release” job was started.
As far as I know the .exe and .dmg artifacts are generated by a Hudson/Jenkins that is inside OpenGeo, I guess its build queue is stuck, or something like that?
Nothing I can do about it unfortunately, can someone from OpenGeo have a look?
Unfortunately this also resulted in the extensions not being uploaded, which I did that right now manually, and the release not being tagged
in github.
In order to perform this last step I fear that, again, direct (ssh) access to the build server is required, given that the checkout
(with all the version number changes) is available only on the build server itself.
I know I could replay manually all the work that went into making the release locally and go from there, but it would take quite
some time, going on the server and running manually the last two commands of the release_publish.sh script is a lot quicker.
Cheers
Andrea
–
==
GeoServer training in Milan, 6th & 7th June 2013! Visit http://geoserver.geo-solutions.it for more information.
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it