Hi Ian,
you might want to check the "ssh agent" section of the configuration... I
just did and added on set of credentials (there are 3 possible, there was
just one).
You might find that issue in other jobs as well.. it's a bit crazy, I have
been adding missing credentials in a lot of jobs and
I'm seeing an SSH credentials problem with the release job (
https://build.geoserver.org/view/release/job/geotools-release/95/console)
java.io.IOException: [ssh-agent] Could not find specified credentials
at
I'm about to make the 11-RC2 and 2.5-RC2 release but I'm confused as to
which branch I'm aiming to release from - my choices seem to be
2.6-Snapshot based on 12-snapshot (
http://ares.boundlessgeo.com/jenkins/job/cite-wfs-1.0/141/consoleText) or
2.4-snapshot based on 10-snapshot (
Il 02/mar/2014 15:43 Ian Turton ijtur...@gmail.com ha scritto:
I'm about to make the 11-RC2 and 2.5-RC2 release but I'm confused as to
which branch I'm aiming to release from - my choices seem to be
2.6-Snapshot based on 12-snapshot (
OK I've copied the 2.4-cite* jobs to 2.5 and made what look like the
necessary changes, I've kicked off the build but if someone who knows what
the cite results should look like can check I'd be grateful.
I'll probably not get a chance to release tonight anyway as I have to pack
for tomorrow's
Thanks Ian:
I have added those new jobs to the cite view. Looks like your build
completedhttp://ares.opengeo.org/jenkins/view/geoserver-cite/job/2.5-cite-wfs-1.1/1/,
here are the resulting revisions for release:
version = 2.5-SNAPSHOT
git revision = a8c189e68bdcc75769b1f8eb43b5a401397d4410
git
On 2 Mar 2014 20:50, Jody Garnett jody.garn...@gmail.com wrote:
Thanks Ian:
I have added those new jobs to the cite view.
Out of interest how did you do that?
Looks like your build completed, here are the resulting revisions for
release:
version = 2.5-SNAPSHOT
git revision =
Jody Garnett ha scritto:
My apologies if this is a resend I have been having trouble with mail
getting through to source forge...
GeoTools 2.6-M2 is tagged; and is deployed to our maven repository.
I updated the release instructions - but still managed a few mistakes;
and not everything
My apologies if this is a resend I have been having trouble with mail
getting through to source forge...
GeoTools 2.6-M2 is tagged; and is deployed to our maven repository.
I updated the release instructions - but still managed a few mistakes;
and not everything worked:
- javadocs did not
