To get more into details : docker-compose has it's own data model and translates into docker API calls. Doing so it can support model versions for config file, as well as adapt when required to underlying docker API Changes
configuration-as-code has been designed as a "no glue code" model : we don't write a single line of code for configuration attribute of plugin X to be supported, everything is based on runtime discovery by reflexion. This design allows to support (mostly) all plugins out-of-the-box, but the price to pay is that there's no "model" but the one discovered at runtime : if you upgrade a plugin which refactored it's databound "API" then the configuraiton schema will change as well. In some "as-code" process we expect such upgrade would be tested before being pushed to production master, so that model changes would be detected before. CasC do already report unknown attributes and fail fast. But afaik there's nothing much we can offer here. 2018-05-11 9:29 GMT+02:00 nicolas de loof <[email protected]>: > not so simple : > > configuration-as-code schema depends on jenkins-core version and all > plugins version being installed. So generating a "version" would be hard. > Credentials syntax used in alpha is here for demonstration purpose, with > minimal lines of code to provide this feature, I expect we remove this code > from CasC as we release 1.0 so it can be implemented by credentials plugin > its own way. > > 2018-05-10 22:30 GMT+02:00 Jesse Glick <[email protected]>: > >> I had the same comment about Declarative Pipeline before it went >> 1.0—that every script should start with >> >> pipeline(1) { >> >> But to no avail. :-( >> >> -- >> 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/ms >> gid/jenkinsci-dev/CANfRfr1ARV%2Br1u98umpjCZBvd2%3Dh7msQ1TQFT >> UvbhpoGPc%3Dz6g%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/CANMVJz%3DOUswr3u4U07zQeFQn6fTJXPUn9A17fdGyV4dE4whQTg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
