I think our use case will have to keep using Ansible from pip as long as we are running off of static jenkins slaves on ci.centos.org, though. We have different projects leveraging Ansible for CI and they are using different versions of Ansible, thus we bootstrap a new virtualenv on each job so we don't conflict with each other. David Moreau Simard Senior Software Engineer | Openstack RDO dmsimard = [irc, github, twitter] On Tue, Nov 15, 2016 at 1:49 PM, Ken Dreyer <kdreyer at redhat.com> wrote: > On Tue, Nov 15, 2016 at 11:42 AM, Karsten Wade <kwade at redhat.com> wrote: >> On 11/14/2016 08:41 AM, Ken Dreyer wrote: >>> The current problem with the ceph-ansible project is that we lack a >>> robust CI framework to test all the codepaths, which means that PRs >>> get merged with little to no testing at this point. We're working to >>> change that, sometimes at the expense of merging things quickly. >> >> Do you think this current work with getting multiple Ansible versions in >> ci.centos.org as well as Francois' work overall with Ceph in CentOS CI >> might help supplement the upstream CI need? > > I think that will help. There's a lot of "pip installs" going on > currently for https://jenkins.ceph.com/job/ceph-ansible-pull-requests/ > :) > > - Ken > _______________________________________________ > CentOS-devel mailing list > CentOS-devel at centos.org > https://lists.centos.org/mailman/listinfo/centos-devel