Re: Jenkins 2.204.1 LTS RC testing started

[ogondza]

Thank you guys very much for keeping the quality bar high! As Baptiste 
said, better to be alarmed for without defect.

My internal testing have not revered anything. The 2.204.1 can be released 
today.

--
oliver

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/7366e9f6-9759-465b-9b81-4da9cea0ee7a%40googlegroups.com.

Re: Jenkins 2.204.1 LTS RC testing started

[Baptiste Mathus]

Nope, Mark, don't be sorry, THANK YOU.

Better safe than sorry, and you're clearly doing a great job actually
checking the RCs.

On Mon, Dec 16, 2019 at 9:51 AM Mark Waite 
wrote:

> Special thanks to Oleg Nenashev for detecting my mistake.  The issues I
> was seeing were caused by *my mistakes* and are not related to anything
> specific to 2.204.1-rc.
>
> I made a merge error in the definition of a Blue Ocean organization folder
> and deleted an opening tag in the 'scm' section of a pipeline library
> definition.  Once that merge error was reverted, the job loads correctly
> and completely in Jenkins 2.204.1-rc.
>
> The on-disc copy I was using at run-time was different from the copy
> stored in source control.  Once they were made the same, then Jenkins
> 2.190.3 showed the same failure.
>
> The second mistake I made was that I had omitted a JCasC agent definition
> for one of my Windows agents and was mistakenly using an on-disk copy of
> the agent definition.  The on-disk copy was damaged in some way.  Once I
> defined the agent in JCasC, the agent ran correctly with Jenkins 2.204.1-rc.
>
> Sorry for the false alarms on both items!
>
> Mark Waite
>
> On Saturday, December 14, 2019 at 10:52:38 PM UTC-7, Mark Waite wrote:
>>
>> I've reported https://issues.jenkins-ci.org/browse/JENKINS-60484 against
>> 2.204.1-rc as a regression that needs more investigation.  An organization
>> folder job from Blue Ocean which parsed correctly with Jenkins 2.190.3 no
>> longer parses correctly with Jenkins 2.204.1-rc.
>>
>> I've also seen another XML parsing issue with the definition of one of my
>> windows agents being unusable while other windows (and non-windows) agent
>> definitions are read and processed correctly.
>>
>> I'll report more tomorrow or Monday.
>>
>> Mark Waite
>>
>> On Thursday, December 5, 2019 at 7:57:45 AM UTC-7, ogondza wrote:
>>>
>>> Hello everyone,
>>>
>>> Latest LTS RC was made public and it is ready to be tested. Final
>>> release is scheduled for 2019-12-18.
>>>
>>> Please, report your findings in this thread.
>>>
>>> Download bits from
>>> http://mirrors.jenkins-ci.org/war-stable-rc/2.204.1/jenkins.war
>>>
>>> Thanks!
>>> --
>>> oliver
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/abc69182-b268-4bd3-8ded-f6af35fef68e%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPyTVp09hc1%2BYybHwsfoXWxAx%2BmCAJVVp-pR7JWwApkCHMWaxA%40mail.gmail.com.

Re: Jenkins 2.204.1 LTS RC testing started

[Mark Waite]

Special thanks to Oleg Nenashev for detecting my mistake.  The issues I was 
seeing were caused by *my mistakes* and are not related to anything 
specific to 2.204.1-rc.

I made a merge error in the definition of a Blue Ocean organization folder 
and deleted an opening tag in the 'scm' section of a pipeline library 
definition.  Once that merge error was reverted, the job loads correctly 
and completely in Jenkins 2.204.1-rc.

The on-disc copy I was using at run-time was different from the copy stored 
in source control.  Once they were made the same, then Jenkins 2.190.3 
showed the same failure.

The second mistake I made was that I had omitted a JCasC agent definition 
for one of my Windows agents and was mistakenly using an on-disk copy of 
the agent definition.  The on-disk copy was damaged in some way.  Once I 
defined the agent in JCasC, the agent ran correctly with Jenkins 2.204.1-rc.

Sorry for the false alarms on both items!

Mark Waite

On Saturday, December 14, 2019 at 10:52:38 PM UTC-7, Mark Waite wrote:
>
> I've reported https://issues.jenkins-ci.org/browse/JENKINS-60484 against 
> 2.204.1-rc as a regression that needs more investigation.  An organization 
> folder job from Blue Ocean which parsed correctly with Jenkins 2.190.3 no 
> longer parses correctly with Jenkins 2.204.1-rc.  
>
> I've also seen another XML parsing issue with the definition of one of my 
> windows agents being unusable while other windows (and non-windows) agent 
> definitions are read and processed correctly.
>
> I'll report more tomorrow or Monday.
>
> Mark Waite
>
> On Thursday, December 5, 2019 at 7:57:45 AM UTC-7, ogondza wrote:
>>
>> Hello everyone, 
>>
>> Latest LTS RC was made public and it is ready to be tested. Final 
>> release is scheduled for 2019-12-18. 
>>
>> Please, report your findings in this thread. 
>>
>> Download bits from 
>> http://mirrors.jenkins-ci.org/war-stable-rc/2.204.1/jenkins.war 
>>
>> Thanks! 
>> -- 
>> oliver 
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/abc69182-b268-4bd3-8ded-f6af35fef68e%40googlegroups.com.

Re: Jenkins 2.204.1 LTS RC testing started

[Mark Waite]

I've reported https://issues.jenkins-ci.org/browse/JENKINS-60484 against 
2.204.1-rc as a regression that needs more investigation.  An organization 
folder job from Blue Ocean which parsed correctly with Jenkins 2.190.3 no 
longer parses correctly with Jenkins 2.204.1-rc.  

I've also seen another XML parsing issue with the definition of one of my 
windows agents being unusable while other windows (and non-windows) agent 
definitions are read and processed correctly.

I'll report more tomorrow or Monday.

Mark Waite

On Thursday, December 5, 2019 at 7:57:45 AM UTC-7, ogondza wrote:
>
> Hello everyone, 
>
> Latest LTS RC was made public and it is ready to be tested. Final 
> release is scheduled for 2019-12-18. 
>
> Please, report your findings in this thread. 
>
> Download bits from 
> http://mirrors.jenkins-ci.org/war-stable-rc/2.204.1/jenkins.war 
>
> Thanks! 
> -- 
> oliver 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/53334be7-9a03-4250-8284-c80aea3b7f5a%40googlegroups.com.

Jenkins 2.204.1 LTS RC testing started

[Oliver Gondža]

Hello everyone,

Latest LTS RC was made public and it is ready to be tested. Final 
release is scheduled for 2019-12-18.


Please, report your findings in this thread.

Download bits from 
http://mirrors.jenkins-ci.org/war-stable-rc/2.204.1/jenkins.war


Thanks!
--
oliver

--
You received this message because you are subscribed to the Google Groups "Jenkins 
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/4b2807a0-01dc-1fc1-5a2f-9ffca19a86d9%40gmail.com.