I am looking into using Jenkins as a tool for continuous deployment. A
commit to a git repository triggers building of rpms, updating a yum repo,
possibly triggering production machines to do a yum update, etc. I've set
up a test project, and Jenkins seems like it provides a lot of useful
On Friday, May 10, 2013 1:23:41 PM UTC-4, Jon Drukman wrote:
I am looking into using Jenkins as a tool for continuous deployment. A
commit to a git repository triggers building of rpms, updating a yum repo,
possibly triggering production machines to do a yum update, etc. I've set
up a
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).
To make this easier to work with I also wrote some shell scripts
On Fri, May 10, 2013 at 10:44 AM, Benjamin Lau benjamin.a@gmail.comwrote:
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
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
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
On Fri, May 10, 2013 at 12:38 PM, JonathanRRogers
jonathanrrog...@gmail.com wrote:
Jenkins' git plugin performs poorly with hundreds of branches in a single
repository. I haven't tried it with hundreds of repositories, but I wouldn't
be surprised if that also performed poorly. I now avoid the
Look into the github trigger where pushes to a repo causes the webhook to hit
the url for the job and it will check for changes and build. Thus no polling
is involved.
http://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/
I'd like to suggest the Jenkins Job
William Soula wrote:
Look into the github trigger where pushes to a repo causes the webhook to hit
the url for the job and it will check for changes and build. Thus no polling
is involved.
http://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/
Chris Marks wrote:
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
10 matches
Mail list logo
