yes indeed. But I also would like this specific seed-job support to move to job-dsl plugin, so the way this configuration element is used is directly managed by job-dsl plugin version
2018-05-13 1:36 GMT+02:00 Daniel Beck <[email protected]>: > > > On 11. May 2018, at 17:14, nicolas de loof <[email protected]> > wrote: > > > > I don't get your point > > > > the physical layout of the yaml file is directly built based on > component discovery > > YAML attributes are mapped to `Describable`s and other components based > on how we can access them from root "jenkins" object (and other root > elements). This mapping is not defined by CasC but by discovery from live > jenkins instance model. > > > > i.e we discover "jenkins" has a "securityRealm" attribute and some > implementation can be used to set this attribute. This directly defines the > yaml tree. But the codebase has no reference to this structure. > > Some stuff is still defined by CasC, otherwise > https://github.com/jenkinsci/configuration-as-code-plugin/pull/62 > wouldn't exist. > > -- > 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/38388CD1-DF9E-4DB9-B22E-B4A0F47ACC8D%40beckweb.net. > 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/CANMVJz%3D6kGMkft8KUUp9d9t2zL%3DbArQkfFJgdSz25-d0VWfODw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
