> > > I don't think that is how the Git plugin does what it does. > > I believe the Git plugin monitors multiple repositories and branch names > for changes. If a change is detected in one or more repositories, the > plugin merges those changes into its local branch, and attempts to run the > job steps you specify (compile, test, deploy, whatever). The Git plugin > has an optional step at the end, "Git Publisher" which will push the > results of that merge to the remote specified in the plugin. > > We did this (which is why the git plugin supported it).
We had git pulling from all developer local repositories, and speculatively compiling them & running tests. It would then be able to say 'hey, your commit xxxxx - it doesn't actually compile'. This was used *as well as* gerrit, just to give each developer extra information about the state of their branches. -- 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.
