Re: Proposal: Evaluating Twitter as code with @memkins

[Oleg Nenashev]

Hi all,

First edition of Twitter as Code is live!

   - GitHub Repo: https://github.com/jenkinsci/memkins
   - First tweet: https://twitter.com/memkins/status/1398437032632848388

The next step is to add meme image generation from code, with previews 
support.
All contributions are welcome!

Best regards,
Oleg

On Monday, May 10, 2021 at 8:06:34 PM UTC+2 Oleg Nenashev wrote:

> I will go ahead and setup a PoC tomorrow if no negative feedback
>
> On Monday, May 10, 2021 at 2:37:27 PM UTC+2 Mark Waite wrote:
>
>> +1 from me as well.  Thanks for doing it
>>
>> On Mon, May 10, 2021 at 5:20 AM Tim Jacomb  wrote:
>>
>>> +1
>>>
>>> On Mon, 10 May 2021 at 11:57, Oleg Nenashev  wrote:
>>>
 Dear all,

 Last week I created the new Jenkins-related Twitter account: 
 https://twitter.com/memkins. The goal of this channel is to repost 
 funny memes and comics about Jenkins, while delivering best practices to 
 end users. Although this channel will include more sarcasm and 
 self-criticism than the official channel, the plan is to keep it overall 
 positive w.r.t Jenkins. It will also remain within the Jenkins Code of 
 Conduct boundaries.

 In the Jenkins Advocacy and Outreach SIG we had many discussions about 
 adopting a social media as code approach so that we could simplify content 
 contributions and to simplify reviews. Currently we do it manually via 
 Tweetdeck and Gitter based content reviews, and the process is not that 
 productive. In the case of Twitter, there is a GitHub action for that: 
 https://github.com/gr2m/twitter-together . I briefly evaluated it for 
 personal use, but the value would be rather evaluating it in a shared 
 account. And it looks much more convenient to test it on Memkins instead 
 of 
 the official Jenkins accounts.

 With permission of the community, I would like to do the following:

- Create a jenkinsci/memkins GitHub repository
- Create a GitHub action which would post Tweets to @memkins. 
Effectively it means that, in addition to the current moderators, all 
GitHub Org Admins will get access to the account
- Evaluate and document the flow

 If the experiment goes well, we can later update the IRC bot (or use 
 another automation), to automate pull requests to the repository via a 
 chat 
 command or a GitHUb App form. Then we will be able to apply the same to 
 the 
 main @jenkinsci or other accounts if all goes well.

 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-de...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCYzYeVP-JPnPWXc9su8jFAP9AA2q56ifBhaaJZsnoZLw%40mail.gmail.com
  
 
 .

>>> -- 
>>>
>> You received this message because you are subscribed to the Google Groups 
>>> "Jenkins Advocacy and Outreach SIG" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to jenkins-advocacy-and-o...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkins-advocacy-and-outreach-sig/CAH-3BicYwOQeftNxTvRHaFHCbqNd3mQY9oKNowq_UBCyu74vmA%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/6ad5bdf6-b1b2-473e-b4e6-ba1c3a481321n%40googlegroups.com.

Re: [Heads-up] Removing commons-digester from Jenkins Core (and the link with our plugins EOL policy discussion :-))

[Basil Crow]

+1 from me

-- 
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/CAFwNDjrQBdo645Zs5cboXStgo_7zJEEsnQ3iCxQ6qC4iw4M%3D4g%40mail.gmail.com.

Re: Stapler IntelliJ Plugin JetBrains Marketplace listing

[Oleg Nenashev]

FTR the plugin was moved to the jenkinsci GitHub 
organization: https://github.com/jenkinsci/idea-stapler-plugin
Denys will be an admin there once he accepts the invitation to the GitHub 
org

On Monday, May 10, 2021 at 6:33:22 PM UTC+2 Oleg Nenashev wrote:

> FTR I started https://groups.google.com/g/jenkinsci-dev/c/1T3yDHl1nEQ . I 
> have a partially-completed proposal for Stapler in my drafts, so I went 
> ahead and started the discussion
>
> On Monday, May 10, 2021 at 2:16:38 PM UTC+2 Jesse Glick wrote:
>
>> On Fri, May 7, 2021 at 7:13 PM Oleg Nenashev  wrote:
>>
>>> should we go ahead and move the repository to the jenkinsci org?
>>>
>>
>> Fine with me. We should probably move `stapler/stapler` itself 
>> (INFRA-2908); we have already started publishing to the Jenkins Artifactory 
>> rather than OSSRH. 
>>
>

-- 
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/9e8ecbc2-adb2-4a65-bd5d-ee2b53d7b384n%40googlegroups.com.

Re: [jenkins-infra] Migrate chat channels from freenode to libera.chat

[Oleg Nenashev]

+1 for going ahead and making the changes official
Maybe we need a short announcement blog, WDYT?

On Friday, May 28, 2021 at 10:00:45 AM UTC+2 timja...@gmail.com wrote:

> Thanks all
>
> Last call for any feedback before we merge the Jenkins.io PR
>
> The channels have all been set up.
>
> If you had 'voice' on freenode and want it on Libera then please verify 
> yourself with someone who has voice/op on libera out of band (email / 
> gitter / github, etc).
> A number of people have left freenode and deleted their accounts already.
>
>
>
>
> On Wed, 26 May 2021 at 20:14, Tim Jacomb  wrote:
>
>> The ircbot has been moved over
>>
>> On Wed, 26 May 2021 at 19:12, 'Gavin Mogan' via Jenkins Developers <
>> jenkin...@googlegroups.com> wrote:
>>
>>> Project registration has been completed since Saturday I think. 
>>>
>>> I've removed the channel locks so anyone can create can register 
>>> channels, project owners can claim the channel if it ever becomes an issue.
>>>
>>> Cloaks can be requested by any group member.
>>>
>>> Jenkins group members:
>>> Primary (can claim. Can manage group member lists)
>>> halkeye (me)
>>> Olblak
>>>
>>> Secondary (primary plus requesting cloaks for users)
>>> Nobody yet
>>>
>>>
>>> Cloaks:
>>> We have jenkins/* reserved
>>> I'm thinking jenkins/contributor/$nick for most people, then maybe board 
>>> specific if we care.
>>>
>>> On Wed., May 26, 2021, 8:01 a.m. Oleg Nenashev,  
>>> wrote:
>>>
 FYI see the project registration instructions here:
> https://libera.chat/chanreg#project-registration
>
 AFAICT from the Governance Board discussion, Gavin and Olivier have 
 already submitted a registration request.
 It just takes time to process



 On Wed, May 26, 2021 at 4:57 PM Basil Crow  wrote:

> +1. I opened a PR to cover updating the references on jenkins.io:
> https://github.com/jenkins-infra/jenkins.io/pull/4384
>
> FYI see the project registration instructions here:
> https://libera.chat/chanreg#project-registration
>
> -- 
> 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/pEcun5ZSfgo/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/CAFwNDjqK%2BDwkLWdBUDh1iku45C9JjxC5NLXwguXAb3c%3Djx1i7g%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-de...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLDg7kSiyUHk6a4VgVHurG-8AcKfZHsSpCv0RG3_bpyFDg%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-de...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_Duu4zWLgXUKN-PC20hdNCD_ct5kPufF9jj9Wh9d9GfbrmQ%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/fd8059af-a567-4be1-ae7d-6dad12cb04e3n%40googlegroups.com.

Re: [workflow-durable-task-step-plugin] Add tool installer for Powershell Core

['Gavin Mogan' via Jenkins Developers]

I think it's deprecated in the same way freestyle is. Code isn't being
removed just not the recommended solution.

On Fri., May 28, 2021, 8:14 a.m. Tony Noble,  wrote:

> "The `ToolInstallation` system is generally deprecated."
>
> Out of interest, how long has this been the case?  For a number of
> reasons, pre-built and configured VMs or containers have not been an option
> for us and the ability to make tools available on demand for development
> teams' builds is pretty key to the service we provide.
>
> In an Enterprise environment with a lot of historical software (and years
> of technical debt that can't quickly be fixed), the availability of
> different versions of Maven, Ant, Java and similar for building is pretty
> important.  And pre-installing them on every single worker VM is simply not
> practical.  Similarly, neither is installing every new version of every
> tool on every VM.
>
>
> On Tue, May 25, 2021 at 11:42 PM Tim Van Holder 
> wrote:
>
>> I'll have another look at that plugin - at first glance, it seems to have
>> hardcoded assumptions on Windows vs Linux.
>> And the point here is to have tool installations for specific PowerShell (
>> *not* Windows PowerShell) versions downloaded and deployed from GitHub
>> releases, regardless of platform.
>>
>> As for the build wrapper, the pwsh step seems to resist proper selection
>> of which shell to run.
>> In a freestyle job, the wrapper works. But that's because it only has
>> equivalents of bat and sh. Running pwsh from those uses the executable from
>> the selected tool installation just fine.
>>
>> However, in a pipeline, a pwsh step inside the wrapper seems to forcibly
>> put "C:\Program Files\PowerShell\7" at the start of PATH, overriding
>> what the wrapper put in place.
>> That feels broken to me - even using a tool section has no effect.
>> It would also be counterintuitive to have to use sh/bat steps to be able
>> to use a tool-based pwsh installation (and the whole point of using a pwsh
>> step would be to not have to care whether it's linux/osx/windows/...).
>>
>> And yes, something like JENKINS-28718
>>  would remove the need
>> for more specific withXXX wrappers - but that proposal as-is seems to
>> assume installation names are globally unique - and it is my understanding
>> they're only unique within a particular installation type. For example, I
>> might have both a PowerShell installation named 'LTS' and a .NET SDK
>> installation named 'LTS', so "withTool('LTS') { }" would be ambiguous.
>> Also, an installation's setup is not necessarily limited to just a home
>> folder, so $(tool 'XXX') might only handle part of what's needed for a
>> given tool.
>>
>>
>> On Mon, 24 May 2021 at 17:40, Jesse Glick  wrote:
>>
>>> On Fri, May 21, 2021 at 5:51 PM Tim Van Holder 
>>> wrote:
>>>
 PowerShell Core is multi-platform and installable via zip or tarball.
 As such, I'd be inclined to want to add a tool installer for it

>>>
>>> The `ToolInstallation` system is generally deprecated. Modern CI setups
>>> are expected to use VMs or containers with appropriate tools preinstalled.
>>> So I would probably recommend creating a separate plugin for the likely
>>> small number of users who would benefit. Or better yet, just check whether
>>> the existing plugin
>>> 
>>>  works
>>> for you.
>>>
>>>
 a withPwsh (or withPowerShellCore?) step would also make sense, to put
 a particular install in PATH for a delimited set of steps (as I understand
 it, with the tool section, it always applies to an entire stage)

>>>
>>> There is limited flexibility in Declarative syntax. For Scripted syntax,
>>> this just sounds like it would be better covered by the general
>>> JENKINS-28718 . A
>>> dedicated block-scoped step makes sense for logic that does something more
>>> complicated than bind a `ToolInstallation` to a `$PATH` entry.
>>>
>>> --
>>> 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/CANfRfr2Q66ArFPTDY2V8eeQn3t4AR_8giQc%3DtsptoDX5n5e8aQ%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
>> 

Re: [workflow-durable-task-step-plugin] Add tool installer for Powershell Core

[Tony Noble]

"The `ToolInstallation` system is generally deprecated."

Out of interest, how long has this been the case?  For a number of reasons,
pre-built and configured VMs or containers have not been an option for us
and the ability to make tools available on demand for development teams'
builds is pretty key to the service we provide.

In an Enterprise environment with a lot of historical software (and years
of technical debt that can't quickly be fixed), the availability of
different versions of Maven, Ant, Java and similar for building is pretty
important.  And pre-installing them on every single worker VM is simply not
practical.  Similarly, neither is installing every new version of every
tool on every VM.


On Tue, May 25, 2021 at 11:42 PM Tim Van Holder 
wrote:

> I'll have another look at that plugin - at first glance, it seems to have
> hardcoded assumptions on Windows vs Linux.
> And the point here is to have tool installations for specific PowerShell (
> *not* Windows PowerShell) versions downloaded and deployed from GitHub
> releases, regardless of platform.
>
> As for the build wrapper, the pwsh step seems to resist proper selection
> of which shell to run.
> In a freestyle job, the wrapper works. But that's because it only has
> equivalents of bat and sh. Running pwsh from those uses the executable from
> the selected tool installation just fine.
>
> However, in a pipeline, a pwsh step inside the wrapper seems to forcibly
> put "C:\Program Files\PowerShell\7" at the start of PATH, overriding what
> the wrapper put in place.
> That feels broken to me - even using a tool section has no effect.
> It would also be counterintuitive to have to use sh/bat steps to be able
> to use a tool-based pwsh installation (and the whole point of using a pwsh
> step would be to not have to care whether it's linux/osx/windows/...).
>
> And yes, something like JENKINS-28718
>  would remove the need
> for more specific withXXX wrappers - but that proposal as-is seems to
> assume installation names are globally unique - and it is my understanding
> they're only unique within a particular installation type. For example, I
> might have both a PowerShell installation named 'LTS' and a .NET SDK
> installation named 'LTS', so "withTool('LTS') { }" would be ambiguous.
> Also, an installation's setup is not necessarily limited to just a home
> folder, so $(tool 'XXX') might only handle part of what's needed for a
> given tool.
>
>
> On Mon, 24 May 2021 at 17:40, Jesse Glick  wrote:
>
>> On Fri, May 21, 2021 at 5:51 PM Tim Van Holder 
>> wrote:
>>
>>> PowerShell Core is multi-platform and installable via zip or tarball.
>>> As such, I'd be inclined to want to add a tool installer for it
>>>
>>
>> The `ToolInstallation` system is generally deprecated. Modern CI setups
>> are expected to use VMs or containers with appropriate tools preinstalled.
>> So I would probably recommend creating a separate plugin for the likely
>> small number of users who would benefit. Or better yet, just check whether
>> the existing plugin
>> 
>>  works
>> for you.
>>
>>
>>> a withPwsh (or withPowerShellCore?) step would also make sense, to put a
>>> particular install in PATH for a delimited set of steps (as I understand
>>> it, with the tool section, it always applies to an entire stage)
>>>
>>
>> There is limited flexibility in Declarative syntax. For Scripted syntax,
>> this just sounds like it would be better covered by the general
>> JENKINS-28718 . A
>> dedicated block-scoped step makes sense for logic that does something more
>> complicated than bind a `ToolInstallation` to a `$PATH` entry.
>>
>> --
>> 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/CANfRfr2Q66ArFPTDY2V8eeQn3t4AR_8giQc%3DtsptoDX5n5e8aQ%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/CAKMi--BZwB%2BL6T6SXvuat9QjVnB5STF3iX1qJLxPHbqfJQqgWw%40mail.gmail.com
> 
> .
>

-- 
You 

Re: Discourse as the default communication channel?

[Oleg Nenashev]

>
> experiment with language community channels

Creating sub-categories, e.g. for francophone, Spanish speaking or Russian
speaking communities

> experiment user outreach tools
> Do you have something in mind?
>
I would start from a call for topic proposals for the Jenkins Contributor
Summit.
Later we can move many GSoC and Hacktoberfest discussions there


On Fri, May 28, 2021, 16:09 'Olblak' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> After additional testing, I decided to allow user registration, on
> community.jenkins.io.
> I needed it to test the Github integration.
> We can still revert that decision if needed
>
>
>
> On Fri, May 28, 2021, at 1:57 PM, 'Olblak' via Jenkins Developers wrote:
>
> Hi Oleg,
>
> Could you elaborate
> > experiment with language community channels
>
> > experiment user outreach tools
> Do you have something in mind?
>
> On Fri, May 28, 2021, at 1:00 PM, Oleg Nenashev wrote:
>
> I would be interested to particupate as the Events officer. I would like
> to experiment with language community channels and user outreach tools.
>
> Thanks to everyone for driving this!
>
>
> On Fri, May 28, 2021, 11:52 'Olblak' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com> wrote:
>
>
> I would like to highlight the discussion about the different possible
> authentication with an option to vote
> -> https://community.jenkins.io/t/authentication-method-used/36
>
> I understand not everybody at this point will be able to vote directly
> from Discourse so feel free to either request access to be part of the
> evaluation process or just provide feedback here.
>
> At this stage, Bruce, Gavin, Tim and I have admin access and can send
> invites.
> Once further in the process, we'll reevaluate admin access.
>
> Cheers
>
>
> On Thu, May 27, 2021, at 11:06 PM, Mark Waite wrote:
>
> I'd like to be part of the test.
>
> On Thu, May 27, 2021 at 2:28 PM 'Gavin Mogan' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com> wrote:
>
> The tech it uses can give you pretty live updates, but its designed as a
> forum.
>
> I've sent you a DM on IRC with an invite link for now.
>
>
>
> On Thu, May 27, 2021 at 1:08 PM Slide  wrote:
>
> I would like access please. Just a question, as I am very unfamiliar with
> Discourse. Is it a real time communication medium, a la IRC, or something
> more akin to a forum?
>
> On Thu, May 27, 2021 at 11:57 AM 'Olblak' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com> wrote:
>
> For whoever is interested to participate to the Discourse project,
> we started discussing over there as a way to test it and get more familiar
> with the tool.
> -> https://community.jenkins.io/t/discussion-about-categories/27/12
>
> Feel free to request an access as I didn't have the time yet to really
> investigate the consequences of the different authentication methods.
>
> On Tue, May 25, 2021, at 8:46 PM, 'Olblak' via Jenkins Developers wrote:
> > Hi Bruce,
> >
> > Thank you for stepping up, you already provided a lot of information
> > here.
> > And let's not assume we all know everything about discourse as we
> > definitely don't.
> > As you are interested to help with this project, I'll send you an
> > invite to "community.jenkins.io".
> >
> > As long as we don't have an agreement on the authentication mechanism,
> > I'll work on invite-only.
> >
> > Regarding identifying what we expected from Discourse, Bruce made a
> > good statement that discourse is what we want it to be, so here what I
> > would like it to solve.
> > I would like to easily identify and participate in discussion about
> > topics that interested me across different sub-project. So as an
> > initial step, Oleg suggestion seems right to me.
> >
> > On my side, I'll investigate the different authentication options.
> > Today during the infrastructure Oleg made a good remark,  we would like
> > to ideally move away from maintaining our Ldap service and we would
> > like to offer more alternatives than just using a Github account so
> > maybe using Linux foundation accounts would be better.
> >
> >
> > On Tue, May 25, 2021, at 7:16 PM, Matt Sicker wrote:
> > > Ha, so I was. Oops!
> > >
> > > On Tue, 25 May 2021 at 10:32, 'Gavin Mogan' via Jenkins Developers
> > >  wrote:
> > > >
> > > > Matt. It's often a confusion point. Discourse is more like a
> form/mailing list type thing. Discord is realtime communication. Sounds
> like your describing discord.
> > > >
> > > > On Tue., May 25, 2021, 6:52 a.m. Matt Sicker, 
> wrote:
> > > >>
> > > >> I’ve never used Discourse outside of video games, but it seems
> easier to set up public communities on than Slack or other things we’ve
> tried here so far. While in theory I’d prefer something open like Matrix, I
> do agree that we should try to minimize the number of services to maintain
> ourselves.
> > > >>
> > > >> On Tue, May 25, 2021 at 07:45 Oleg Nenashev 
> wrote:
> > > >>>
> > > >>> Hi all,
> > > >>>
> > > >>> Thanks to Olivier for starting 

Re: Discourse as the default communication channel?

['Olblak' via Jenkins Developers]

After additional testing, I decided to allow user registration, on 
community.jenkins.io.
I needed it to test the Github integration.
We can still revert that decision if needed



On Fri, May 28, 2021, at 1:57 PM, 'Olblak' via Jenkins Developers wrote:
> Hi Oleg, 
> 
> Could you elaborate 
> > experiment with language community channels
> 
> > experiment user outreach tools
> Do you have something in mind? 
> 
> On Fri, May 28, 2021, at 1:00 PM, Oleg Nenashev wrote:
>> I would be interested to particupate as the Events officer. I would like to 
>> experiment with language community channels and user outreach tools.
>> 
>> Thanks to everyone for driving this!
>> 
>> 
>> On Fri, May 28, 2021, 11:52 'Olblak' via Jenkins Developers 
>>  wrote:
>>> __
>>> I would like to highlight the discussion about the different possible 
>>> authentication with an option to vote
>>> -> https://community.jenkins.io/t/authentication-method-used/36
>>> 
>>> I understand not everybody at this point will be able to vote directly from 
>>> Discourse so feel free to either request access to be part of the 
>>> evaluation process or just provide feedback here.
>>> 
>>> At this stage, Bruce, Gavin, Tim and I have admin access and can send 
>>> invites.
>>> Once further in the process, we'll reevaluate admin access.
>>> 
>>> Cheers
>>> 
>>> 
>>> On Thu, May 27, 2021, at 11:06 PM, Mark Waite wrote:
 I'd like to be part of the test.
 
 On Thu, May 27, 2021 at 2:28 PM 'Gavin Mogan' via Jenkins Developers 
  wrote:
> The tech it uses can give you pretty live updates, but its designed as a 
> forum.
> 
> I've sent you a DM on IRC with an invite link for now.
> 
> 
> 
> On Thu, May 27, 2021 at 1:08 PM Slide  wrote:
>> I would like access please. Just a question, as I am very unfamiliar 
>> with Discourse. Is it a real time communication medium, a la IRC, or 
>> something more akin to a forum? 
>> 
>> On Thu, May 27, 2021 at 11:57 AM 'Olblak' via Jenkins Developers 
>>  wrote:
>>> For whoever is interested to participate to the Discourse project, 
>>> we started discussing over there as a way to test it and get more 
>>> familiar with the tool.
>>> -> https://community.jenkins.io/t/discussion-about-categories/27/12
>>> 
>>> Feel free to request an access as I didn't have the time yet to really 
>>> investigate the consequences of the different authentication methods.
>>> 
>>> On Tue, May 25, 2021, at 8:46 PM, 'Olblak' via Jenkins Developers wrote:
>>> > Hi Bruce, 
>>> > 
>>> > Thank you for stepping up, you already provided a lot of information 
>>> > here.
>>> > And let's not assume we all know everything about discourse as we 
>>> > definitely don't.
>>> > As you are interested to help with this project, I'll send you an 
>>> > invite to "community.jenkins.io".
>>> > 
>>> > As long as we don't have an agreement on the authentication 
>>> > mechanism, 
>>> > I'll work on invite-only.
>>> > 
>>> > Regarding identifying what we expected from Discourse, Bruce made a 
>>> > good statement that discourse is what we want it to be, so here what 
>>> > I 
>>> > would like it to solve.
>>> > I would like to easily identify and participate in discussion about 
>>> > topics that interested me across different sub-project. So as an 
>>> > initial step, Oleg suggestion seems right to me.
>>> >  
>>> > On my side, I'll investigate the different authentication options. 
>>> > Today during the infrastructure Oleg made a good remark,  we would 
>>> > like 
>>> > to ideally move away from maintaining our Ldap service and we would 
>>> > like to offer more alternatives than just using a Github account so 
>>> > maybe using Linux foundation accounts would be better.
>>> > 
>>> > 
>>> > On Tue, May 25, 2021, at 7:16 PM, Matt Sicker wrote:
>>> > > Ha, so I was. Oops!
>>> > > 
>>> > > On Tue, 25 May 2021 at 10:32, 'Gavin Mogan' via Jenkins Developers
>>> > >  wrote:
>>> > > >
>>> > > > Matt. It's often a confusion point. Discourse is more like a 
>>> > > > form/mailing list type thing. Discord is realtime communication. 
>>> > > > Sounds like your describing discord.
>>> > > >
>>> > > > On Tue., May 25, 2021, 6:52 a.m. Matt Sicker,  
>>> > > > wrote:
>>> > > >>
>>> > > >> I’ve never used Discourse outside of video games, but it seems 
>>> > > >> easier to set up public communities on than Slack or other 
>>> > > >> things we’ve tried here so far. While in theory I’d prefer 
>>> > > >> something open like Matrix, I do agree that we should try to 
>>> > > >> minimize the number of services to maintain ourselves.
>>> > > >>
>>> > > >> On Tue, May 25, 2021 at 07:45 Oleg Nenashev 
>>> > > >>  wrote:
>>> > > >>>
>>> > > >>> Hi all,
>>> > > >>>
>>> 

Re: [jenkins-infra] Elastic Sponsorship for OpenTelemetry usage for community Jenkins instances

['Cyrille Le Clerc' via Jenkins Developers]

Thank you Damien.

Elastic is very excited to collaborate with the Jenkins community on better 
observability for Jenkins and for CI/CD at large.
Please note that these observability are vendor neutral, there is no vendor 
lock-in and what we will accomplish with the Elastic Observability backend 
will be achievable with other observability solution that also integrate 
with OpenTelemetry such as Jaeger and Prometheus. 

Victor, Ivan and I will do our best to offer an unprecedented User 
Experience with Elastic Observability there will be no lock in, it will 
alway be possible to switch to other observability backends :-) 

Cyrille

On Friday, May 28, 2021 at 12:59:06 PM UTC+2 Oleg Nenashev wrote:

> Connecting ci.jenkins.io looks perfectly fine to me. There is no 
> sensitive data on this instance. For other Jenkins instances (infra, 
> release, trusted-ci, cert, ...) a sign-off from the Jenkins Security 
> Officer is required IMHO
>
> On Fri, May 28, 2021, 10:40 Tim Jacomb  wrote:
>
>> Sounds great
>>
>> On Fri, 28 May 2021 at 09:30, Damien Duportal  
>> wrote:
>>
>>> [Cross posted on jenkins-dev and jenkins-infra]
>>>
>>> Hello dear community,
>>>
>>> During the last Jenkins infrastructure weekly meeting (2021-05-25 - 
>>> Notes -with recording link: https://hackmd.io/sBywc0IfRraU93aNETVwkw), 
>>> Victor Martinez and Iván Fernández from Elastic did a demonstration of the 
>>> opentelemetry plugin used with an Elastic APM platform.
>>> The goal was to demonstrate how the build metrics could be used with 
>>> distributed tracing: please check the notes, video and 
>>> https://plugins.jenkins.io/opentelemetry/ for more details.
>>>
>>>
>>> Victor and Ivan's employer, Elastic Inc. is proposing to sponsor the 
>>> Jenkins project by providing an APM instance that could be used along with 
>>> opentelemetry plugin, and a bit support to get it configured and maintained.
>>> Their interest is to study what are our (Jenkins community) usages (and 
>>> obviously mentioning that we are using it).
>>>
>>> The proposal from the Infrastructure team is to provide this service for 
>>> the 2 following use cases:
>>>
>>>- For users of ci.jenkins.io (core and plugins contributors) to get 
>>>build metrics and traces of their projects. It could help a lot for 
>>>performances tracking, and much more as "Jenkins Pipeline level metrics"
>>>- For infrastructure maintainers of ci.jenkins.io to track the 
>>>agents allocations and their errors, to improve the QoS of the build 
>>> farm, 
>>>as the pure infrastructure metrics is not enough because issues come 
>>> from 
>>>different areas (infra, Cloud providers, Jenkins configuration, Pipeline 
>>>usages, etc.)
>>>
>>>
>>> It could be a great opportunity for whoever interested in better 
>>> understanding Jenkins behavior. As we'll try to identify typical use cases 
>>> that we want to better understand and then build dashboards using metric.
>>> The challenge we face on the Jenkins infrastructure is that it's pretty 
>>> easy to know if Jenkins is running. But not so much if it's working in an 
>>> efficient way.
>>>
>>> The plan would be the following:
>>>
>>>- Start by a PoC on a private Jenkins instance  (e.g. 
>>>infra.ci.jenkins.io)
>>>   - Install the plugin
>>>   - Check APM instance access with Elastic
>>>   - Configure the plugin to point to the APM
>>>   - Bring back the conclusion to the community (by email here, blog 
>>>   post, meetup, whatever)
>>>- Once the configuration is straightforward, deploying to 
>>>ci.jenkins.io, targeting as much publicly available dashboards and 
>>>data as possible, as service for the ci.jenkins.io users.
>>>
>>> What do you think about this topic, what would be your thoughts or red 
>>> flags?
>>>
>>> Cheers,
>>>
>>> For the Infra. team,
>>> Damien DUPORTAL
>>>
>>> PS: by default, without any blocker or red flags, we (the infra.team) 
>>> will proceed with the infra.ci setup described in this email the 1st of 
>>> June.
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Jenkins Infrastructure" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to jenkins-infr...@googlegroups.com.
>>> To view this discussion on the web, visit 
>>> https://groups.google.com/d/msgid/jenkins-infra/0A4790E7-DF29-4C36-AAF3-320763D230B9%40gmail.com
>>>  
>>> 
>>> .
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Infrastructure" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkins-infr...@googlegroups.com.
>>
> To view this discussion on the web, visit 
>> 

Re: Discourse as the default communication channel?

['Olblak' via Jenkins Developers]

Hi Oleg, 

Could you elaborate 
> experiment with language community channels

> experiment user outreach tools
Do you have something in mind? 

On Fri, May 28, 2021, at 1:00 PM, Oleg Nenashev wrote:
> I would be interested to particupate as the Events officer. I would like to 
> experiment with language community channels and user outreach tools.
> 
> Thanks to everyone for driving this!
> 
> 
> On Fri, May 28, 2021, 11:52 'Olblak' via Jenkins Developers 
>  wrote:
>> __
>> I would like to highlight the discussion about the different possible 
>> authentication with an option to vote
>> -> https://community.jenkins.io/t/authentication-method-used/36
>> 
>> I understand not everybody at this point will be able to vote directly from 
>> Discourse so feel free to either request access to be part of the evaluation 
>> process or just provide feedback here.
>> 
>> At this stage, Bruce, Gavin, Tim and I have admin access and can send 
>> invites.
>> Once further in the process, we'll reevaluate admin access.
>> 
>> Cheers
>> 
>> 
>> On Thu, May 27, 2021, at 11:06 PM, Mark Waite wrote:
>>> I'd like to be part of the test.
>>> 
>>> On Thu, May 27, 2021 at 2:28 PM 'Gavin Mogan' via Jenkins Developers 
>>>  wrote:
 The tech it uses can give you pretty live updates, but its designed as a 
 forum.
 
 I've sent you a DM on IRC with an invite link for now.
 
 
 
 On Thu, May 27, 2021 at 1:08 PM Slide  wrote:
> I would like access please. Just a question, as I am very unfamiliar with 
> Discourse. Is it a real time communication medium, a la IRC, or something 
> more akin to a forum? 
> 
> On Thu, May 27, 2021 at 11:57 AM 'Olblak' via Jenkins Developers 
>  wrote:
>> For whoever is interested to participate to the Discourse project, 
>> we started discussing over there as a way to test it and get more 
>> familiar with the tool.
>> -> https://community.jenkins.io/t/discussion-about-categories/27/12
>> 
>> Feel free to request an access as I didn't have the time yet to really 
>> investigate the consequences of the different authentication methods.
>> 
>> On Tue, May 25, 2021, at 8:46 PM, 'Olblak' via Jenkins Developers wrote:
>> > Hi Bruce, 
>> > 
>> > Thank you for stepping up, you already provided a lot of information 
>> > here.
>> > And let's not assume we all know everything about discourse as we 
>> > definitely don't.
>> > As you are interested to help with this project, I'll send you an 
>> > invite to "community.jenkins.io".
>> > 
>> > As long as we don't have an agreement on the authentication mechanism, 
>> > I'll work on invite-only.
>> > 
>> > Regarding identifying what we expected from Discourse, Bruce made a 
>> > good statement that discourse is what we want it to be, so here what I 
>> > would like it to solve.
>> > I would like to easily identify and participate in discussion about 
>> > topics that interested me across different sub-project. So as an 
>> > initial step, Oleg suggestion seems right to me.
>> >  
>> > On my side, I'll investigate the different authentication options. 
>> > Today during the infrastructure Oleg made a good remark,  we would 
>> > like 
>> > to ideally move away from maintaining our Ldap service and we would 
>> > like to offer more alternatives than just using a Github account so 
>> > maybe using Linux foundation accounts would be better.
>> > 
>> > 
>> > On Tue, May 25, 2021, at 7:16 PM, Matt Sicker wrote:
>> > > Ha, so I was. Oops!
>> > > 
>> > > On Tue, 25 May 2021 at 10:32, 'Gavin Mogan' via Jenkins Developers
>> > >  wrote:
>> > > >
>> > > > Matt. It's often a confusion point. Discourse is more like a 
>> > > > form/mailing list type thing. Discord is realtime communication. 
>> > > > Sounds like your describing discord.
>> > > >
>> > > > On Tue., May 25, 2021, 6:52 a.m. Matt Sicker,  
>> > > > wrote:
>> > > >>
>> > > >> I’ve never used Discourse outside of video games, but it seems 
>> > > >> easier to set up public communities on than Slack or other things 
>> > > >> we’ve tried here so far. While in theory I’d prefer something 
>> > > >> open like Matrix, I do agree that we should try to minimize the 
>> > > >> number of services to maintain ourselves.
>> > > >>
>> > > >> On Tue, May 25, 2021 at 07:45 Oleg Nenashev 
>> > > >>  wrote:
>> > > >>>
>> > > >>> Hi all,
>> > > >>>
>> > > >>> Thanks to Olivier for starting this discussion and for 
>> > > >>> confirming sponsorship for Discourse. This is definitely 
>> > > >>> something we could use to address the current sprawl of Jenkins 
>> > > >>> communication channels. Many channels like User Mailing list, 
>> > > >>> some SIG mailing lists and many Gitter channels could be 
>> > > >>> replaced by 

Re: Discourse as the default communication channel?

[Oleg Nenashev]

I would be interested to particupate as the Events officer. I would like to
experiment with language community channels and user outreach tools.

Thanks to everyone for driving this!


On Fri, May 28, 2021, 11:52 'Olblak' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> I would like to highlight the discussion about the different possible
> authentication with an option to vote
> -> https://community.jenkins.io/t/authentication-method-used/36
>
> I understand not everybody at this point will be able to vote directly
> from Discourse so feel free to either request access to be part of the
> evaluation process or just provide feedback here.
>
> At this stage, Bruce, Gavin, Tim and I have admin access and can send
> invites.
> Once further in the process, we'll reevaluate admin access.
>
> Cheers
>
>
> On Thu, May 27, 2021, at 11:06 PM, Mark Waite wrote:
>
> I'd like to be part of the test.
>
> On Thu, May 27, 2021 at 2:28 PM 'Gavin Mogan' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com> wrote:
>
> The tech it uses can give you pretty live updates, but its designed as a
> forum.
>
> I've sent you a DM on IRC with an invite link for now.
>
>
>
> On Thu, May 27, 2021 at 1:08 PM Slide  wrote:
>
> I would like access please. Just a question, as I am very unfamiliar with
> Discourse. Is it a real time communication medium, a la IRC, or something
> more akin to a forum?
>
> On Thu, May 27, 2021 at 11:57 AM 'Olblak' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com> wrote:
>
> For whoever is interested to participate to the Discourse project,
> we started discussing over there as a way to test it and get more familiar
> with the tool.
> -> https://community.jenkins.io/t/discussion-about-categories/27/12
>
> Feel free to request an access as I didn't have the time yet to really
> investigate the consequences of the different authentication methods.
>
> On Tue, May 25, 2021, at 8:46 PM, 'Olblak' via Jenkins Developers wrote:
> > Hi Bruce,
> >
> > Thank you for stepping up, you already provided a lot of information
> > here.
> > And let's not assume we all know everything about discourse as we
> > definitely don't.
> > As you are interested to help with this project, I'll send you an
> > invite to "community.jenkins.io".
> >
> > As long as we don't have an agreement on the authentication mechanism,
> > I'll work on invite-only.
> >
> > Regarding identifying what we expected from Discourse, Bruce made a
> > good statement that discourse is what we want it to be, so here what I
> > would like it to solve.
> > I would like to easily identify and participate in discussion about
> > topics that interested me across different sub-project. So as an
> > initial step, Oleg suggestion seems right to me.
> >
> > On my side, I'll investigate the different authentication options.
> > Today during the infrastructure Oleg made a good remark,  we would like
> > to ideally move away from maintaining our Ldap service and we would
> > like to offer more alternatives than just using a Github account so
> > maybe using Linux foundation accounts would be better.
> >
> >
> > On Tue, May 25, 2021, at 7:16 PM, Matt Sicker wrote:
> > > Ha, so I was. Oops!
> > >
> > > On Tue, 25 May 2021 at 10:32, 'Gavin Mogan' via Jenkins Developers
> > >  wrote:
> > > >
> > > > Matt. It's often a confusion point. Discourse is more like a
> form/mailing list type thing. Discord is realtime communication. Sounds
> like your describing discord.
> > > >
> > > > On Tue., May 25, 2021, 6:52 a.m. Matt Sicker, 
> wrote:
> > > >>
> > > >> I’ve never used Discourse outside of video games, but it seems
> easier to set up public communities on than Slack or other things we’ve
> tried here so far. While in theory I’d prefer something open like Matrix, I
> do agree that we should try to minimize the number of services to maintain
> ourselves.
> > > >>
> > > >> On Tue, May 25, 2021 at 07:45 Oleg Nenashev 
> wrote:
> > > >>>
> > > >>> Hi all,
> > > >>>
> > > >>> Thanks to Olivier for starting this discussion and for confirming
> sponsorship for Discourse. This is definitely something we could use to
> address the current sprawl of Jenkins communication channels. Many channels
> like User Mailing list, some SIG mailing lists and many Gitter channels
> could be replaced by discourse. So I am +1 for starting evaluation.
> > > >>>
> > > >>>
> > > >>> > 2) Configure the right level of Categories, as a first iteration
> I would like to focus on Jenkins users but we could extend it to Jenkins
> contributors as well.
> > > >>>
> > > >>> As Bruce said above, setting up a proper structure and moderation
> process is essential to the success of Discourse. Before we make it
> official, we should try it out and see how to better structure the
> communication channels. IMHO any interested contributor with Discourse
> expertise is welcome to participate in this effort. And thanks for stepping
> up Bruce!
> > > >>>
> > > >>> My notes:
> > > >>>
> > > >>> 

Re: [jenkins-infra] Elastic Sponsorship for OpenTelemetry usage for community Jenkins instances

[Oleg Nenashev]

Connecting ci.jenkins.io looks perfectly fine to me. There is no sensitive
data on this instance. For other Jenkins instances (infra, release,
trusted-ci, cert, ...) a sign-off from the Jenkins Security Officer is
required IMHO

On Fri, May 28, 2021, 10:40 Tim Jacomb  wrote:

> Sounds great
>
> On Fri, 28 May 2021 at 09:30, Damien Duportal 
> wrote:
>
>> [Cross posted on jenkins-dev and jenkins-infra]
>>
>> Hello dear community,
>>
>> During the last Jenkins infrastructure weekly meeting (2021-05-25 - Notes
>> -with recording link: https://hackmd.io/sBywc0IfRraU93aNETVwkw), Victor
>> Martinez and Iván Fernández from Elastic did a demonstration of the
>> opentelemetry plugin used with an Elastic APM platform.
>> The goal was to demonstrate how the build metrics could be used with
>> distributed tracing: please check the notes, video and
>> https://plugins.jenkins.io/opentelemetry/ for more details.
>>
>>
>> Victor and Ivan's employer, Elastic Inc. is proposing to sponsor the
>> Jenkins project by providing an APM instance that could be used along with
>> opentelemetry plugin, and a bit support to get it configured and maintained.
>> Their interest is to study what are our (Jenkins community) usages (and
>> obviously mentioning that we are using it).
>>
>> The proposal from the Infrastructure team is to provide this service for
>> the 2 following use cases:
>>
>>- For users of ci.jenkins.io (core and plugins contributors) to get
>>build metrics and traces of their projects. It could help a lot for
>>performances tracking, and much more as "Jenkins Pipeline level metrics"
>>- For infrastructure maintainers of ci.jenkins.io to track the agents
>>allocations and their errors, to improve the QoS of the build farm, as the
>>pure infrastructure metrics is not enough because issues come from
>>different areas (infra, Cloud providers, Jenkins configuration, Pipeline
>>usages, etc.)
>>
>>
>> It could be a great opportunity for whoever interested in better
>> understanding Jenkins behavior. As we'll try to identify typical use cases
>> that we want to better understand and then build dashboards using metric.
>> The challenge we face on the Jenkins infrastructure is that it's pretty
>> easy to know if Jenkins is running. But not so much if it's working in an
>> efficient way.
>>
>> The plan would be the following:
>>
>>- Start by a PoC on a private Jenkins instance  (e.g.
>>infra.ci.jenkins.io)
>>   - Install the plugin
>>   - Check APM instance access with Elastic
>>   - Configure the plugin to point to the APM
>>   - Bring back the conclusion to the community (by email here, blog
>>   post, meetup, whatever)
>>- Once the configuration is straightforward, deploying to
>>ci.jenkins.io, targeting as much publicly available dashboards and
>>data as possible, as service for the ci.jenkins.io users.
>>
>> What do you think about this topic, what would be your thoughts or red
>> flags?
>>
>> Cheers,
>>
>> For the Infra. team,
>> Damien DUPORTAL
>>
>> PS: by default, without any blocker or red flags, we (the infra.team)
>> will proceed with the infra.ci setup described in this email the 1st of
>> June.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Infrastructure" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkins-infra+unsubscr...@googlegroups.com.
>> To view this discussion on the web, visit
>> https://groups.google.com/d/msgid/jenkins-infra/0A4790E7-DF29-4C36-AAF3-320763D230B9%40gmail.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Infrastructure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkins-infra+unsubscr...@googlegroups.com.
> To view this discussion on the web, visit
> https://groups.google.com/d/msgid/jenkins-infra/CAH-3Bie3U4UOxmSLpex8sSw48FQeVGwJjXP4KLQTPWBAon%3DS1Q%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/CAPfivLBCAAJGP2p3oAudZztVQ2yT8sp5Zi9m%3DmMHC3REr%3DYNcA%40mail.gmail.com.

Re: [jenkins-infra] Elastic Sponsorship for OpenTelemetry usage for community Jenkins instances

[Tim Jacomb]

Sounds great

On Fri, 28 May 2021 at 09:30, Damien Duportal 
wrote:

> [Cross posted on jenkins-dev and jenkins-infra]
>
> Hello dear community,
>
> During the last Jenkins infrastructure weekly meeting (2021-05-25 - Notes
> -with recording link: https://hackmd.io/sBywc0IfRraU93aNETVwkw), Victor
> Martinez and Iván Fernández from Elastic did a demonstration of the
> opentelemetry plugin used with an Elastic APM platform.
> The goal was to demonstrate how the build metrics could be used with
> distributed tracing: please check the notes, video and
> https://plugins.jenkins.io/opentelemetry/ for more details.
>
>
> Victor and Ivan's employer, Elastic Inc. is proposing to sponsor the
> Jenkins project by providing an APM instance that could be used along with
> opentelemetry plugin, and a bit support to get it configured and maintained.
> Their interest is to study what are our (Jenkins community) usages (and
> obviously mentioning that we are using it).
>
> The proposal from the Infrastructure team is to provide this service for
> the 2 following use cases:
>
>- For users of ci.jenkins.io (core and plugins contributors) to get
>build metrics and traces of their projects. It could help a lot for
>performances tracking, and much more as "Jenkins Pipeline level metrics"
>- For infrastructure maintainers of ci.jenkins.io to track the agents
>allocations and their errors, to improve the QoS of the build farm, as the
>pure infrastructure metrics is not enough because issues come from
>different areas (infra, Cloud providers, Jenkins configuration, Pipeline
>usages, etc.)
>
>
> It could be a great opportunity for whoever interested in better
> understanding Jenkins behavior. As we'll try to identify typical use cases
> that we want to better understand and then build dashboards using metric.
> The challenge we face on the Jenkins infrastructure is that it's pretty
> easy to know if Jenkins is running. But not so much if it's working in an
> efficient way.
>
> The plan would be the following:
>
>- Start by a PoC on a private Jenkins instance  (e.g.
>infra.ci.jenkins.io)
>   - Install the plugin
>   - Check APM instance access with Elastic
>   - Configure the plugin to point to the APM
>   - Bring back the conclusion to the community (by email here, blog
>   post, meetup, whatever)
>- Once the configuration is straightforward, deploying to ci.jenkins.io,
>targeting as much publicly available dashboards and data as possible, as
>service for the ci.jenkins.io users.
>
> What do you think about this topic, what would be your thoughts or red
> flags?
>
> Cheers,
>
> For the Infra. team,
> Damien DUPORTAL
>
> PS: by default, without any blocker or red flags, we (the infra.team) will
> proceed with the infra.ci setup described in this email the 1st of June.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Infrastructure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkins-infra+unsubscr...@googlegroups.com.
> To view this discussion on the web, visit
> https://groups.google.com/d/msgid/jenkins-infra/0A4790E7-DF29-4C36-AAF3-320763D230B9%40gmail.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/CAH-3Bie3U4UOxmSLpex8sSw48FQeVGwJjXP4KLQTPWBAon%3DS1Q%40mail.gmail.com.

Elastic Sponsorship for OpenTelemetry usage for community Jenkins instances

[Damien Duportal]

[Cross posted on jenkins-dev and jenkins-infra]

Hello dear community,

During the last Jenkins infrastructure weekly meeting (2021-05-25 - Notes -with 
recording link: https://hackmd.io/sBywc0IfRraU93aNETVwkw 
), Victor Martinez and Iván Fernández 
from Elastic did a demonstration of the opentelemetry plugin used with an 
Elastic APM platform.
The goal was to demonstrate how the build metrics could be used with 
distributed tracing: please check the notes, video and 
https://plugins.jenkins.io/opentelemetry/ 
 for more details.


Victor and Ivan's employer, Elastic Inc. is proposing to sponsor the Jenkins 
project by providing an APM instance that could be used along with 
opentelemetry plugin, and a bit support to get it configured and maintained.
Their interest is to study what are our (Jenkins community) usages (and 
obviously mentioning that we are using it).

The proposal from the Infrastructure team is to provide this service for the 2 
following use cases:
For users of ci.jenkins.io (core and plugins contributors) to get build metrics 
and traces of their projects. It could help a lot for performances tracking, 
and much more as "Jenkins Pipeline level metrics"
For infrastructure maintainers of ci.jenkins.io to track the agents allocations 
and their errors, to improve the QoS of the build farm, as the pure 
infrastructure metrics is not enough because issues come from different areas 
(infra, Cloud providers, Jenkins configuration, Pipeline usages, etc.)

It could be a great opportunity for whoever interested in better understanding 
Jenkins behavior. As we'll try to identify typical use cases that we want to 
better understand and then build dashboards using metric.
The challenge we face on the Jenkins infrastructure is that it's pretty easy to 
know if Jenkins is running. But not so much if it's working in an efficient way.

The plan would be the following:
Start by a PoC on a private Jenkins instance  (e.g. infra.ci.jenkins.io)
Install the plugin
Check APM instance access with Elastic
Configure the plugin to point to the APM
Bring back the conclusion to the community (by email here, blog post, meetup, 
whatever)
Once the configuration is straightforward, deploying to ci.jenkins.io, 
targeting as much publicly available dashboards and data as possible, as 
service for the ci.jenkins.io users.
What do you think about this topic, what would be your thoughts or red flags?

Cheers,

For the Infra. team,
Damien DUPORTAL

PS: by default, without any blocker or red flags, we (the infra.team) will 
proceed with the infra.ci setup described in this email the 1st of June.

-- 
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/0A4790E7-DF29-4C36-AAF3-320763D230B9%40gmail.com.

Re: [jenkins-infra] Migrate chat channels from freenode to libera.chat

[Tim Jacomb]

Thanks all

Last call for any feedback before we merge the Jenkins.io PR

The channels have all been set up.

If you had 'voice' on freenode and want it on Libera then please verify
yourself with someone who has voice/op on libera out of band (email /
gitter / github, etc).
A number of people have left freenode and deleted their accounts already.




On Wed, 26 May 2021 at 20:14, Tim Jacomb  wrote:

> The ircbot has been moved over
>
> On Wed, 26 May 2021 at 19:12, 'Gavin Mogan' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com> wrote:
>
>> Project registration has been completed since Saturday I think.
>>
>> I've removed the channel locks so anyone can create can register
>> channels, project owners can claim the channel if it ever becomes an issue.
>>
>> Cloaks can be requested by any group member.
>>
>> Jenkins group members:
>> Primary (can claim. Can manage group member lists)
>> halkeye (me)
>> Olblak
>>
>> Secondary (primary plus requesting cloaks for users)
>> Nobody yet
>>
>>
>> Cloaks:
>> We have jenkins/* reserved
>> I'm thinking jenkins/contributor/$nick for most people, then maybe board
>> specific if we care.
>>
>> On Wed., May 26, 2021, 8:01 a.m. Oleg Nenashev, 
>> wrote:
>>
>>> FYI see the project registration instructions here:
 https://libera.chat/chanreg#project-registration

>>> AFAICT from the Governance Board discussion, Gavin and Olivier have
>>> already submitted a registration request.
>>> It just takes time to process
>>>
>>>
>>>
>>> On Wed, May 26, 2021 at 4:57 PM Basil Crow  wrote:
>>>
 +1. I opened a PR to cover updating the references on jenkins.io:
 https://github.com/jenkins-infra/jenkins.io/pull/4384

 FYI see the project registration instructions here:
 https://libera.chat/chanreg#project-registration

 --
 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/pEcun5ZSfgo/unsubscribe
 .
 To unsubscribe from this group and all its topics, 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/CAFwNDjqK%2BDwkLWdBUDh1iku45C9JjxC5NLXwguXAb3c%3Djx1i7g%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/CAPfivLDg7kSiyUHk6a4VgVHurG-8AcKfZHsSpCv0RG3_bpyFDg%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/CAG%3D_Duu4zWLgXUKN-PC20hdNCD_ct5kPufF9jj9Wh9d9GfbrmQ%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/CAH-3BicOYrO7S2yVQci3ZiN1fkqjV4ktOatmwFbU4O52S_PHFw%40mail.gmail.com.