Howdy,
I was trying to use linch-pin that I found ( https://github.com/CentOS-PaaS-SIG/linch-pin) to spin up machines; however it requires Ansible 2.1. What is the accepted ways to handle situations where on the slave new versions of packages may be needed to call out to Duffy?
Thanks, Eric
Perhaps you could install it in a virtualenvironment from within the job?
David Moreau Simard Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
On Jul 9, 2016 7:40 AM, "Eric D Helms" ericdhelms@gmail.com wrote:
Howdy,
I was trying to use linch-pin that I found ( https://github.com/CentOS-PaaS-SIG/linch-pin) to spin up machines; however it requires Ansible 2.1. What is the accepted ways to handle situations where on the slave new versions of packages may be needed to call out to Duffy?
Thanks, Eric
Ci-users mailing list Ci-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
Virtualenv should take care of it that is how we are currently using it. On Jul 9, 2016 9:30 AM, "David Moreau Simard" dms@redhat.com wrote:
Perhaps you could install it in a virtualenvironment from within the job?
David Moreau Simard Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
On Jul 9, 2016 7:40 AM, "Eric D Helms" ericdhelms@gmail.com wrote:
Howdy,
I was trying to use linch-pin that I found ( https://github.com/CentOS-PaaS-SIG/linch-pin) to spin up machines; however it requires Ansible 2.1. What is the accepted ways to handle situations where on the slave new versions of packages may be needed to call out to Duffy?
Thanks, Eric
Ci-users mailing list Ci-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
Ci-users mailing list Ci-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-
Ari LiVigni -
David Moreau Simard -
Eric D Helms