> My point being we ware shipping a core with > this flaw for years (correct me if I wrong)
Correct there ware no documentation > plugins should not save before EXTENSIONS_AUGMENTED is completed and > people ware not bitten severely enough to file an issue until recently > (again, correct me if I a wrong). I think people have been bitten by this for a long time it was just not obvious and there are only a few plugins that manipulate state like this. The setup I use at work has been bitten by this for about a year - partly because one of our plugins was badly behaving, we have had some reports going back that some configuration was lost but was a one off for the customer so no extra deep diving occurred at the time. There are issues reported in Config-As-Code before core prevented the dataloss exactly about dataloss, so I think people have been seeing this in CasC but there was never a correlation (and as Casc adoption is growing explains why we see this a little more). https://github.com/jenkinsci/configuration-as-code-plugin/issues/280 (reported > 1 year ago but theoretical ) https://github.com/jenkinsci/configuration-as-code-plugin/issues/1171 https://github.com/jenkinsci/configuration-as-code-plugin/issues/1026 Are we ok to see how the JCasC PR is doing before committing to an LTS > baseline? >From my point of view certainly. -- 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/289dd519-217f-4071-82d1-d02a7e529cdc%40googlegroups.com.
