You may also want to look into the Jenkins job dsl plugin (
https://github.com/jenkinsci/job-dsl-plugin/) for providing an easier way
to create and manage jobs in Jenkins.

I haven't used Jenkins in a large Git environment, but perhaps those who
have problems with the performance could file bugs related to their
experiences in specific situations if they haven't already?  It would
benefit the community to have a bullet-proof Git plugin that performed well
at scale.

Thanks,
Chris

topher1...@gmail.com


On Fri, May 10, 2013 at 12:41 PM, Benjamin Lau <benjamin.a....@gmail.com>wrote:

> I'm not using post commit hooks... But those would probably work well for
> your situation. For us we don't build on every commit currently. But if you
> take a look at the remote api you can probably make it work that way pretty
> easily.
>
> You can use cURL to trigger it here's one of our urls to trigger a build
> with parameters:
>
>
> http://buildserver:8080/job/buildServer/buildWithParameters?delay=0sec&server_git_branch=featureBranch
>
> Ben
> On May 10, 2013 2:10 PM, "Jon Drukman" <jdruk...@gmail.com> wrote:
>
>> On Fri, May 10, 2013 at 10:44 AM, Benjamin Lau 
>> <benjamin.a....@gmail.com>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 jenkinsci-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>  --
> 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.
>
>
>

-- 
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.


Reply via email to