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 was my motivation for keeping job dsl. Alternative solution may exist next to job dsl support I believe
On Wednesday, April 18, 2018 at 6:53:58 AM UTC+2, nicolas de loof wrote: > > > > 2018-04-18 0:42 GMT+02:00 Jesse Glick <[email protected] <javascript:>> > : > >> On Tue, Apr 17, 2018 at 4:45 PM, nicolas de loof >> <[email protected] <javascript:>> 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. >> > > Sure, but this will be for future version then > We want JCasC to support current releases of Jenkins by Praqma customers > (and others), not require bleeding edge Jenkins core. > > >> >> -- >> 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 [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr03rVj6r1tWfwYeO1QKeDMtDYjuc8fF0Se%2B4Rh9qbZFvg%40mail.gmail.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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/0950046f-3477-4ef9-88eb-74908f01e313%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
