Hmmm... odd indeed. When i released from 2.3.x i didn't run into the
problem, i explicitly checked since it was a problem last time around.
On Tue, Feb 26, 2013 at 10:04 AM, Mauro Bartolomeoli <
mauro.bartolome...@geo-solutions.it> wrote:
> As a workaround I temporarily changed the job to remove
As a workaround I temporarily changed the job to remove the offending
folder before doing the release. After the release I changed back the job
to it's original configuration.
I was simply doing a rm -rf && cd build &&
publish_release.sh
We'll see at the next 2.2.x release if the issue is always
Hmmm I thought I recently fixed this issue. Looking at the
geoserver-release-publish history i am not seing that build... was it
deleted? Anyways it seems to have worked itself out?
On Tue, Feb 26, 2013 at 5:15 AM, Mauro Bartolomeoli <
mauro.bartolome...@geo-solutions.it> wrote:
> The geoser
The geoserver-release-publish is currently giving this error:
Started by user hudson
[workspace] $ /bin/sh -xe /var/cache/jetty/data/hudson7528167848804124322.sh
+ set -x
+ git checkout master
warning: unable to rmdir
build/geowebcache/master/83b284b341ef25fe89adf2eb7858991defa64e57:
Directory not
