I must be missing something obvious here, but how can I get my build to be triggered whenever a new revision is committed to my source repository. In the older style Jenkins jobs, this was something I configured in the webform, I don’t see this in the multi-branch pipeline itself. I assumed this was automatic.
I have a Subversion repository setup this way: http://svn.vegicorp.net/vc/commons/<project>/trunk/... http://svn.vegicorp.net/vc/commons/<project>/branches/… I have a multi-branch pipeline watching over http://svn.vegicorp.net/vc/commons and includes branches “*/trunk” and “*/branches/*”. When I index the branches, all of my projects and branches show up. However, none of them build unless I do a reindex of the branches. I don’t see anything in the multi-branch pipeline to build on a commit. I see in each project a way to configure to build on commit in their configuration screen, but there’s no “Save” button to save such a configuration. Is there a problem with my setup? Do I need to use Git rather than Subversion? Do I need to do each project under our commons separately? I love the idea of not having to setup new Jenkins jobs whenever a new branch of a project is created, but it’s not “Continuous Integration” unless you build automatically after each commit. -- David Weintraub qazw...@gmail.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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/44C4D64F-4350-468F-B482-C3A776707BF5%40gmail.com. For more options, visit https://groups.google.com/d/optout.
