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.

Re: build.geoserver.org setup for un-reliable builds?

Hi Andrea,

build.geoserver.org is using a newer version of Jenkins that ares, and as such has some different solutions to some of these issues. In this case, it is using the Locks and Latches plugin to control what can and cannot be executed concurrently. Right now, there are two different locks set up - "GeoServer" and "Docs".

So, I think it should be working as-is? However, the fact that you are seeing a failure like that is concerning.

Nick - you set up the locks and latches, was there a specific reason why build.geoserver.org is not using the same concurrent execution group setup as ares? Is it just because of the version of Jenkins?

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.

Re: build.geoserver.org setup for un-reliable builds?

build.geoserver.org is using a newer version of Jenkins that ares, and as such has some different solutions to some of these issues. In this case, it is using the Locks and Latches plugin to control what can and cannot be executed concurrently. Right now, there are two different locks set up - "GeoServer" and "Docs".

So, I think it should be working as-is? However, the fact that you are seeing a failure like that is concerning.

Right, it seems that the current concurrent build solution is at least not fully configured, e.g., a geoserver nightly build should

not be allowed to run while a geoserver one is running (and vice versa). And same goes for geotools of course, the

group should be one large all encompassing gt/gs/gwc, since upstream projects might wipe jars off the downstream

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.

build.geoserver.org is using a newer version of Jenkins that ares, and as such has some different solutions to some of these issues. In this case, it is using the Locks and Latches plugin to control what can and cannot be executed concurrently. Right now, there are two different locks set up - "GeoServer" and "Docs".

So, I think it should be working as-is? However, the fact that you are seeing a failure like that is concerning.

Nick - you set up the locks and latches, was there a specific reason why build.geoserver.org is not using the same concurrent execution group setup as ares? Is it just because of the version of Jenkins?

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.