Based on the branch discussion around 2.4.x tagging it seems we need 2.4.x targets created for cite testing.
I do not want to create any additional load on the server, so I will copy the 2.3.x build targets, and then “unschedule” the original.
With this in mind I am going to delay the release by a day, sorry for not noticing this earlier!
Jody
Well I must be missing part of the story 
I have created the entries by copying the cite master tests, and changing to 2.4.x.
When run the tests fail with:
Pinging GeoServer at [http://localhost:11010/geoserver](http://localhost:11010/geoserver)
+ curl -G [http://localhost:11010/geoserver](http://localhost:11010/geoserver)
curl: (7) couldn't connect to host
On Mon, Sep 2, 2013 at 8:03 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:
Based on the branch discussion around 2.4.x tagging it seems we need 2.4.x targets created for cite testing.
I do not want to create any additional load on the server, so I will copy the 2.3.x build targets, and then “unschedule” the original.
With this in mind I am going to delay the release by a day, sorry for not noticing this earlier!
Jody
There are some manual steps that you have to do on the build server. Basically just creating a symlink in a specific directory for the “2.4.x” branch. I’ve updated the script that runs the test to create this symlink on demand if it doesn’t exist.
On Mon, Sep 2, 2013 at 6:46 AM, Jody Garnett <jody.garnett@anonymised.com> wrote:
Well I must be missing part of the story
I have created the entries by copying the cite master tests, and changing to 2.4.x.When run the tests fail with:
Pinging GeoServer at [http://localhost:11010/geoserver](http://localhost:11010/geoserver) + curl -G [http://localhost:11010/geoserver](http://localhost:11010/geoserver) curl: (7) couldn't connect to host
Learn the latest–Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
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.
On Mon, Sep 2, 2013 at 8:03 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:
Based on the branch discussion around 2.4.x tagging it seems we need 2.4.x targets created for cite testing.
I do not want to create any additional load on the server, so I will copy the 2.3.x build targets, and then “unschedule” the original.
With this in mind I am going to delay the release by a day, sorry for not noticing this earlier!
Jody
Thanks Justin I can confirm that is working.
In the interest of making scheduling easier to manage I am making 2.2-cite-all, …, 2.4-cite-all jobs for scheduling, that kick off the individual cite tests. It is too annoying to prevent overlap now that we are getting so many scheduled targets.
Is there any other scheduled build targets that I should take into account?
Jody
On Tue, Sep 3, 2013 at 12:49 AM, Justin Deoliveira <jdeolive@anonymised.com> wrote:
There are some manual steps that you have to do on the build server. Basically just creating a symlink in a specific directory for the “2.4.x” branch. I’ve updated the script that runs the test to create this symlink on demand if it doesn’t exist.
On Mon, Sep 2, 2013 at 6:46 AM, Jody Garnett <jody.garnett@anonymised.com> wrote:
Well I must be missing part of the story
I have created the entries by copying the cite master tests, and changing to 2.4.x.When run the tests fail with:
Pinging GeoServer at [http://localhost:11010/geoserver](http://localhost:11010/geoserver) + curl -G [http://localhost:11010/geoserver](http://localhost:11010/geoserver) curl: (7) couldn't connect to host
Learn the latest–Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
On Mon, Sep 2, 2013 at 8:03 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:
Based on the branch discussion around 2.4.x tagging it seems we need 2.4.x targets created for cite testing.
I do not want to create any additional load on the server, so I will copy the 2.3.x build targets, and then “unschedule” the original.
With this in mind I am going to delay the release by a day, sorry for not noticing this earlier!
Jody
Well it doesn’t really matter since they execute in serial. I usually don’t worry about trying to schedule the jobs so that there are no conflicts and just let hudson queue them up and churn through them.
On Mon, Sep 2, 2013 at 5:39 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:
Thanks Justin I can confirm that is working.
In the interest of making scheduling easier to manage I am making 2.2-cite-all, …, 2.4-cite-all jobs for scheduling, that kick off the individual cite tests. It is too annoying to prevent overlap now that we are getting so many scheduled targets.
Is there any other scheduled build targets that I should take into account?
Jody
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
On Tue, Sep 3, 2013 at 12:49 AM, Justin Deoliveira <jdeolive@anonymised.com> wrote:
There are some manual steps that you have to do on the build server. Basically just creating a symlink in a specific directory for the “2.4.x” branch. I’ve updated the script that runs the test to create this symlink on demand if it doesn’t exist.
On Mon, Sep 2, 2013 at 6:46 AM, Jody Garnett <jody.garnett@anonymised.com> wrote:
Well I must be missing part of the story
I have created the entries by copying the cite master tests, and changing to 2.4.x.When run the tests fail with:
Pinging GeoServer at [http://localhost:11010/geoserver](http://localhost:11010/geoserver) + curl -G [http://localhost:11010/geoserver](http://localhost:11010/geoserver) curl: (7) couldn't connect to host
Learn the latest–Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
On Mon, Sep 2, 2013 at 8:03 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:
Based on the branch discussion around 2.4.x tagging it seems we need 2.4.x targets created for cite testing.
I do not want to create any additional load on the server, so I will copy the 2.3.x build targets, and then “unschedule” the original.
With this in mind I am going to delay the release by a day, sorry for not noticing this earlier!
Jody
Agreed.
I note that the 2.4.x docs series is failing, it appears to be due to a missing directory:
On Tue, Sep 3, 2013 at 1:33 PM, Justin Deoliveira <jdeolive@anonymised.com> wrote:
Well it doesn’t really matter since they execute in serial. I usually don’t worry about trying to schedule the jobs so that there are no conflicts and just let hudson queue them up and churn through them.
On Mon, Sep 2, 2013 at 5:39 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:
Thanks Justin I can confirm that is working.
In the interest of making scheduling easier to manage I am making 2.2-cite-all, …, 2.4-cite-all jobs for scheduling, that kick off the individual cite tests. It is too annoying to prevent overlap now that we are getting so many scheduled targets.
Is there any other scheduled build targets that I should take into account?
Jody
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
On Tue, Sep 3, 2013 at 12:49 AM, Justin Deoliveira <jdeolive@anonymised.com> wrote:
There are some manual steps that you have to do on the build server. Basically just creating a symlink in a specific directory for the “2.4.x” branch. I’ve updated the script that runs the test to create this symlink on demand if it doesn’t exist.
On Mon, Sep 2, 2013 at 6:46 AM, Jody Garnett <jody.garnett@anonymised.com> wrote:
Well I must be missing part of the story
I have created the entries by copying the cite master tests, and changing to 2.4.x.When run the tests fail with:
Pinging GeoServer at [http://localhost:11010/geoserver](http://localhost:11010/geoserver) + curl -G [http://localhost:11010/geoserver](http://localhost:11010/geoserver) curl: (7) couldn't connect to host
Learn the latest–Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
On Mon, Sep 2, 2013 at 8:03 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:
Based on the branch discussion around 2.4.x tagging it seems we need 2.4.x targets created for cite testing.
I do not want to create any additional load on the server, so I will copy the 2.3.x build targets, and then “unschedule” the original.
With this in mind I am going to delay the release by a day, sorry for not noticing this earlier!
Jody
Fixed.
On Mon, Sep 2, 2013 at 10:44 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:
Agreed.
I note that the 2.4.x docs series is failing, it appears to be due to a missing directory:
Build finished. The HTML pages are in build/html. + rm -rf /var/www/html/geoserver/2.4.x/doc/en/user + cp -r build/html /var/www/html/geoserver/2.4.x/doc/en/user cp: cannot create directory `/var/www/html/geoserver/2.4.x/doc/en/user': No such file or directory [DEBUG] Skipping watched dependency update for build: geoserver-2.4.x-docs #14 due to result: FAILURE Finished: FAILURE
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
On Tue, Sep 3, 2013 at 1:33 PM, Justin Deoliveira <jdeolive@anonymised.com> wrote:
Well it doesn’t really matter since they execute in serial. I usually don’t worry about trying to schedule the jobs so that there are no conflicts and just let hudson queue them up and churn through them.
On Mon, Sep 2, 2013 at 5:39 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:
Thanks Justin I can confirm that is working.
In the interest of making scheduling easier to manage I am making 2.2-cite-all, …, 2.4-cite-all jobs for scheduling, that kick off the individual cite tests. It is too annoying to prevent overlap now that we are getting so many scheduled targets.
Is there any other scheduled build targets that I should take into account?
Jody
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
On Tue, Sep 3, 2013 at 12:49 AM, Justin Deoliveira <jdeolive@anonymised.com> wrote:
There are some manual steps that you have to do on the build server. Basically just creating a symlink in a specific directory for the “2.4.x” branch. I’ve updated the script that runs the test to create this symlink on demand if it doesn’t exist.
On Mon, Sep 2, 2013 at 6:46 AM, Jody Garnett <jody.garnett@anonymised.com> wrote:
Well I must be missing part of the story
I have created the entries by copying the cite master tests, and changing to 2.4.x.When run the tests fail with:
Pinging GeoServer at [http://localhost:11010/geoserver](http://localhost:11010/geoserver) + curl -G [http://localhost:11010/geoserver](http://localhost:11010/geoserver) curl: (7) couldn't connect to host
Learn the latest–Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
On Mon, Sep 2, 2013 at 8:03 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:
Based on the branch discussion around 2.4.x tagging it seems we need 2.4.x targets created for cite testing.
I do not want to create any additional load on the server, so I will copy the 2.3.x build targets, and then “unschedule” the original.
With this in mind I am going to delay the release by a day, sorry for not noticing this earlier!
Jody