Grabbed the tag and am deploying from my local machine.
Trust the next release will go better.
--
Jody Garnett
On 24 August 2017 at 12:42, Jody Garnett <[email protected]> wrote:
> Did not work for obvious reasons:
>
> sent 130 bytes received 24 bytes 102.67 bytes/sec
>
> total size is 238855569 speedup is 1551010.19
>
> + popd
>
> + git tag 16.5
>
> fatal: tag '16.5' already exists
>
> Build step 'Execute shell' marked build as failure
>
> [locks-and-latches] Releasing all the locks
>
> [locks-and-latches] All the locks released
>
> Finished: FAILURE
>
>
> --
> Jody Garnett
>
> On 24 August 2017 at 12:39, Jody Garnett <[email protected]> wrote:
>
>> Done, job is running here https://build.geoserver.o
>> rg/view/geotools/job/geotools-release-publish/83/
>>
>> --
>> Jody Garnett
>>
>> On 24 August 2017 at 12:03, Ian Turton <[email protected]> wrote:
>>
>>> So can someone log on and change deploy=skip to deploy=true, or
>>> whatever.
>>>
>>> I'd do it but I don't have a fixed ip so I can't log in.
>>>
>>> Ian
>>>
>>> On 24 Aug 2017 19:55, "Jody Garnett" <[email protected]> wrote:
>>>
>>>> I think I may know, there was some madness with SSL and certificates
>>>> and waiting for build.geoserver.org to be trusted as a thing that
>>>> could upload to our maven repo. That has been sorted out now as i
>>>> understand it due to some help from FrankW on the system admin committee,
>>>> so let us try again ...
>>>>
>>>> https://trac.osgeo.org/osgeo/ticket/1931
>>>>
>>>> --
>>>> Jody Garnett
>>>>
>>>> On 24 August 2017 at 00:46, Andrea Aime <[email protected]>
>>>> wrote:
>>>>
>>>>> On Thu, Aug 24, 2017 at 9:33 AM, Ian Turton <[email protected]>
>>>>> wrote:
>>>>>
>>>>>> That's odd, the files are on sourceforge (
>>>>>> https://sourceforge.net/projects/geotools/files/GeoTools%20
>>>>>> 16%20Releases/16.5/) so I assume the jenkins job ran correctly - TBH
>>>>>> I'm not sure which step pushes the artifacts to the repo I would guess
>>>>>> publish-release?
>>>>>>
>>>>>
>>>>> Yes, that's the step which is supposed to deploy on the
>>>>> repositories... but I don't see it happening in the build logs:
>>>>> https://build.geoserver.org/view/geotools/job/geotools-relea
>>>>> se-publish/82/consoleFull
>>>>>
>>>>> Was the release script modified not to perform deploys? Checking the
>>>>> script, it has a variable to guard against
>>>>> maven deploy:
>>>>>
>>>>> https://github.com/geotools/geotools/blob/master/build/relea
>>>>> se/publish_release.sh#L56
>>>>>
>>>>> and indeed someone set that variable:
>>>>>
>>>>> [image: Inline image 1]
>>>>>
>>>>> So... no surprises actually, it's "by design". Can the mastermind
>>>>> behind it tell us why?
>>>>> I'm guessing maybe lack of credentials for deploy on the new build
>>>>> server, or some such?
>>>>>
>>>>> Cheers
>>>>> Andrea
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Regards,
>>>>>
>>>>> Andrea Aime
>>>>>
>>>>> ==
>>>>> GeoServer Professional Services from the experts! Visit
>>>>> http://goo.gl/it488V for more information.
>>>>> ==
>>>>>
>>>>> Ing. Andrea Aime
>>>>> @geowolf
>>>>> Technical Lead
>>>>>
>>>>> GeoSolutions S.A.S.
>>>>> Via di Montramito 3/A
>>>>> 55054 Massarosa (LU)
>>>>> phone: +39 0584 962313 <+39%200584%20962313>
>>>>> fax: +39 0584 1660272 <+39%200584%20166%200272>
>>>>> mob: +39 339 8844549 <+39%20339%20884%204549>
>>>>>
>>>>> 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.
>>>>>
>>>>>
>>>>> ------------------------------------------------------------
>>>>> ------------------
>>>>> Check out the vibrant tech community on one of the world's most
>>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>>> _______________________________________________
>>>>> GeoTools-Devel mailing list
>>>>> [email protected]
>>>>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>>>>>
>>>>>
>>>>
>>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
