[openstack-dev] [tripleo][ironic][heat] Adding back the tripleo check job

Sergey Kraynev skraynev at mirantis.com
Tue Dec 1 08:02:08 UTC 2015

On 30 November 2015 at 18:19, Derek Higgins <derekh at redhat.com> wrote:

> Hi All,
>     A few months tripleo switch from its devtest based CI to one that was
> based on instack. Before doing this we anticipated disruption in the ci
> jobs and removed them from non tripleo projects.
>     We'd like to investigate adding it back to heat and ironic as these
> are the two projects where we find our ci provides the most value. But we
> can only do this if the results from the job are treated as voting.
>     In the past most of the non tripleo projects tended to ignore the
> results from the tripleo job as it wasn't unusual for the job to broken for
> days at a time. The thing is, ignoring the results of the job is the reason
> (the majority of the time) it was broken in the first place.
>     To decrease the number of breakages we are now no longer running
> master code for everything (for the non tripleo projects we bump the
> versions we use periodically if they are working). I believe with this
> model the CI jobs we run have become a lot more reliable, there are still
> breakages but far less frequently.
> What I proposing is we add at least one of our tripleo jobs back to both
> heat and ironic (and other projects associated with them e.g. clients,
> ironicinspector etc..), tripleo will switch to running latest master of
> those repositories and the cores approving on those projects should wait
> for a passing CI jobs before hitting approve. So how do people feel about
> doing this? can we give it a go? A couple of people have already expressed
> an interest in doing this but I'd like to make sure were all in agreement
> before switching it on.

+1 for make it for Heat. I'd prefer approach mentioned by Zane - make it
non-voting for first time with enabling voting later in the future, when
 it be stable enough.

Also I have one more suggestion.
Could we make this TripleO job in following way:
 - with separate score, which is independent from score of other Heat jobs

I prefer mentioned approach, because:
1. Other jobs will be executed faster (AFAIK, it will take less or equal 1
hour), for TripleO it will take more time.
2. In the future it will allow to recheck only this particular job in
situation, when we want to tests some fix.
3. I hope, that Sahara team will provide similar job and we will get two
really useful job which will give one score, like: "third-party real
deployment test".

> thanks,
> Derek.
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151201/49e08965/attachment.html>

More information about the OpenStack-dev mailing list