On Fri, Jan 20, 2017 at 1:50 PM, Emilien Macchi <emil...@redhat.com> wrote:
> On Fri, Jan 20, 2017 at 7:30 AM, Alfredo Moralejo Alonso
> <amora...@redhat.com> wrote:
>> In RDO we are preparing for the incoming Ocata release. This means
In RDO we are preparing for the incoming Ocata release. This means
we'll create a new RDO Trunk builder "centos-ocata" in the next few
days (It will be ready for next week). This builder will get content
from stable/ocata branches of projects as they become available and
fallback to master
On Wed, Mar 8, 2017 at 12:44 PM, Steven Hardy wrote:
> Hi all,
> I wanted to raise visibility of a problem we're experiencing in TripleO CI,
> which I think will potentially affect other projects that consume trunk
> builds from the RDO repositories (and potentially other
Will you push a new tag release for ocata also?
On Wed, Feb 8, 2017 at 8:55 PM, Sukhdev Kapur wrote:
> Thank you - you da man...
> On Sun, Feb 5, 2017 at 11:27 PM, Gary Kotton wrote:
Great!, Thank you all for those words
On Mon, Oct 16, 2017 at 5:21 PM, Emilien Macchi wrote:
> sounds good, updating Gerrit permissions now.
> Thanks all,
> On Fri, Oct 13, 2017 at 2:09 PM, Iury Gregory wrote:
>> On Oct 13, 2017 17:13,
On Thu, Nov 23, 2017 at 7:59 PM, Emilien Macchi wrote:
> Queens's main theme is stabilization.
> That's what we're currently working on in our CI, see which areas we
> can consolidate and stabilize so we can continue to scale TripleO
> One of the challenges
-- Forwarded message --
From: Alfredo Moralejo Alonso <amora...@redhat.com>
Date: Fri, May 18, 2018 at 1:02 PM
Subject: Status of activities related to python3 PoC in RDO
To: d...@lists.rdoproject.org, us...@lists.rdoproject.org
One of the goals for RDO
ript stuck doing a "git pull --ff-only" for a repo.
Is it safe to revert/resend the review to get the missing releases?
On Fri, Jan 19, 2018 at 10:07 AM, Alfredo Moralejo Alonso <
> Review https://review.openstack.o
On Fri, Jan 19, 2018 at 5:50 PM, Sean McGinnis
> > Just an update - it does look like it was just the one job failure.
> There are
> > multiple puppet-* releases done as part of the one job, and it appears
> they are
> > processed in alphabetically order. So
Review https://review.openstack.org/#/c/535206/ was merged yesterday to
create some new releases for puppet modules in pike. I've observed that
releases were not created for following modules:
On Fri, Jan 19, 2018 at 6:29 PM, Alfredo Moralejo Alonso <
> On Fri, Jan 19, 2018 at 5:50 PM, Sean McGinnis <sean.mcgin...@gmx.com>
>> > Just an update - it does look like it w
On Sun, Feb 18, 2018 at 1:35 AM, Tony Breeds
> On Sat, Feb 17, 2018 at 04:40:12PM -0500, Dan Prince wrote:
> > Thanks for the update Emilien. A couple of things to add:
> > 1) This was really difficult to pin-point via the Heat stack error
> > message ('list
On Thu, Feb 22, 2018 at 12:06 AM, Tony Breeds <t...@bakeyournoodle.com>
> On Wed, Feb 21, 2018 at 08:53:09PM +0100, Alfredo Moralejo Alonso wrote:
> > Short version is:
> > 1. We generate a review to rdoinfo (RDO's package database) every time a
On Tue, Feb 20, 2018 at 12:24 AM, Tony Breeds <t...@bakeyournoodle.com>
> On Mon, Feb 19, 2018 at 06:10:56PM +0100, Alfredo Moralejo Alonso wrote:
> > Recently, we have added a job in post pipeline for openstack/requirements
> > in https://review.rdoproject.org t
On Sat, Mar 17, 2018 at 9:34 AM, Emilien Macchi wrote:
> During the PTG we had some nice conversations about how TripleO can make
> progress on testing OpenStack deployments with Python 3.
> In CC, Haikel, Alfredo and Javier, please complete if I missed something.
Mail list logo