On 08.03.2016, at 23:31, memoe <[email protected]> wrote: > Very strange behavior.
Jenkins generally only modifies configuration files when requested to do so (i.e. someone clicks 'Save'). There's no roundtrip when POSTing a config.xml, it simply gets loaded. It's often the case (e.g. when adding new features) that a default behavior is determined programmatically when loading a configuration file without any related data. Only when saving to disk, this is made explicit (and e.g. the option's value written to the config file). Your empty project config is an extreme case of this. Note that you'll probably run into JENKINS-21017 when pursuing this further. -- 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/AD189505-9F33-4CB4-B11F-B43A572E90FC%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
