Worth mentioning that the MB "build" is not a build of the code, but indexing of the repo for branch status. So if you schedule it to build every 5 minutes, it will re-index the repo every 5 minutes - but only build the branches that have changes in them and only when there is a change (or however you configure it)
-M On Wednesday, August 31, 2016 at 11:09:55 AM UTC-5, Spamme wrote: > > Hello, I was testing the multibranch job in jenkins (1.642.4) because I > wanted to trigger a (visual studio) build after each commit in a branch, > because it happens very often that our developers commit broken code. > I had configured the multibranch project with the jenkinsfile and it > builds, > after I wanted to trigger the build with a web hook from visualsvn (I hope > to switch soon to github), but I discovered later that this feature is > broken (https://issues.jenkins-ci.org/browse/JENKINS-33020). The other > two > available options are: "Build Periodically", what is a bad idea and > "Periodically if not otherwise run", which doesn't seem to better than the > former. There also no SCM poll option. Therefore I'm quite puzzled, how > should be used this multibranch job? How it can be configured to build a > branch as soon as something is committed to the SCM? Because the only > trigger that could do it is broken since months, therefore there should be > another way to achieve it, or not? > > > > -- > View this message in context: > http://jenkins-ci.361315.n4.nabble.com/Multibranch-triggers-configuration-tp4838717.html > > Sent from the Jenkins users mailing list archive at Nabble.com. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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-users/ac366e66-255e-4531-8c61-22b785ab25a4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
