On Fri, May 10, 2013 at 10:44 AM, Benjamin Lau <[email protected]>wrote:
> I also use git commands directly. If you make it so your build is > identical for all of your repositories you could have a single > parameterized job which has parameters for the repo and branch (unless > everything is always in master). > I was thinking of going down this route. Can you elaborate on how you set it up? Are you using git post-commit hooks to trigger the Jenkins project with the name of the repo & branch that got committed? The builds are all basically identical so being able to parameterize a single project seems like the correct approach. -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
