Re: LTS baseline selection for the successor of 2.235

[Mark Waite]

I agree with Daniel that we should prefer 2.249 or consider 2.251 so that
we avoid confusion in bug reports.  I also like that Ulli noted it
increases the Hamming distance.  It has been a while since I thought about
Hamming codes.

On Thu, Jul 30, 2020 at 2:22 PM Daniel Beck  wrote:

>
>
> > On 29. Jul 2020, at 13:59, Oleg Nenashev  wrote:
> >
> > 2.250 is a fancy number, so why not?
>
> As I previously explained, too similar to 2.150 which was also an LTS
> baseline. Since there's no other notable difference to 2.249, I would
> prefer less confusing bug reports over having a nice looking number.
>
> --
> 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/374FBAD1-9229-4EC1-B333-1B1BF1B299B5%40beckweb.net
> .
>

-- 
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/CAO49JtEw3QRSpm-5UncC%2Bc4M%2BJSpeZ9MBisxvL0W1THqbY36LQ%40mail.gmail.com.

Re: LTS baseline selection for the successor of 2.235

[Daniel Beck]

> On 29. Jul 2020, at 13:59, Oleg Nenashev  wrote:
> 
> 2.250 is a fancy number, so why not?

As I previously explained, too similar to 2.150 which was also an LTS baseline. 
Since there's no other notable difference to 2.249, I would prefer less 
confusing bug reports over having a nice looking number.

-- 
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/374FBAD1-9229-4EC1-B333-1B1BF1B299B5%40beckweb.net.

Re: Terminology Updates

[slide]

Hi Everyone,

Just wanted to update on the current status of this effort. We discussed 
this in the Governance Meeting yesterday. The poll closed yesterday, you 
can see the results at: 
https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_1bd92a17371a1ca5. They 
are also shown below:

Result
1. *Controller*  (Condorcet winner: wins contests with all other choices)
2. Manager  loses to Controller by 95–35
3. Coordinator  loses to Controller by 98–37, loses to Manager by 69–59
4. Primary  loses to Controller by 90–44, loses to Coordinator by 66–63
5. Main  loses to Controller by 97–36, loses to Primary by 68–47
6. Director  loses to Controller by 110–21, loses to Main by 70–56
7. Leader  loses to Controller by 106–24, loses to Director by 71–46
8. Executive  loses to Controller by 116–15, loses to Leader by 65–34

Our plan now is to take the terms from the poll and run them through some 
checks with native speakers and Google Translate to check the 
internationalization aspects of the options. We will make a final decision 
in the next Governance Meeting and make announcements here on the 
Developers Mailing List as well as providing context and information via 
blog posts.

Just as a reminder, this effort is to replace the "Jenkins application" 
term, for what used to be termed the "Jenkins Master." In addition to this 
usage of "master" we also have the concept of the "master" node that can 
exist in the Jenkins Application. We will determine next steps on replacing 
that term (for that node) in the future (because the terms in the list 
below do not necessarily match the requirements in the context of nodes). 

We want to thank everyone who participated in the poll. We are working hard 
to get these changes going on this important effort.

Regards,

Alex Earl

On Wednesday, July 29, 2020 at 10:38:24 AM UTC-7 Oleg Nenashev wrote:

> Thanks to everyone who voted for the options! We will review of the voting 
> results to the Governance meeting agenda: 
> https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#heading=h.cgd8zbewht8o
>
> The meeting will start in 20 minutes, everyone is welcome to join: 
> https://zoom.us/j/99217163913?pwd=TldwZWZTQzNNc3ZGaThFOThlckFGQT09
>
> Best regards,
> Oleg
>
>
> On Thursday, July 23, 2020 at 8:35:15 PM UTC+2, Mark Waite wrote:
>
>> Unfortunately, new terms can't be included in the the votiing.  The 
>> voting is already in progress at  
>> https://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_1bd92a17371a1ca5=f82b79a50f54ad87
>>  .  
>> The governance board is using the voting as input for the final decision on 
>> the term to be used.
>>
>> On Thu, Jul 23, 2020 at 7:15 AM Steve Carter  wrote:
>>
> Hi all,
>>>
>>> I showed up late to the party, so I'll accept a snub gracefully, but I 
>>> was intrigued by the problem of replacing the term "master" and have one 
>>> further term I would like to put in the poll if at all possible.
>>>
>>> Dispatcher.
>>>
>>> This would most correctly apply to the function of taking jobs off the 
>>> queue and handing them to nodes. What we today know as master would 
>>> therefore consist of dispatcher and zero-or-one agents.
>>>
>>> What I think distinguishes this suggestion is that it connotes a service 
>>> provided to agents in collaboration rather than a hierarchical power 
>>> relationship.
>>>
>>> -- 
>>> 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 jenkin...@googlegroups.com.
>>
>>
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/b8487054-6383-4dec-be3e-29103215cc09o%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/16dd80db-6686-451a-9e77-9f009833bafen%40googlegroups.com.

Re: Stopping a build in pipeline vs freestyle mode: Different "Results"

[Philipp Mahlberg]

Hi Jesse, 
thanks a lot for your comments; I hope the penny has dropped now (see 
below...).

You were right -- there was still a `setResult(ABORTED)` call preceding the 
exception in the plugin. This survives in pipeline mode buts gets 
overwritten in a Freestyle project which caused the observed inconsistency.

>From what I understand, the build result mechanism works as follows:
* Within a  `run`-method of a step I can call run.setResult() with an 
argument of type SUCCESS, UNSTABLE or FAILURE -- depending on the outcome I 
want to indicate. 
* In case of an error that is still "normal" in terms that I might happen 
during a build process but is such severe that I want to abort the build I 
throw an Exception e.g. of type AbortException. Jenkins, in turn, marks 
such builds as FAILED. 
* The other two possible outcomes, namely ABORTED or NOT_BUILD are beyond 
the scope of "normal" build execution and as such there should be in 
general no need to set them from a run method of a step. This is probably 
also the reason why one can specify an (abnormal) cause when triggering an 
build that should be treated as ABORTED. 

Is this correct now? This would still leave an ambiguity between "failed, 
but completed" and "normally aborted" (which gets also marked as failed) 
builds but apart from this it looks rather consistent...

Jesse Glick schrieb am Mittwoch, 29. Juli 2020 um 16:41:26 UTC+2:

> On Wed, Jul 29, 2020 at 8:44 AM Philipp Mahlberg
>  wrote:
> > run.setResult(jenkinsResult);
>
> Do not call `setResult`. Use exceptions only.
>
> > In pipeline mode, this works as expected. The first line is not even 
> needed, even without it, the build stops and will be marked as ABORTED.
>
> Must be a mistake. `AbortException`, despite the name, should produce
> `Result.FAILURE`. It is the stock marker for a build which failed not
> due to any bug in Jenkins (an expected failure), so no stack trace is
> printed.
>
> > I know that I can achieve the ABORT state by "interrupting" the build. 
> But interrupting seems to encode the user actively stopping the build e.g. 
> by clicking the red cross.
>
> For Pipeline builds, `FlowInterruptedException` encodes a cause and a
> result, defaulting to `ABORTED`. There is no exact equivalent for
> traditional job types but (IIRC) any `InterruptedException` will count
> as `ABORTED`.
>

-- 
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/fbf2266a-a448-4ecd-ae29-6393c592bb2dn%40googlegroups.com.

Re: Proposal - Expanding the DockerHub admins team

[Oleg Nenashev]

Thanks all!

I have added markewaite and slideomix accouns as owners in the *jenkins *and 
*jenkins4eval *organizations. I have no access to the old *jenkinsci 
*organization, 
but AFAICT we do not have any active images there except Blue Ocean.

Best regards,
Oleg

On Wednesday, July 29, 2020 at 6:58:00 PM UTC+2, Vlad Silverman wrote:
>
> +1
>
> On Jul 29, 2020, at 9:24 AM, 'Gavin Mogan' via Jenkins Developers <
> jenkin...@googlegroups.com > wrote:
>
> +1
>
> On Wed, Jul 29, 2020 at 9:20 AM Tim Jacomb  > wrote:
>
>> +1
>>
>> On Wed, 29 Jul 2020 at 17:14, Matt Sicker > > wrote:
>>
>>> Sounds great!
>>>
>>> On Wed, Jul 29, 2020 at 11:06 AM Oleg Nenashev >> > wrote:
>>> >
>>> > Hi all,
>>> >
>>> > I am planning to be on vacation in the beginning of September, likely 
>>> off the grid for some time. I would like to ensure that we have a good bus 
>>> factor. Taking our experience with the Docker images in the recent months, 
>>> it would be great to add more admins there.
>>> >
>>> > I propose to add Alex Earl and Mark Waite to the team. It would mean 
>>> the administrative access to all DockerHub organizations: jenkins, 
>>> jenkinsci, jenkins4eval. Both Mark and Alex have CLA signed. They also have 
>>> administrative access to many areas of the Jenkins infrastructure, 
>>> including critical components like the new release infrastructure and 
>>> Trusted CI.
>>> >
>>> > Any objections?
>>> >
>>> > Thanks in advance,
>>> > Oleg
>>> >
>>> >
>>> > --
>>> > 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 jenkin...@googlegroups.com .
>>> > To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLBiDZxaB3txQjmABX8t1_L4W2YY%3Dvg5G7C%2BX0vcPqfzsg%40mail.gmail.com
>>> .
>>>
>>>
>>>
>>> -- 
>>> Matt Sicker
>>> Senior Software Engineer, CloudBees
>>>
>>> -- 
>>> 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 jenkin...@googlegroups.com .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4ozj%3DFAjDU4fjQni9U3XsNQ2p%2Bi3Jbhwc-ncMZZ8ZYmDSw%40mail.gmail.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 jenkin...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BicwCsJfLA1xhWAb4m_S4HJUaJkho1y70vmac3UVK%2BKvOw%40mail.gmail.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 jenkin...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_Duti-rP2UEvVohek_1BRpjLBqGBLV6jO48cypyUG7yR4hg%40mail.gmail.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/079af8ab-0701-4928-b579-f5648db1a146o%40googlegroups.com.

Re: ANN - GSoC Coding Phase 2 demos on Jul 29 and 30

[Oleg Nenashev]

Recording of the first part: https://youtu.be/b67I6spBdTg . Join us at 2PM
UTC today for a second part!

Best regards,
Oleg

On Wed, Jul 29, 2020, 00:12 Oleg Nenashev  wrote:

> Dear all,
>
> On Wednesday and Thursday we will have the project status updates and
> demos by the Jenkins' Google Summer of code students. We have 6 Jenkins and
> 1 Jenkins X projects, all of them are going well.You can find the full list
> of projects and the details links here
> .
>
> Part 1: Jul 29, Wed, 2PM UTC
>
>- Git Plugin Performance Improvements by Rishabh Budhouliya
>- GitHub Checks API for Jenkins Plugins by Kezhi Xiong
>- External Fingerprint Storage by Sumit Sarin
>
> Part 2: Jul 30, Thu, 2PM UTC
>
>- Custom Jenkins distribution build service by Sladyn Nunes
>- Machine Learning Plugins for Data Science by Loghi Perinpanayagam
>- Jenkins Windows Services: YAML Configuration Support by Buddhika
>Chathuranga
>
> Full presentation abstracts and links can be found here
> .
> Both meetings will be held in Zoom:
> https://zoom.us/j/99217163913?pwd=TldwZWZTQzNNc3ZGaThFOThlckFGQT09 . Your
> participation and feedback will be much appreciated!
>
> Best regards,
> Oleg Nenashev
> Jenkins GSoC Org Team
>
>

-- 
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/CAPfivLBUa4vyzL-_JF4VN8203Jg1Lnf3QR%3Dvxeq3BWcThEbnFQ%40mail.gmail.com.

Re: Jenkins Governance meeting on Jul 29, 2020

[Oleg Nenashev]

Recording of the meeting: https://www.youtube.com/watch?v=lGQGaJyFe0I At 
this meting we discussed the recent news (core release automation, next LTS 
baseline, public roadmap), reviewed results of the "Jenkins master" term 
replacement voting and next steps, CDF graduation status, Core 
Infrastructure Initiative checklist and the Jenkins Epipheo video proposal.

We also agreed to keep doing the Governance Meetings in Zoom by default in 
the future. To provide transparency, we will make sure to record meeting 
notes and to send summaries to the developer mailing list threads.

Best regards,
Oleg


On Wednesday, July 29, 2020 at 7:45:26 PM UTC+2, Oleg Nenashev wrote:
>
> Hi all,
>
> In 15 minutes we will have a regular Jenkins Governance Meeting. This time 
> we agreed to have it in Zoom: 
> https://zoom.us/j/99217163913?pwd=TldwZWZTQzNNc3ZGaThFOThlckFGQT09 . As 
> always, everyone is welcome to join the meeting and to participate in the 
> discussion/voting!
>
> Current agenda:
>
>- 
>
>News!
>- 
>   
>   Ongoing LTS baseline selection: 
>   https://groups.google.com/forum/#!topic/jenkinsci-dev/vtjcrJtZCnk
>   - 
>
>Terminology updates: Selecting the new name for the “Jenkins master” 
>(Alex)
>- 
>   
>   Dev list: 
>   https://groups.google.com/forum/#!topic/jenkinsci-dev/CLR55wMZwZ8
>   - 
>   
>   Results: 
>   https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_1bd92a17371a1ca5
>   - 
>   
>   Other updates
>   - 
>
>Core Infrastructure Initiative updates (Oleg)
>- 
>   
>   
>   
> https://groups.google.com/forum/#!msg/jenkinsci-dev/n1qH1K5_td0/a3SoeMGzBQAJ
>   - 
>   
>   https://bestpractices.coreinfrastructure.org/en/projects/3538
>   - 
>   
>   Highlight: reached the passing criteria. Current score is 133% 
>   - 
>
>Jenkins CDF graduation status report (Oleg)
>- 
>   
>   CDF TOC voting in the mailing list: 
>   
> https://lists.cd.foundation/g/cdf-toc/topic/vote_jenkins_graduation/75705780?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,75705780
>   - 
>
>I would like to request approval to use Jenkins Epipheo video on 
>jenkins.io (Alyssa)
>- 
>   
>   
>   
> https://groups.google.com/g/jenkins-advocacy-and-outreach-sig/c/EQUWRgdwrO8
>   - 
>
>Switching Governance meetings to Zoom by default (Oleg)
>
>  
> If you would like to add any other topics, please add them here 
> 
>
> Best regards,
> Oleg Nenashev
>
>

-- 
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/8e256eff-bfb6-43a0-bc2b-c5c364325783o%40googlegroups.com.