Hi all, You've probably heard that we've been working on replacing the gitbuilders with a new build system. I recently did some work [0] in teuthology to support that new system, and that work got merged yesterday. Here's an overview of its current state: The way it works is that it talks to Shaman [1] to locate the package repository to use. It is not enabled by default as it isn't yet able to cover all gitbuilder use cases. It can be enabled by setting "use_shaman: true" in either your teuthology.yaml or your job's yaml. It can be set for an entire suite-run by doing something like: $ echo "use_shaman: true" > ./shaman.yaml $ teuthology-suite -v -c jewel -s upgrade/jewel-x -m vps -k distro $PWD/shaman.yaml --dry-run Of course, later on when we can fully replace gitbuilders this behavior will be the default. At some point after that we'll be decommissioning the gitbuilders. Please note that using it in the following scenarios will *not* do what you want: * Any job that requires one of our testing kernels, as the new system isn't building our kernels yet * Any job that uses the install task for samba, for the same reason * Any job that uses ceph-deploy, as ceph-deploy isn't using the new system yet Please try to give this new system some exercise. It's been tested well but of course we can't necessarily anticipate everything. Teuthology bugs, as always, should go here [2] and bugs related to the new build system should go here [3]. Thanks for reading! Zack [0] https://github.com/ceph/teuthology/pull/951 [1] https://github.com/ceph/shaman/ [2] http://tracker.ceph.com/projects/teuthology/issues/new [3] http://tracker.ceph.com/projects/ci/issues/new -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
