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

> The credentials domain syntax, IIRC something like system: ? # global : -credentials # … baffles everyone who sees it. Just because internally `credentials` uses a `Map` from (I guess) domains to lists of credentials does not mean you must reflect that in YAML syntax. You should rather

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

2018-05-08 21:08 GMT+02:00 Liam Newman : > > Just FYI: Nicolas asked a question of me in a GH comment: > https://github.com/jenkinsci/jep/commit/78bede6c731e7a85a90ca374ca1c39 > 4e219aa961#commitcomment-28894501 > > @bitwiseman Discussion on

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

Just FYI: Nicolas asked a question of me in a GH comment: https://github.com/jenkinsci/jep/commit/78bede6c731e7a85a90ca374ca1c394e219aa961#commitcomment-28894501 @bitwiseman Discussion on plugin management > was probably introduced in this JEP too early as we

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

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

On Wed, May 2, 2018 at 3:58 PM, Ewelina Wilkosz wrote: > Any of you interested in contributing to that one? Please let me know, so we > don't duplicate I will leave the reasoning to you! Just bringing up things that seemed to merit discussion. -- You received this message

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

Jesse, Nicolas, I'd like to follow Liam's suggestion about updating JEP-201's Reasoning section Any of you interested in contributing to that one? Please let me know, so we don't duplicate :) I hope to have something around Friday On Friday, April 20, 2018 at 8:26:45 PM UTC+2, Liam Newman

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

(offlist) I want to be clear: I was not singling you out or criticizing. This looks like a challenging thread, and you're doing a great job staying positive and open to ideas. If there's anything I can do to help just say so. Thanks for all your hard work, Liam Newman On Sun, Apr 22, 2018 at

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

Thanks for keeping your eye on it Liam, I will take necessary actions this week! On Friday, April 20, 2018 at 8:26:45 PM UTC+2, Liam Newman wrote: > > Ewelina, Nicolas, > > I'm jumping in because I don't see anyone mentioning who will be doing > this. > > As JEP-1 sponsor, I would like to

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

Ewelina, Nicolas, I'm jumping in because I don't see anyone mentioning who will be doing this. As JEP-1 sponsor, I would like to remind you that part of your duties as sponsors of JEP-201 include different viewpoints and design suggestions in your JEP. (I'm jumping in because I don't see

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: [JEP-201] [configuration-as-code] Feedback from Meetup

2018-04-18 0:42 GMT+02:00 Jesse Glick : > On Tue, Apr 17, 2018 at 4:45 PM, nicolas de loof > wrote: > > Job class hierarchy is full of hand written JSON parsing > > I suspect such cases are fixable, which would take some work, but on > the other

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

On Tue, Apr 17, 2018 at 4:45 PM, nicolas de loof wrote: > Job class hierarchy is full of hand written JSON parsing I suspect such cases are fixable, which would take some work, but on the other hand we would get a clearer code base as a result anyway. -- You received

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

2018-04-17 22:05 GMT+02:00 Jesse Glick : > On Tue, Apr 17, 2018 at 2:03 PM, nicolas de loof > wrote: > > the yaml schema is for a specific version of jenkins-core + plugin. > > Any change to a plugin will change this model, this will happen any

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

On Tue, Apr 17, 2018 at 2:03 PM, nicolas de loof wrote: > the yaml schema is for a specific version of jenkins-core + plugin. > Any change to a plugin will change this model, this will happen any time a > DataBoundConstructor is modified Well, typically we would expect

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

2018-04-17 17:58 GMT+02:00 Jesse Glick : > Some things that might otherwise have gotten lost in IRC. > > > About the automatic inference of symbols like `ldap` from > `hudson.security.LDAPSecurityRealm`: this seems like a nice trick to > use when prototyping the JEP, so you