I just released 0.5, which fixes the job configuration history craziness. As for the "except they can't be configured directly" bit... this was true at one point (version 0.1) but since then the interworkings of the multi-branch-project-plugin have changed to use a hidden template. By doing that, many headaches were solved, but with the trade-off that the sub-projects became directly configurable. Any direct configuration will be overwritten by the sync/indexing. I updated the wiki page to clear that up a bit. I think the only way to prevent direct configuration involves using project-based matrix authorization as your security strategy.
On Mon, Jun 27, 2016 at 2:56 AM, Jochen Fuerbacher < [email protected]> wrote: > It's not possible to reconfigure scm. But it's still possible to do some > config changes like adding build steps or post build actions. > > Am Dienstag, 21. Juni 2016 12:49:40 UTC+2 schrieb Arnaud Héritier: >> >> As far as I can see you can only "View Configuration" which displays the >> configuration form but doesn't allow you to save it (yes I find it a little >> bit ugly too) >> >> >> On Mon, Jun 20, 2016 at 1:52 PM, Jochen Fuerbacher < >> [email protected]> wrote: >> >>> Hello there, >>> >>> i was wondering about the behavior of the Multi-Branch Project Plugin. >>> The wiki page says "Each branch has its own sub-project. Sub-projects >>> are just like normal projects, except they can't be configured directly and >>> they are listed on the main (parent) project's page." >>> >>> However, when I click on such a branch / sub-project, I CAN confgure >>> them directly. Is that wanted? >>> If not, is it still possible, that the sub-project configuration can >>> change? >>> >>> One problem of this behavior is, that the sync of the branches leads to >>> changes in the sub-project config files (temporarily disable and re-enable >>> of the job), which get tracked by JobConfigHistory (if installed). See: >>> https://issues.jenkins-ci.org/browse/JENKINS-33682 >>> >>> Jochen Fürbacher >>> >>> >>> >>> -- >>> 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/234ad651-18f7-43bc-85b6-aa381e6dd5ff%40googlegroups.com >>> <https://groups.google.com/d/msgid/jenkinsci-dev/234ad651-18f7-43bc-85b6-aa381e6dd5ff%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> ----- >> Arnaud Héritier >> http://aheritier.net >> Mail/GTalk: aheritier AT gmail DOT com >> Twitter/Skype : aheritier >> > -- 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/CAH2jAL3ddmujQMBncz3E07%2Bhz-6Ji_Bq-se58LqvdwWGUaRXtQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
