My bet is first solve the problem, and then discuss how to improve the
solution.
Specifying the DIB_REPOREF variables by hand on the puppet-module element
in t-p-e will be an immediate
improvement in stability terms.
Then, it is fair to discuss how to automate the process to syncrhonise with
On 15.12.2015 19:12, Emilien Macchi wrote:
On 12/15/2015 12:23 PM, Jiří Stránský wrote:
On 15.12.2015 17:46, Emilien Macchi wrote:
For information, Puppet OpenStack CI is consistent for unit & functional
tests, we use a single (versionned) Puppetfile:
On 15.12.2015 17:46, Emilien Macchi wrote:
For information, Puppet OpenStack CI is consistent for unit & functional
tests, we use a single (versionned) Puppetfile:
https://github.com/openstack/puppet-openstack-integration/blob/master/Puppetfile
TripleO folks might want to have a look at this to
For information, Puppet OpenStack CI is consistent for unit & functional
tests, we use a single (versionned) Puppetfile:
https://github.com/openstack/puppet-openstack-integration/blob/master/Puppetfile
TripleO folks might want to have a look at this to follow the
dependencies actually supported
I suggest then to pin the dependencies from [1] to below.
Couldn't be posible to just clone the openstack/puppet-* ones
and then use some tool to install the dependencies from them, some
kind of
pip install -r requirements.txt
but adapted for Puppet? Does this tool exist?
[1]:
On 12/15/2015 12:23 PM, Jiří Stránský wrote:
> On 15.12.2015 17:46, Emilien Macchi wrote:
>> For information, Puppet OpenStack CI is consistent for unit & functional
>> tests, we use a single (versionned) Puppetfile:
>>
On Fri, 2015-12-11 at 21:50 +0100, Jaume Devesa wrote:
> Hi all,
>
> Today TripleO CI jobs failed because a new commit introduced on
> puppetlabs-mysql[1].
> Mr. Jiri Stransky solved it as a temporally fix by pinning the puppet
> module clone to a previous
> commit in the tripleo-common
Hi all,
Today TripleO CI jobs failed because a new commit introduced on
puppetlabs-mysql[1].
Mr. Jiri Stransky solved it as a temporally fix by pinning the puppet
module clone to a previous
commit in the tripleo-common project[2].
source-repositories puppet element[3] allows you to pin the
