On Fri, 2016-01-29 at 08:17 -0500, Emilien Macchi wrote:
> Hi,
>
> I'm wondering why don't we use Mitaka CI tested repository [1].
> IIRC, TripleO is currently using a snapshot which is updated
> asynchronously by TripleO CI folks.
> The problem is that we're not consistent with what RDO CI is
Hi,
I'm wondering why don't we use Mitaka CI tested repository [1].
IIRC, TripleO is currently using a snapshot which is updated
asynchronously by TripleO CI folks.
The problem is that we're not consistent with what RDO CI is testing. In
my memory and tell me if I'm wrong but it happens we're
On 01/29/2016 09:40 AM, Dan Prince wrote:
> On Fri, 2016-01-29 at 08:17 -0500, Emilien Macchi wrote:
>> Hi,
>>
>> I'm wondering why don't we use Mitaka CI tested repository [1].
>> IIRC, TripleO is currently using a snapshot which is updated
>> asynchronously by TripleO CI folks.
>> The problem
+1 for aligning efforts between Triple-O and RDO Manager around CI.
There's been a *lot* of work (trown++) towards RDO Manager CI and it'd
be great if Triple O could benefit from that.
Like Emilien said, our test coverage for promoting a set of packages
to "current-passed-ci" is huge already and
