Re: Jenkins Governance Meeting, Sep 8, 2021

meetings on either side >>> of it. >>> >>> On Wed, Sep 22, 2021 at 8:19 AM Ewelina Wilkosz >>> wrote: >>> >>>> I can have this meeting few hours earlier or an hour later >>>> we're changing time in a few weeks? I c

Re: Jenkins Governance Meeting, Sep 8, 2021

I can have this meeting few hours earlier or an hour later we're changing time in a few weeks? I can't remember which direction... we should consider that too though but the bottom line is that I can make it work any time Wednesday afternoon till late evening On Wednesday, September 22, 2021

Re: Welcome Ewelina Wilkosz - new Jenkins Governance Board Member

have finished the interim board member >> selection procedure. The Mar 10 Governance meeting has confirmed Ewelina >> Wilkosz as a new Jenkins Governance Board member who will replace Marky >> Jackson in this role. The term will last until the Jenkins elections in >> late 2022

Please reassing plugins to Eficode

Hi! Praqma is now a part of Eficode and we want to make sure all the plugins that are being maintained by my colleagues from both companies are getting the attention when the new issue comes. For that reason I have created a new jenkins.io user - *eficode* - and I'd like to ask for help

Re: Adopt Post Build Task Plugin

Hi, thanks for pinging me directly Oleg, it is perfectly ok for Tim to take over, thanks! (I checked with Mads) On Sunday, November 15, 2020 at 11:29:23 PM UTC+1 Oleg Nenashev wrote: > Hello, > > Sorry, I completely missed this thread. Not sure this maintainer's email > is still active. > I

Re: Need help with accessing Praqma Support user

yes, thanks a lot - I'll now consult with old Praqma people and our newer colleagues from Eficode to figure out how to best handle our plugins from now on but I got the help I needed for now! On Thu, 12 Nov 2020 at 10:07, Oleg Nenashev wrote: > FTR I have sent a new temporary password to

Re: Need help with accessing Praqma Support user

I couldn't reach anyone with the access before I asked for help here obviously I tried... I decided to take the matter into my own hands and was offered help straight away - the opposite to the person with access, who's not very responsive On Thu, 12 Nov 2020 at 09:58, Daniel Beck wrote: > > >

Re: Need help with accessing Praqma Support user

I was informed later today that you did :) thanks But that mail account is being used for different support cases and I want to make it more convenient for the future - so it’s easier for everyone I had order new mail account for Jenkins only and I hope to get it soon On Wed, 11 Nov 2020 at

Re: Need help with accessing Praqma Support user

Thanks! I’ll check with my IT department how fast they can create one for me and get back to you. On Wed, 11 Nov 2020 at 21:46, Oleg Nenashev wrote: > I confirm that a few years ago Ewelina was designated by Praqma to be a > liaison in the Jenkins community. > The Praqma Support account has

Need help with accessing Praqma Support user

As a representative of Praqma Eficode I need to get an access to Praqma Support account (supp...@praqma.net) so I can handle issues on https://issues.jenkins-ci.org Currently I can't access supp...@praqma.net and I will update it with new email - if possible - once I get the access Can

Re: Notification when new image pushed to docker hub

gt; email notification from a Jenkins job. Maybe not the most glorious way but >> it solves the immediate need. >> Have a good rest of the week  >> >> On Jun 4, 2020, at 1:15 AM, Ewelina Wilkosz wrote: >> >>  >> wow, thanks a lot!! >> >> On

Re: Notification when new image pushed to docker hub

wow, thanks a lot!! On Thursday, June 4, 2020 at 10:08:12 AM UTC+2, Marky Jackson wrote: > > I have always had super good luck writing a go script job and > incorporating https://github.com/crazy-max/diun > > > > On Jun 4, 2020, at 1:04 AM, Ewelina Wilkosz > wrote:

Re: Notification when new image pushed to docker hub

Would this be for a production type instances of Jenkins or a personal > instance? > > > On Jun 4, 2020, at 12:55 AM, Ewelina Wilkosz > wrote: > >  > Hi! > > I am trying to automate updating jenkins when new lts image is released > do you know: > 1. if there is some notifi

Notification when new image pushed to docker hub

Hi! I am trying to automate updating jenkins when new lts image is released do you know: 1. if there is some notification mechanism in place? something I can "watch" and learn that new version is out? 2. I do not want to really go for "jenkins/jenkins:lts", I want to match lts to specific

Re: JCasC & Plugins updates result in infinite restart loop

:26 PM UTC+1, Ewelina Wilkosz wrote: > > (Logs in the attachment) > > I had a Jenkins mastered configured with Jenkins Configuration as Code > plugin. > > Jenkins version: 2.138.? > JCasC version: 1.3 > and number of plugins requiring upgrade > > I've updated JC

Day of Jenkins [as code]

In October 2018 Praqma is bringing Day of Jenkins back, this time [as code]! https://www.code-conf.com/2018/day-of-jenkins-as-code/ Praqma, Cloudbees and a number of external contributors are currently developing the JCasC plugin and believe it will become THE configuration as code solution

Re: [JEP-201] [configuration-as-code] Feedback from Meetup

just a short update - JEP update in progress, next week we're planning a short maintainers status meeting where I hope to clarify stuff and PR will be sent On Thursday, May 3, 2018 at 12:24:07 AM UTC+2, Jesse Glick wrote: > > On Wed, May 2, 2018 at 3:58 PM, Ewelina Wilkosz <ewel...@

Re: [JEP-201] [configuration-as-code] Feedback from Meetup

ope for the current release. > > You may ask Jesse if he'd be willing to submit PRs (adding to > "Specification" or "Reasoning"), but ultimately it is your responsibility > to make sure it happens. > > Thanks, > -L. > > > > On Tuesday, April 17,

Re: Jenkinsfile-runner + Configuration-as-Code

I am pretty sure you'll make many people happy with it - are you planning to write/is there already a JEP for that? since you've mentioned JCasC couple of times I believe it would make sense to how exactly those two could work together (I'm assuming you have some ideas in mind, but we can try

Re: [JEP-201] [configuration-as-code] Feedback from Meetup

), but ultimately it is your responsibility > to make sure it happens. > > Thanks, > -L. > > > > On Tuesday, April 17, 2018 at 11:31:30 PM UTC-7, Ewelina Wilkosz wrote: >> >> interesting discussion! >> >> I agree we can have a nicer way of configuring

Re: [JEP-201] [configuration-as-code] Feedback from Meetup

interesting discussion! I agree we can have a nicer way of configuring job, to keep the consistency, but I also agree with Nicolas about not wanting to "re-invent the wheel" - many users have their job dsls ready, so the transition may be easier if they don't need to learn a new syntax, that

Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

I must say I only briefly scanned the part with all the jenkinsci-foo and sig-foo :( it seemed like a lot indeed. I like the rest of the document though! but this part was almost verwhelming... that's why I asked about SIG Lead responsibility. If we want to do a good job we should make it as

Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

Good job! I'll just comment what I think could be clarified, really small things... - "Record SIG meeting, such as via YouTube Live Streaming, and make it publicly available. Text-based meetings can use #jenkins-meeting on Freenode.." - So is it obligatory to record a meeting or not? should we

Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

+1 to that Baptiste, let's try to make it in a way that 1. will not isolate us, but "keep us together" 2. will make it easy for us to keep the track and easy to say without providing ideas, but for now I just wanted to highlight I believe those two are important things to keep in mind while

Re: JEP: Modification of "Accepted" JEPs

Thanks a lot for this extended answer Liam! As I said I do not have any strong feelings/objections but I'm glad we have this discussion that hopefully will make things more clear :) On Friday, March 23, 2018 at 12:47:52 AM UTC+1, Liam Newman wrote: > > We recently had a pull request with a

Re: JEP: Modification of "Accepted" JEPs

I'm perfectly ok with starting a discussion about proposed change And in general I do not disagree with your proposal but I want to share my doubts... when we started working on Jenkins Configuration as Code we had an idea and then the idea has changed and I'm glad we put it all in one

Re: alpha version of Jenkins Configuration as Code plugin available

no need to create anything on github now, we'll continue here in the thread you created On Wednesday, February 28, 2018 at 6:01:32 AM UTC+1, Harsh Bajaj wrote: > > Just a clarification do i create a thread on github then? > > On Tuesday, February 27, 2018 at 12:32:12 PM UTC-6, Ewe

Re: alpha version of Jenkins Configuration as Code plugin available

s of open source.I am proficient > with programming and working on Docker.Please if you can guide me how to > get started on this > > On Monday, February 26, 2018 at 10:00:00 AM UTC-6, Ewelina Wilkosz wrote: >> >> Last Friday we've released 0.1-alpha of Jenkins Configuratio

alpha version of Jenkins Configuration as Code plugin available

Last Friday we've released 0.1-alpha of Jenkins Configuration as Code plugin. Use carefully, number of key features still missing but we're getting there! -- You received this message because you are subscribed to the Google Groups

Re: Draft JEP: Configuration as Code

Nice! good luck Eric, and if you need some clarification I can try to explain via mail or short online meeting When is the meetup? On Wednesday, February 14, 2018 at 9:54:04 PM UTC+1, Eric Smalling wrote: > > Sounds like I may need to be the first to try then! :) > > On Wed, Feb 14, 2018 at

Re: [GSoC 2018] - Preliminary announcement

Count me in, for Jenkins Configuration as Code On Saturday, December 16, 2017 at 5:50:19 PM UTC+1, martinda wrote: > > I would like to renew this experience. You can count me in as a mentor. > > Where should we propose and discuss project ideas? I suggest a page on the > Wiki like GSoC 2016

Re: Selecting Delegates for the first wave of JEPs

I won't object :) On Tuesday, December 5, 2017 at 9:01:08 AM UTC+1, Kohsuke Kawaguchi wrote: > > Time to select Delegate > for > the first wave of JEPs! > > JEP-200 is in

Re: [configuration-as-code] Descriptors configuration

need to investigate a better way to check a Descriptor has a > global.jelly view (I'm so pleased to dig into Stapler internals :P) > > > > 2017-11-24 13:34 GMT+01:00 Ewelina Wilkosz <ewel...@gmail.com > >: > >> It looks the list is not empty, it's URL global = Co

Re: [configuration-as-code] Descriptors configuration

, for a reason I don't understand yet, > "Jenkins.getInstance().getExtensionList(Descriptor.class)" returns an empty > list :-\ > investigating ... > > 2017-11-24 9:51 GMT+01:00 Ewelina Wilkosz <ewel...@gmail.com > >: > >> Hi Nicolas, I have a problem with

Re: [configuration-as-code] Descriptors configuration

Hi Nicolas, I have a problem with configuring mailer - if I use "mailer:" as root element Jenkins won't start - exact copy from demo folder - if I put mailer under "jenkins:" root element there is no error on startup but no configuration is applied Is there anything special about that one, that

Re: stack trace in configure system (docker, plugin development)

wow, I forgot 'checkout scm' step :D it was using the old workspace from previous version of Jenkinsfile, that was the source of conflict I guess thanks guys for pointing me the workspace as the source of problem, solved! On Friday, November 10, 2017 at 8:32:52 PM UTC+1, Ewelina Wilkosz wrote

Re: stack trace in configure system (docker, plugin development)

ok, when I build locally I do not get stack trace, something is messed up in my Jenkins job or agent :) On Friday, November 10, 2017 at 8:06:43 PM UTC+1, Ewelina Wilkosz wrote: > > right, it does look like a git merge, the thing is, I can't see any > conflicts in my repo > so

Re: stack trace in configure system (docker, plugin development)

d "git merge". No idea of the source of that > failed merge, but those markers are used by git when it can't resolve a > merge of a historical file into the current file. > > Mark Waite > > On Fri, Nov 10, 2017 at 10:14 AM Ewelina Wilkosz <ewel...@gmail.com >

stack trace in configure system (docker, plugin development)

I'm working on dockerizing Configuration as Code plugin, which means I create a docker image, based on jenkins:2.60.3, I build the plugin and I install it in a Dockerfile: https://github.com/jenkinsci/configuration-as-code-plugin/blob/praqma/dev/Dockerfile It seems to be working, but I get