[Geoserver-devel] GeoServer release publish fail for 2.7.5?

GeoServer GeoServer Developer
1

Does anyone know why the git checkout on jenkins if failing for the 2.7.5 release?

http://ares.opengeo.org/jenkins/view/release/job/geoserver-release-publish/47/console

I don’t recall ever having a problem with this step before

Ian

–

Ian Turton

2

Hi,
I might be wrong, but I see Jody releasing too… and I don’t think that
two releases can go out in parallel, as release and release-publish
retain some state on a local checkout on the build server.

If that’s the case, you may have to redo the release job too to
re-instate the correct state for your release.

Then again… maybe I’m wrong and it’s something else (but don’t know what)

Cheers
Andrea

···

On Mon, Dec 21, 2015 at 6:12 PM, Ian Turton <ijturton@anonymised.com> wrote:

Does anyone know why the git checkout on jenkins if failing for the 2.7.5 release?

http://ares.opengeo.org/jenkins/view/release/job/geoserver-release-publish/47/console

I don’t recall ever having a problem with this step before

Ian

–

Ian Turton

Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–

==
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.

Geosolutions’ Winter Holidays from 24/12 to 6/1

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

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

3

Those files were all changed by my Java 8 upgrade on master. I think we have a race condition in release-publish because it switches to master and pulls (when I think it should only fetch) even when it is on a non-master branch. If files that are processed in the release job (release tag updates in poms and installers) are changed on master between the running of release and release-publish, there may be a conflict.

I do not think this is a problem caused by Jody's concurrent release.

Andrea, I agree with your proposed solution: Ian, please try rerunning the release job. Hopefully that will clear the workspace and resolve the conflict.

Kind regards,
Ben.

On 22/12/15 09:26, Andrea Aime wrote:

Hi,
I might be wrong, but I see Jody releasing too... and I don't think that
two releases can go out in parallel, as release and release-publish
retain some state on a local checkout on the build server.

If that's the case, you may have to redo the release job too to
re-instate the correct state for _your_ release.

Then again... maybe I'm wrong and it's something else (but don't know what)

Cheers
Andrea

On Mon, Dec 21, 2015 at 6:12 PM, Ian Turton <ijturton@anonymised.com> wrote:

Does anyone know why the git checkout on jenkins if failing for the 2.7.5
release?

http://ares.opengeo.org/jenkins/view/release/job/geoserver-release-publish/47/console

I don't recall ever having a problem with this step before

Ian

--
Ian Turton

------------------------------------------------------------------------------

_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

------------------------------------------------------------------------------

_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand