Open Stack

On Wed, Jan 25, 2017 at 3:42 PM, Sagi Shnaidman <sshnaidm at redhat.com> wrote:
> HI, all
>
> I'd like to propose a bit different approach to run experimental jobs in
> TripleO CI.
> As you know we have OVB jobs and not-OVB jobs, and different pipelines for
> running these two types of them.
>
> What is current flow:
> if you need to run experimental jobs, you write comment with "check
> experimental" and all types of jobs will run - both OVB and not-OVB.
>
> What is proposal:
> for running OVB jobs only, you'll need to leave comment "check
> experimental-tripleo", for running non-OVB jobs only you'll still write
> "check experimental".
> For running all experimental jobs OVB and not-OVB just leave two comments:
> check experimental-tripleo
> check experimental
>
> From what I observed people usually want to run one-two of experimental jobs
> and usually one type of them. So this more explicit run can save us
> expensive OVB resources.
> If this not a case and you prefer to run all experimental jobs we have at
> once, please provide a feedback and I'll take it back.
>
> Patch about the topic: https://review.openstack.org/#/c/425184/

If infra is ok, I'm fine whith this change.
FWIW, infra rejected the proposal of having recheck-tripleo (to run
tripleo jobs running in RH1 cloud only).
Let's see how it goes now.

> Thanks
> --
> Best regards
> Sagi Shnaidman
>
> __________________________________________________________________________
> 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
>



-- 
Emilien Macchi