Re: Proposal: Evaluating Twitter as code with @memkins

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

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

+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

Re: Stapler IntelliJ Plugin JetBrains Marketplace listing

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

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

+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

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

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

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

"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

Re: Discourse as the default communication channel?

> > 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.

Re: Discourse as the default communication channel?

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 > >

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

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

Re: Discourse as the default communication channel?

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

Re: Discourse as the default communication channel?

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

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

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

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

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 >

Elastic Sponsorship for OpenTelemetry usage for community Jenkins instances

[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

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

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