I guess you are using git as your version control system and your question is specific to the way the Jenkins git plugin works. It really would make answering these questions a bit easier if people would tell a little bit what kind of setup they have...
If the git plugin has been configured to follow all branches, it wants to build every branch at least once. After it has done that, it will only build the branches that get new commits. If you have a lot of branches which have not been built, remove all branches you do not need anymore. You can also cancel the builds of branches you don't need. Jenkins git plugin consider a branch built when it has started building a branch. It does not matter if you cancel the build in mid-flight. -- Sami Ahmed Mubbashir Khan <mubbashi...@gmail.com> kirjoitti 28.1.2013 kello 10.36: > Hi All, > > Which branch is build if there are multiple branches in a job and job has > been configured for all jobs? > What is the workflow? How jenkins determine what to build? > > Similarly: > If a job was initially configured for master, and then we switch it to > monitor all branches. It seems like its building branches which doesn't have > any commits lately. > The output is something like: > Checking out Revision b6f8f39... (origin/sprint1) > No change to record in branch origin/sprint1 > [workspace] $ /bin/sh -xe /home... --> Still > executing. > > Any thoughts? > > -- > Regards, > Mubbashir -- 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. For more options, visit https://groups.google.com/groups/opt_out.
