George V. Reilly

Jenkins #3: GitHub Integration

[Pre­vi­ous­ly published at the now defunct MetaBrite Dev Blog.]

Much of our code is in one large GitHub repository, from which several different ap­pli­ca­tions are built. When changes are pushed to the master branch, we want only the ap­pli­ca­tions in affected di­rec­to­ries to be built. This was not easy to get right with “Pipeline script from SCM” builds.

#3 in a series on Jenkins Pipelines


Pipeline (Jenk­ins­file)

blog comments powered by Disqus
Trump: Media Suppresses Coverage of Terrorist Attacks » « Jenkins #4: The sh Step