jenkins official kubernetes operator

[夏润泽]

Hi dev:
   In the cloud native domain, kubernetes is an important part, and now 
many software are using kubernetes operator to manage applications in 
kubernetes.
   Now we can manage jenkins through groovy scripts, casc plugins, etc.In 
particular, the casc plugin allows us to manage jenkins with declarative 
code.
   But I think there are still some problems in it. I deployed my jenkins 
in the kubernetes cluster and managed my jenkins through the groovy script 
and the casc plugin. But once the jenkins is started, I need to modify the 
configuration of the casc, then I need to submit the configuration to the 
jenkins dashborad, and the submitted configuration is not necessarily 
successful, and there is no failure record. In other words, although I have 
a casc configuration file, it is difficult for me to ensure that my 
environment is consistent with the casc configuration. Or at least let me 
know that my current configuration is incorrect, I need to fix it.
   If we can provide an official jenkins operator to manage jenkins in 
kubernetes, it must be great.
   I hope to hear your opinions.

Best wishes 
RunzeXia

-- 
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/7939b7df-2935-4aeb-a1f5-3f300990119f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reading console log of parallel stages

[Ullrich Hafner]

If a pipeline contains parallel stages, then the console log will contain an 
unordered mix of stdout messages of all parallel stages. This makes it 
impossible to decided which log message is from which parallel stage if I 
access the log using Run.getLogReader().

Since a couple of weeks the console log view shows in the frame border which 
log message is from which parallel stage, so it is somehow possible to obtain 
that information. Which API can I use to read the individual console log 
information of a parallel stage? 

-- 
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/50959DF5-2CB4-45AA-9BF3-5292F535587A%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Discussion: Community Onboarding/Outreach and Advocacy SIGs

[Marky Jackson]

I would like to be a lead or if that is full, a volunteer

> On Jan 14, 2019, at 2:24 PM, Liam Newman  wrote:
> 
> Marky, 
> 
> Are you saying you'd like to be one of the Leads for this SIG or just that 
> you want to be a member of it? 
> 
> -Liam 
> 
> On Tuesday, December 18, 2018 at 12:01:05 PM UTC-8, Marky Jackson wrote:
> I would like to volunteer 
> 
>> On Dec 18, 2018, at 11:59 AM, Oleg Nenashev > wrote:
>> 
>> I noticed that I have forgot to respond to Liam's question about the SIG 
>> leadership.
>> 
>> As a separate question: Who are potential owners of the SIG(s)?
>> 
>> Some candidates:
>> Oleg Nenashev
>> Tracy Miranda 
>> Liam Newman
>> (your name here - any voluteers?)
>> No volunteers here so far (beyond the list by Liam). SIGs may actually 
>> multiple leaders to balance the workload and to have more capacity (see 
>> Roles in JEP-4 ). 
>> We did it for GSoC and Platform SIGs, and I believe it can work well here as 
>> well. My proposal would be to just start the SIG with multiple leaders 
>> (whomever is active in the Jenkins community && shows interest in it), and 
>> then we can adjust going forward.
>> 
>> P.S: Personally I am interested to participate in organizing this SIG, and I 
>> will be happy to commit some time to this effort. I will have a very limited 
>> availability over the next months due to personal reasons and GSoC, but I 
>> will try to help where I can.
>> 
>> Best regards,
>> Oleg
>> 
>>  
>> On Wednesday, December 12, 2018 at 5:32:46 PM UTC+1, Oleg Nenashev wrote:
>> Option 3 is my preference, but I am OK with options 1/2 as well
>> 
>> 
>> On Tue, Dec 11, 2018 at 11:22 PM Liam Newman > wrote:
>> Oleg,
>> I totally agree with how you described the SIG's relationship with channels 
>> - there to help, not to specifically own/control the channels.
>> 
>> As to naming:
>> "Advocacy and Outreach"
>> "Outreach and Advocacy"
>> "Advocacy and Community Outreach"
>> "Community Outreach and Advocacy"
>> 
>> I've listed these in my order of preference, with my only -1 vote being #4.  
>>  Anyone else have an opinion? 
>> 
>> -L. 
>> 
>> On Sunday, December 9, 2018 at 1:41:28 AM UTC-8, Rick wrote:
>> In my opinion, anyone who wants to help advocacy the Jenkins could be part 
>> of the social media channels. Of course, the code of conduct is necessary. 
>> But how to running Twitter and WeChat or other social media channels. Maybe 
>> we could have a regular meeting to discuss.
>> 
>> On Sun, Dec 9, 2018 at 3:16 PM Oleg Nenashev > wrote:
>> Hi,
>> 
>> I do not think that such activity needs to be transferred unless Rick wants 
>> to do that. There are also many other outreach channels maintained my 
>> subprojects and other entities (e.g. Jenkins X, Evergreen, Jenkins RU, etc., 
>> etc.). My understanding is that:
>> The SIG is interested to help others to create such channels (as a part of 
>> outreach effort). E.g. it can help to create accounts and to promote them in 
>> the community
>> The SIG does not claim ownership of the social media channels unless it is 
>> agreed on
>> Best regards,
>> Oleg
>> 
>> On Sun, Dec 9, 2018 at 1:52 AM Lloyd Chang > wrote:
>> Curiously, would specific localization initiatives (e.g. Chinese 
>> Localization SIG's WeChat) be transferred to the broader umbrella of 
>> Outreach and Advocacy Mega-SIG?
>> 
>> For example: I view Twitter and WeChat as comparable mechanisms for 
>> advocacy; both would have measurable metrics re: followers and impressions.
>> 
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "Jenkins Developers" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/jenkinsci-dev/84vjWz_Ho1k/unsubscribe 
>> .
>> To unsubscribe from this group and all its topics, send an email to 
>> jenkinsci-de...@googlegroups.com <>.
>> 
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/4e219e41-f579-4316-a382-0c7cf72bd55c%40googlegroups.com
>>  
>> .
>> For more options, visit https://groups.google.com/d/optout 
>> .
>> 
>> -- 
>> 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-de...@googlegroups.com <>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCz0oyDmsKcmSz%2Biq9Sw0B6UQ%3DLqEdSYizYR8k-Uh4NuA%40mail.gmail.com
>>  
>> .
>> For more options, visit 

Re: Discussion: Community Onboarding/Outreach and Advocacy SIGs

[Liam Newman]

Marky, 

Are you saying you'd like to be one of the Leads for this SIG or just that 
you want to be a member of it? 

-Liam 

On Tuesday, December 18, 2018 at 12:01:05 PM UTC-8, Marky Jackson wrote:
>
> I would like to volunteer 
>
> On Dec 18, 2018, at 11:59 AM, Oleg Nenashev  > wrote:
>
> I noticed that I have forgot to respond to Liam's question about the SIG 
> leadership.
>
> As a separate question: Who are potential owners of the SIG(s)?
>>
>> Some candidates:
>>
>>- Oleg Nenashev
>>- Tracy Miranda 
>>- Liam Newman
>>- (your name here - any voluteers?)
>>
>> No volunteers here so far (beyond the list by Liam). SIGs may actually 
> multiple leaders to balance the workload and to have more capacity (see 
> Roles in JEP-4 ). 
> We did it for GSoC and Platform SIGs, and I believe it can work well here 
> as well. My proposal would be to just start the SIG with multiple leaders 
> (whomever is active in the Jenkins community && shows interest in it), and 
> then we can adjust going forward.
>
> P.S: Personally I am interested to participate in organizing this SIG, and 
> I will be happy to commit some time to this effort. I will have a very 
> limited availability over the next months due to personal reasons and GSoC, 
> but I will try to help where I can.
>
> Best regards,
> Oleg
>
>  
> On Wednesday, December 12, 2018 at 5:32:46 PM UTC+1, Oleg Nenashev wrote:
>>
>> Option 3 is my preference, but I am OK with options 1/2 as well
>>
>>
>> On Tue, Dec 11, 2018 at 11:22 PM Liam Newman > > wrote:
>>
>>> Oleg,
>>> I totally agree with how you described the SIG's relationship with 
>>> channels - there to help, not to specifically own/control the channels.
>>>
>>> As to naming:
>>>
>>>1. "Advocacy and Outreach"
>>>2. "Outreach and Advocacy"
>>>3. "Advocacy and Community Outreach"
>>>4. "Community Outreach and Advocacy"
>>>
>>>
>>> I've listed these in my order of preference, with my only -1 vote being 
>>> #4.   Anyone else have an opinion? 
>>>
>>> -L. 
>>>
>>> On Sunday, December 9, 2018 at 1:41:28 AM UTC-8, Rick wrote:

 In my opinion, anyone who wants to help advocacy the Jenkins could be 
 part of the social media channels. Of course, the code of conduct is 
 necessary. But how to running Twitter and WeChat or other social media 
 channels. Maybe we could have a regular meeting to discuss.

 On Sun, Dec 9, 2018 at 3:16 PM Oleg Nenashev  
 wrote:

> Hi,
>
> I do not think that such activity needs to be transferred unless Rick 
> wants to do that. There are also many other outreach channels maintained 
> my 
> subprojects and other entities (e.g. Jenkins X, Evergreen, Jenkins RU, 
> etc., etc.). My understanding is that:
>
>- The SIG is interested to help others to create such channels (as 
>a part of outreach effort). E.g. it can help to create accounts and to 
>promote them in the community
>- The SIG does not claim ownership of the social media channels 
>unless it is agreed on
>
> Best regards,
> Oleg
>
> On Sun, Dec 9, 2018 at 1:52 AM Lloyd Chang  wrote:
>
>> Curiously, would specific localization initiatives (e.g. Chinese 
>> Localization SIG's WeChat) be transferred to the broader umbrella of 
>> Outreach and Advocacy Mega-SIG?
>>
>> For example: I view Twitter and WeChat as comparable mechanisms for 
>> advocacy; both would have measurable metrics re: followers and 
>> impressions.
>>
>> -- 
>>
> You received this message because you are subscribed to a topic in the 
>> Google Groups "Jenkins Developers" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/jenkinsci-dev/84vjWz_Ho1k/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to 
>> jenkinsci-de...@googlegroups.com.
>
>
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/4e219e41-f579-4316-a382-0c7cf72bd55c%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> -- 
> 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-de...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCz0oyDmsKcmSz%2Biq9Sw0B6UQ%3DLqEdSYizYR8k-Uh4NuA%40mail.gmail.com
>  
> 

Request to become a Jenkins Core committer

[Matt Sicker]

Hello,

My name is Matt Sicker, currently working as a senior software engineer at
CloudBees with a focus on supporting open source Jenkins and various
supporting plugins. I've been contributing to Jenkins and related projects
since April 2018, and I've been a member of the Jenkins Security Team with
Daniel Beck, Wadeck Follonier, and Jeff Thompson, for about the same time
as well. I would like to request to become a committer to help collaborate
more on Jenkins itself as well as provide more eyes for merging PRs.

My PRs to jenkinsci:
https://github.com/pulls?utf8=%E2%9C%93=is%3Apr+author%3Ajvz+archived%3Afalse+user%3Ajenkinsci

My PRs to jenkins-core:
https://github.com/pulls?utf8=%E2%9C%93=is%3Apr+author%3Ajvz+archived%3Afalse+repo%3Ajenkinsci%2Fjenkins

My PRs to jenkins-x:
https://github.com/pulls?utf8=%E2%9C%93=is%3Apr+author%3Ajvz+archived%3Afalse+user%3Ajenkins-x

General query for my PRs related to Jenkins:
https://github.com/pulls?utf8=%E2%9C%93=is%3Apr+author%3Ajvz+archived%3Afalse+mentions%3Areviewbybees

-- 
Matt Sicker
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4oxHEjBE5e%2BoLeno4xt341aJsHLxDA5K83wGOHE3v0nA0A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request to join organization

[Daniel Beck]

I discussed this request with Fran out of band, and asked about some common 
issues causing problems in core maintenance, like ensuring new API is 
deliberate or @Restricted, or the need to keep binary (and to a lesser extent 
source) compatibility. With his background in preparing CloudBees product 
releases and ensuring tests run successfully (many of his past contributions) 
he's very familiar with the latter. The former should just be automated, but 
while we don't have that, I'll make sure he understands the requirements to not 
accidentally introduce new APIs.

I am in support of this request.


> On 27. Dec 2018, at 11:16, fjfernan...@cloudbees.com wrote:
> 
> Hi all,
> 
> I am Francisco Javier Fernández González, currently engineer at CloudBees. 
> During the last year I've been collaborating with some work of the community, 
> becoming co-maintainer of the Jenkinsfile-runner project with Oleg Nenashev 
> and Evaristo Gutiérrez, and maintainer of Folders plugin. I would like to 
> continue collaborating in the maintenance of Jenkins and its ecosystem of 
> plugins, and in terms of easing my collaborations and reviews, I would like 
> to become a member of the organization getting the merge permissions for the 
> core. Would it be possible?
> 
> Just in case you're interested in knowing more from me:
>   • My Jenkins JIRA user is fcojfernandez
>   • My github user is fcojfernandez
>   • My contributions to the jenkinsci organization: 
> https://github.com/pulls?utf8=%E2%9C%93=is%3Apr+author%3Afcojfernandez+archived%3Afalse+user%3Ajenkinsci+
>   • Specific contributions to jenkins-core: 
> https://github.com/jenkinsci/jenkins/pulls?utf8=%E2%9C%93=is%3Apr+author%3Afcojfernandez+
> 
> Best Regards!
> 
> -- 
> 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/3a997e95-4d44-4933-bc9e-a92c1a574644%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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/306EC450-E803-4BC5-B8B1-5C86012B6F7C%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.