Hi all,
Another update. The release scripts are getting close to complete. I am more or less ready to try them out for the 2.2-beta2 release. At the moment I am waiting on the geotools 8.0-RC1 issues currently being discussed on geotools-dev to be resolved. As soon as that is out of the way I will go ahead and try out the scripts for real. Last remaining TODO is to generate the RELEASE_NOTES.txt file, which should be pretty straight forward as we previously discussed. Will do that tomorrow.
I did up some rough docs for how the process works thus far. You can find these here:
https://github.com/jdeolive/geoserver/blob/build_scripts/doc/en/developer/source/release-guide/automated.rst
(I really like how github can render rst directly!)
A couple of more things.
I wanted to stick to straight bash command line utilities for all the scripts but it seems the JIRA rest api doesn’t offer all the functionality we need in the 4.4 version, which is the version that is deployed on codehaus. So i had to fall back to SOAP api for which there is a python client. So the jira release component is written in python and requires a library called SOAPpy which does not come standard in python but can easily be installed via easy_install. The rest api as of JIRA version 5 does do what we need at which point we can port the python stuff to bash + curl.
As noted above i decided to break out the jira release component out into a separate step/job. Mostly because it required python but also because it made the main release script cleaner and less complex.
So as soon as geotools 8.0-RC1 is out the door I will take these babies for a real test spin. Although I have done a fair bit of testing of the individual parts in isolation i am sure more issues will arise the first time through.
On a related note I am hoping to put together the same sorts of automated process for GeoTools releases. Which should be quite a bit simpler than the GeoServer one.
-Justin
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Very cool,
thanks Justin.
Regards,
Alessio.
Ing. Alessio Fabiani
Founder / CTO GeoSolutions S.A.S.
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: (+39) 0584 96.23.13
fax: (+39) 0584 96.23.13
mobile:(+39) 331 62.33.686
On Fri, May 18, 2012 at 6:19 AM, Justin Deoliveira <jdeolive@anonymised.com> wrote:
Hi all,
Another update. The release scripts are getting close to complete. I am more or less ready to try them out for the 2.2-beta2 release. At the moment I am waiting on the geotools 8.0-RC1 issues currently being discussed on geotools-dev to be resolved. As soon as that is out of the way I will go ahead and try out the scripts for real. Last remaining TODO is to generate the RELEASE_NOTES.txt file, which should be pretty straight forward as we previously discussed. Will do that tomorrow.
I did up some rough docs for how the process works thus far. You can find these here:
https://github.com/jdeolive/geoserver/blob/build_scripts/doc/en/developer/source/release-guide/automated.rst
(I really like how github can render rst directly!)
A couple of more things.
I wanted to stick to straight bash command line utilities for all the scripts but it seems the JIRA rest api doesn’t offer all the functionality we need in the 4.4 version, which is the version that is deployed on codehaus. So i had to fall back to SOAP api for which there is a python client. So the jira release component is written in python and requires a library called SOAPpy which does not come standard in python but can easily be installed via easy_install. The rest api as of JIRA version 5 does do what we need at which point we can port the python stuff to bash + curl.
As noted above i decided to break out the jira release component out into a separate step/job. Mostly because it required python but also because it made the main release script cleaner and less complex.
So as soon as geotools 8.0-RC1 is out the door I will take these babies for a real test spin. Although I have done a fair bit of testing of the individual parts in isolation i am sure more issues will arise the first time through.
On a related note I am hoping to put together the same sorts of automated process for GeoTools releases. Which should be quite a bit simpler than the GeoServer one.
-Justin
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Live Security Virtual Conference
Exclusive live event will cover all the ways today’s security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
On Thu, May 17, 2012 at 10:19 PM, Justin Deoliveira <jdeolive@anonymised.com> wrote:
Hi all,
Another update. The release scripts are getting close to complete. I am more or less ready to try them out for the 2.2-beta2 release. At the moment I am waiting on the geotools 8.0-RC1 issues currently being discussed on geotools-dev to be resolved. As soon as that is out of the way I will go ahead and try out the scripts for real. Last remaining TODO is to generate the RELEASE_NOTES.txt file, which should be pretty straight forward as we previously discussed. Will do that tomorrow.
I did up some rough docs for how the process works thus far. You can find these here:
https://github.com/jdeolive/geoserver/blob/build_scripts/doc/en/developer/source/release-guide/automated.rst
(I really like how github can render rst directly!)
A couple of more things.
I wanted to stick to straight bash command line utilities for all the scripts but it seems the JIRA rest api doesn’t offer all the functionality we need in the 4.4 version, which is the version that is deployed on codehaus. So i had to fall back to SOAP api for which there is a python client. So the jira release component is written in python and requires a library called SOAPpy which does not come standard in python but can easily be installed via easy_install. The rest api as of JIRA version 5 does do what we need at which point we can port the python stuff to bash + curl.
Ironically enough it seems that codehaus has just upgraded jira to 5.0… if only i had waited a few days 
Oh well. For now i am going to stick with the soap api.
As noted above i decided to break out the jira release component out into a separate step/job. Mostly because it required python but also because it made the main release script cleaner and less complex.
So as soon as geotools 8.0-RC1 is out the door I will take these babies for a real test spin. Although I have done a fair bit of testing of the individual parts in isolation i am sure more issues will arise the first time through.
On a related note I am hoping to put together the same sorts of automated process for GeoTools releases. Which should be quite a bit simpler than the GeoServer one.
-Justin
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.