]> git-server-git.apps.pok.os.sepia.ceph.com Git - ceph-build.git/commit
jenkins: use in-tree clone for the ceph-build repo 3/head
authorKen Dreyer <ken.dreyer@inktank.com>
Tue, 14 Jan 2014 17:18:39 +0000 (10:18 -0700)
committerKen Dreyer <ken.dreyer@inktank.com>
Thu, 16 Jan 2014 04:29:55 +0000 (21:29 -0700)
commitd74d5ad1fcbaa76e324048f0b61fcf2f6f95f656
tree160498bbe9254df844642c79dfbb34a19a3a297f
parentcfb8ba3513532789c850850aa32c48cfc2b57323
jenkins: use in-tree clone for the ceph-build repo

Historically we have had a single system-wide clone of the ceph-build
repository on each builder, at /srv/ceph-build.

The disadvantage to this configuration is that there is no way to ensure
that each of these clones are up to date. When we make changes to the
ceph-build repository on GitHub, we have to manually pull the changes
into each builder's local clone at /srv.

Going forward, we will use the Multi-SCM plugin to Jenkins to make the
ceph-setup Jenkins job use an up-to-date clone of the ceph-build
repository. This will ensure that Jenkins is using the very latest code
from ceph-build.

The ceph-build repository will be cloned into the root of the tree.
Remove the references to /srv/ceph-build and just use the relative path,
"ceph-build".
jenkins/build
jenkins/setup