Re: 3.6.1 branch is not treated as a stable branch, no CI as well

2015-12-02 Thread Sandro Bonazzola 
On Tue, Dec 1, 2015 at 6:42 PM, David Caro  wrote:

> On 12/01 19:37, Tal Nisan wrote:
> > Well, if the integration team is OK with that then I guess it's up to the
> > branch owner indeed and as said it will be very helpful for the backport
> > process if we indeed have CI jobs and gerrit hooks on the 3.6.1 branch
> for
> > the following weeks until 3.6.1 is released
>
> Ok, waiting for reply from the integration team, not sure if all of them
> are
> monitoring the infra list though, you might ask on devel too (or cc them)
>

ack on my side



>
> >
> > On Tue, Dec 1, 2015 at 7:30 PM, David Caro  wrote:
> >
> > > On 12/01 19:25, Tal Nisan wrote:
> > > > Well, it's not my decision but of the integration team, for me as the
> > > > stable branches maintainer it will help a lot to have the gerrit
> hooks
> > > (I'd
> > > > say even a must) and CI (not a must but definitely nice to have)
> > >
> > >
> > > I disagree on that, I think that it's the projects owners that should
> know
> > > what do they want to test and when, not the integration team.
> > >
> > > In any case, can you ask whoever makes the decision to ack?
> > >
> > > >
> > > > On Tue, Dec 1, 2015 at 7:23 PM, David Caro  wrote:
> > > >
> > > > >
> > > > > So a couple questions here:
> > > > >
> > > > >  * Who decides which branches are stable?
> > > > >  * Who decides which branches have ci?
> > > > >
> > > > > In the latter, you can easily add the extra branch to the vdsm
> project
> > > > > yaml:
> > > > >
> > > > >
> > > > >
> > >
> https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=blob;f=jobs/confs/projects/vdsm/vdsm_standard.yaml;hb=refs/heads/master
> > > > >
> > > > > There on line 55, just define another version:
> > > > >
> > > > >  - 3.6.1:
> > > > >  branch: ovirt-3.6.1
> > > > >
> > > > > And the jobs will be created automatically once merged
> > > > >
> > > > >
> > > > > (I know, it needs a bit of a cleanup, and we are working on even
> not
> > > > > having to
> > > > > change any yaml, but for now it's what we have)
> > > > >
> > > > > On 12/01 10:52, Tal Nisan wrote:
> > > > > > The 3.6.1 branch is not treated by the hooks as a stable branch
> [1]
> > > > > > Aside for that, CI is not running on new patches there
> > > > > >
> > > > > > [1]
> > > > > >
> > > > > >- Check TM::SKIP, not in a monitored branch (ovirt-engine-3.6
> > > > > >ovirt-engine-3.6.0 ovirt-engine-3.5 ovirt-engine-3.4
> > > ovirt-engine-3.3
> > > > > >engine_3.2 engine_3.1 ovirt-engine-3.5.2 ovirt-engine-3.4.0
> > > > > >ovirt-engine-3.3.4 ovirt-engine-3.3.3 ovirt-engine-3.3.2
> > > > > ovirt-engine-3.3.1)
> > > > > >- Check merged to previous::IGNORE, Not in stable branch
> > > > > >(['ovirt-engine-3.6', 'ovirt-engine-3.6.0',
> 'ovirt-engine-3.5',
> > > > > >'ovirt-engine-3.4', 'ovirt-engine-3.3', 'ovirt-engine-3.5.2',
> > > > > >'ovirt-engine-3.4.0', 'ovirt-engine-3.3.4',
> 'ovirt-engine-3.3.3',
> > > > > >'ovirt-engine-3.3.2', 'ovirt-engine-3.3.1'])
> > > > >
> > > > > > ___
> > > > > > Infra mailing list
> > > > > > Infra@ovirt.org
> > > > > > http://lists.ovirt.org/mailman/listinfo/infra
> > > > >
> > > > >
> > > > > --
> > > > > David Caro
> > > > >
> > > > > Red Hat S.L.
> > > > > Continuous Integration Engineer - EMEA ENG Virtualization R
> > > > >
> > > > > Tel.: +420 532 294 605
> > > > > Email: dc...@redhat.com
> > > > > IRC: dcaro|dcaroest@{freenode|oftc|redhat}
> > > > > Web: www.redhat.com
> > > > > RHT Global #: 82-62605
> > > > >
> > >
> > > --
> > > David Caro
> > >
> > > Red Hat S.L.
> > > Continuous Integration Engineer - EMEA ENG Virtualization R
> > >
> > > Tel.: +420 532 294 605
> > > Email: dc...@redhat.com
> > > IRC: dcaro|dcaroest@{freenode|oftc|redhat}
> > > Web: www.redhat.com
> > > RHT Global #: 82-62605
> > >
>
> --
> David Caro
>
> Red Hat S.L.
> Continuous Integration Engineer - EMEA ENG Virtualization R
>
> Tel.: +420 532 294 605
> Email: dc...@redhat.com
> IRC: dcaro|dcaroest@{freenode|oftc|redhat}
> Web: www.redhat.com
> RHT Global #: 82-62605
>
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>


-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: 3.6.1 branch is not treated as a stable branch, no CI as well

2015-12-02 Thread Sandro Bonazzola 
On Wed, Dec 2, 2015 at 2:00 PM, Eyal Edri  wrote:

> Sandro,
> I think we need to add this to the formal release process of ovirt, i.e:
>  - when is a new branch added to gerrit hooks as stable branch
>  - what kind of verification / ci we want to run on it..
>
>
+1
the new branch should be added as stable branch on creation.
verification should be inherited from parent branch (3.6.1 jobs should be
as for 3.6 branch)




> e
>
> On Wed, Dec 2, 2015 at 2:49 PM, David Caro  wrote:
>
>> On 12/02 13:35, Sandro Bonazzola wrote:
>> > On Tue, Dec 1, 2015 at 6:42 PM, David Caro  wrote:
>> >
>> > > On 12/01 19:37, Tal Nisan wrote:
>> > > > Well, if the integration team is OK with that then I guess it's up
>> to the
>> > > > branch owner indeed and as said it will be very helpful for the
>> backport
>> > > > process if we indeed have CI jobs and gerrit hooks on the 3.6.1
>> branch
>> > > for
>> > > > the following weeks until 3.6.1 is released
>> > >
>> > > Ok, waiting for reply from the integration team, not sure if all of
>> them
>> > > are
>> > > monitoring the infra list though, you might ask on devel too (or cc
>> them)
>> > >
>> >
>> > ack on my side
>>
>> Added the 3.6.1 branch to the stable branches list, about the jobs, feel
>> free
>> to send a patch following the indications below (from my previous email)
>> and
>> I'll review+merge
>>
>> >
>> >
>> >
>> > >
>> > > >
>> > > > On Tue, Dec 1, 2015 at 7:30 PM, David Caro 
>> wrote:
>> > > >
>> > > > > On 12/01 19:25, Tal Nisan wrote:
>> > > > > > Well, it's not my decision but of the integration team, for me
>> as the
>> > > > > > stable branches maintainer it will help a lot to have the gerrit
>> > > hooks
>> > > > > (I'd
>> > > > > > say even a must) and CI (not a must but definitely nice to have)
>> > > > >
>> > > > >
>> > > > > I disagree on that, I think that it's the projects owners that
>> should
>> > > know
>> > > > > what do they want to test and when, not the integration team.
>> > > > >
>> > > > > In any case, can you ask whoever makes the decision to ack?
>> > > > >
>> > > > > >
>> > > > > > On Tue, Dec 1, 2015 at 7:23 PM, David Caro 
>> wrote:
>> > > > > >
>> > > > > > >
>> > > > > > > So a couple questions here:
>> > > > > > >
>> > > > > > >  * Who decides which branches are stable?
>> > > > > > >  * Who decides which branches have ci?
>> > > > > > >
>> > > > > > > In the latter, you can easily add the extra branch to the vdsm
>> > > project
>> > > > > > > yaml:
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > >
>> > >
>> https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=blob;f=jobs/confs/projects/vdsm/vdsm_standard.yaml;hb=refs/heads/master
>> > > > > > >
>> > > > > > > There on line 55, just define another version:
>> > > > > > >
>> > > > > > >  - 3.6.1:
>> > > > > > >  branch: ovirt-3.6.1
>> > > > > > >
>> > > > > > > And the jobs will be created automatically once merged
>> > > > > > >
>> > > > > > >
>> > > > > > > (I know, it needs a bit of a cleanup, and we are working on
>> even
>> > > not
>> > > > > > > having to
>> > > > > > > change any yaml, but for now it's what we have)
>> > > > > > >
>> > > > > > > On 12/01 10:52, Tal Nisan wrote:
>> > > > > > > > The 3.6.1 branch is not treated by the hooks as a stable
>> branch
>> > > [1]
>> > > > > > > > Aside for that, CI is not running on new patches there
>> > > > > > > >
>> > > > > > > > [1]
>> > > > > > > >
>> > > > > > > >- Check TM::SKIP, not in a monitored branch
>> (ovirt-engine-3.6
>> > > > > > > >ovirt-engine-3.6.0 ovirt-engine-3.5 ovirt-engine-3.4
>> > > > > ovirt-engine-3.3
>> > > > > > > >engine_3.2 engine_3.1 ovirt-engine-3.5.2
>> ovirt-engine-3.4.0
>> > > > > > > >ovirt-engine-3.3.4 ovirt-engine-3.3.3 ovirt-engine-3.3.2
>> > > > > > > ovirt-engine-3.3.1)
>> > > > > > > >- Check merged to previous::IGNORE, Not in stable branch
>> > > > > > > >(['ovirt-engine-3.6', 'ovirt-engine-3.6.0',
>> > > 'ovirt-engine-3.5',
>> > > > > > > >'ovirt-engine-3.4', 'ovirt-engine-3.3',
>> 'ovirt-engine-3.5.2',
>> > > > > > > >'ovirt-engine-3.4.0', 'ovirt-engine-3.3.4',
>> > > 'ovirt-engine-3.3.3',
>> > > > > > > >'ovirt-engine-3.3.2', 'ovirt-engine-3.3.1'])
>> > > > > > >
>> > > > > > > > ___
>> > > > > > > > Infra mailing list
>> > > > > > > > Infra@ovirt.org
>> > > > > > > > http://lists.ovirt.org/mailman/listinfo/infra
>> > > > > > >
>> > > > > > >
>> > > > > > > --
>> > > > > > > David Caro
>> > > > > > >
>> > > > > > > Red Hat S.L.
>> > > > > > > Continuous Integration Engineer - EMEA ENG Virtualization R
>> > > > > > >
>> > > > > > > Tel.: +420 532 294 605
>> > > > > > > Email: dc...@redhat.com
>> > > > > > > IRC: dcaro|dcaroest@{freenode|oftc|redhat}
>> > > > > > > Web: www.redhat.com
>> > > > > > > RHT Global #: 82-62605
>> > > > > > >
>> > > > >
>> > > > > --
>> > > > > David Caro
>> > > > >
>> > > > > Red Hat S.L.

Re: 3.6.1 branch is not treated as a stable branch, no CI as well

2015-12-02 Thread Eyal Edri 
it should probably opened as a JIRA ticket to infra team with all the info
when needed.

e.

On Wed, Dec 2, 2015 at 3:24 PM, Sandro Bonazzola 
wrote:

>
>
> On Wed, Dec 2, 2015 at 2:00 PM, Eyal Edri  wrote:
>
>> Sandro,
>> I think we need to add this to the formal release process of ovirt, i.e:
>>  - when is a new branch added to gerrit hooks as stable branch
>>  - what kind of verification / ci we want to run on it..
>>
>>
> +1
> the new branch should be added as stable branch on creation.
> verification should be inherited from parent branch (3.6.1 jobs should be
> as for 3.6 branch)
>
>
>
>
>> e
>>
>> On Wed, Dec 2, 2015 at 2:49 PM, David Caro  wrote:
>>
>>> On 12/02 13:35, Sandro Bonazzola wrote:
>>> > On Tue, Dec 1, 2015 at 6:42 PM, David Caro  wrote:
>>> >
>>> > > On 12/01 19:37, Tal Nisan wrote:
>>> > > > Well, if the integration team is OK with that then I guess it's up
>>> to the
>>> > > > branch owner indeed and as said it will be very helpful for the
>>> backport
>>> > > > process if we indeed have CI jobs and gerrit hooks on the 3.6.1
>>> branch
>>> > > for
>>> > > > the following weeks until 3.6.1 is released
>>> > >
>>> > > Ok, waiting for reply from the integration team, not sure if all of
>>> them
>>> > > are
>>> > > monitoring the infra list though, you might ask on devel too (or cc
>>> them)
>>> > >
>>> >
>>> > ack on my side
>>>
>>> Added the 3.6.1 branch to the stable branches list, about the jobs, feel
>>> free
>>> to send a patch following the indications below (from my previous email)
>>> and
>>> I'll review+merge
>>>
>>> >
>>> >
>>> >
>>> > >
>>> > > >
>>> > > > On Tue, Dec 1, 2015 at 7:30 PM, David Caro 
>>> wrote:
>>> > > >
>>> > > > > On 12/01 19:25, Tal Nisan wrote:
>>> > > > > > Well, it's not my decision but of the integration team, for me
>>> as the
>>> > > > > > stable branches maintainer it will help a lot to have the
>>> gerrit
>>> > > hooks
>>> > > > > (I'd
>>> > > > > > say even a must) and CI (not a must but definitely nice to
>>> have)
>>> > > > >
>>> > > > >
>>> > > > > I disagree on that, I think that it's the projects owners that
>>> should
>>> > > know
>>> > > > > what do they want to test and when, not the integration team.
>>> > > > >
>>> > > > > In any case, can you ask whoever makes the decision to ack?
>>> > > > >
>>> > > > > >
>>> > > > > > On Tue, Dec 1, 2015 at 7:23 PM, David Caro 
>>> wrote:
>>> > > > > >
>>> > > > > > >
>>> > > > > > > So a couple questions here:
>>> > > > > > >
>>> > > > > > >  * Who decides which branches are stable?
>>> > > > > > >  * Who decides which branches have ci?
>>> > > > > > >
>>> > > > > > > In the latter, you can easily add the extra branch to the
>>> vdsm
>>> > > project
>>> > > > > > > yaml:
>>> > > > > > >
>>> > > > > > >
>>> > > > > > >
>>> > > > >
>>> > >
>>> https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=blob;f=jobs/confs/projects/vdsm/vdsm_standard.yaml;hb=refs/heads/master
>>> > > > > > >
>>> > > > > > > There on line 55, just define another version:
>>> > > > > > >
>>> > > > > > >  - 3.6.1:
>>> > > > > > >  branch: ovirt-3.6.1
>>> > > > > > >
>>> > > > > > > And the jobs will be created automatically once merged
>>> > > > > > >
>>> > > > > > >
>>> > > > > > > (I know, it needs a bit of a cleanup, and we are working on
>>> even
>>> > > not
>>> > > > > > > having to
>>> > > > > > > change any yaml, but for now it's what we have)
>>> > > > > > >
>>> > > > > > > On 12/01 10:52, Tal Nisan wrote:
>>> > > > > > > > The 3.6.1 branch is not treated by the hooks as a stable
>>> branch
>>> > > [1]
>>> > > > > > > > Aside for that, CI is not running on new patches there
>>> > > > > > > >
>>> > > > > > > > [1]
>>> > > > > > > >
>>> > > > > > > >- Check TM::SKIP, not in a monitored branch
>>> (ovirt-engine-3.6
>>> > > > > > > >ovirt-engine-3.6.0 ovirt-engine-3.5 ovirt-engine-3.4
>>> > > > > ovirt-engine-3.3
>>> > > > > > > >engine_3.2 engine_3.1 ovirt-engine-3.5.2
>>> ovirt-engine-3.4.0
>>> > > > > > > >ovirt-engine-3.3.4 ovirt-engine-3.3.3 ovirt-engine-3.3.2
>>> > > > > > > ovirt-engine-3.3.1)
>>> > > > > > > >- Check merged to previous::IGNORE, Not in stable branch
>>> > > > > > > >(['ovirt-engine-3.6', 'ovirt-engine-3.6.0',
>>> > > 'ovirt-engine-3.5',
>>> > > > > > > >'ovirt-engine-3.4', 'ovirt-engine-3.3',
>>> 'ovirt-engine-3.5.2',
>>> > > > > > > >'ovirt-engine-3.4.0', 'ovirt-engine-3.3.4',
>>> > > 'ovirt-engine-3.3.3',
>>> > > > > > > >'ovirt-engine-3.3.2', 'ovirt-engine-3.3.1'])
>>> > > > > > >
>>> > > > > > > > ___
>>> > > > > > > > Infra mailing list
>>> > > > > > > > Infra@ovirt.org
>>> > > > > > > > http://lists.ovirt.org/mailman/listinfo/infra
>>> > > > > > >
>>> > > > > > >
>>> > > > > > > --
>>> > > > > > > David Caro
>>> > > > > > >
>>> > > > > > > Red Hat S.L.
>>> > > > > > > Continuous Integration Engineer - EMEA ENG

Re: 3.6.1 branch is not treated as a stable branch, no CI as well

2015-12-02 Thread David Caro 
On 12/02 13:35, Sandro Bonazzola wrote:
> On Tue, Dec 1, 2015 at 6:42 PM, David Caro  wrote:
> 
> > On 12/01 19:37, Tal Nisan wrote:
> > > Well, if the integration team is OK with that then I guess it's up to the
> > > branch owner indeed and as said it will be very helpful for the backport
> > > process if we indeed have CI jobs and gerrit hooks on the 3.6.1 branch
> > for
> > > the following weeks until 3.6.1 is released
> >
> > Ok, waiting for reply from the integration team, not sure if all of them
> > are
> > monitoring the infra list though, you might ask on devel too (or cc them)
> >
> 
> ack on my side

Added the 3.6.1 branch to the stable branches list, about the jobs, feel free
to send a patch following the indications below (from my previous email) and
I'll review+merge

> 
> 
> 
> >
> > >
> > > On Tue, Dec 1, 2015 at 7:30 PM, David Caro  wrote:
> > >
> > > > On 12/01 19:25, Tal Nisan wrote:
> > > > > Well, it's not my decision but of the integration team, for me as the
> > > > > stable branches maintainer it will help a lot to have the gerrit
> > hooks
> > > > (I'd
> > > > > say even a must) and CI (not a must but definitely nice to have)
> > > >
> > > >
> > > > I disagree on that, I think that it's the projects owners that should
> > know
> > > > what do they want to test and when, not the integration team.
> > > >
> > > > In any case, can you ask whoever makes the decision to ack?
> > > >
> > > > >
> > > > > On Tue, Dec 1, 2015 at 7:23 PM, David Caro  wrote:
> > > > >
> > > > > >
> > > > > > So a couple questions here:
> > > > > >
> > > > > >  * Who decides which branches are stable?
> > > > > >  * Who decides which branches have ci?
> > > > > >
> > > > > > In the latter, you can easily add the extra branch to the vdsm
> > project
> > > > > > yaml:
> > > > > >
> > > > > >
> > > > > >
> > > >
> > https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=blob;f=jobs/confs/projects/vdsm/vdsm_standard.yaml;hb=refs/heads/master
> > > > > >
> > > > > > There on line 55, just define another version:
> > > > > >
> > > > > >  - 3.6.1:
> > > > > >  branch: ovirt-3.6.1
> > > > > >
> > > > > > And the jobs will be created automatically once merged
> > > > > >
> > > > > >
> > > > > > (I know, it needs a bit of a cleanup, and we are working on even
> > not
> > > > > > having to
> > > > > > change any yaml, but for now it's what we have)
> > > > > >
> > > > > > On 12/01 10:52, Tal Nisan wrote:
> > > > > > > The 3.6.1 branch is not treated by the hooks as a stable branch
> > [1]
> > > > > > > Aside for that, CI is not running on new patches there
> > > > > > >
> > > > > > > [1]
> > > > > > >
> > > > > > >- Check TM::SKIP, not in a monitored branch (ovirt-engine-3.6
> > > > > > >ovirt-engine-3.6.0 ovirt-engine-3.5 ovirt-engine-3.4
> > > > ovirt-engine-3.3
> > > > > > >engine_3.2 engine_3.1 ovirt-engine-3.5.2 ovirt-engine-3.4.0
> > > > > > >ovirt-engine-3.3.4 ovirt-engine-3.3.3 ovirt-engine-3.3.2
> > > > > > ovirt-engine-3.3.1)
> > > > > > >- Check merged to previous::IGNORE, Not in stable branch
> > > > > > >(['ovirt-engine-3.6', 'ovirt-engine-3.6.0',
> > 'ovirt-engine-3.5',
> > > > > > >'ovirt-engine-3.4', 'ovirt-engine-3.3', 'ovirt-engine-3.5.2',
> > > > > > >'ovirt-engine-3.4.0', 'ovirt-engine-3.3.4',
> > 'ovirt-engine-3.3.3',
> > > > > > >'ovirt-engine-3.3.2', 'ovirt-engine-3.3.1'])
> > > > > >
> > > > > > > ___
> > > > > > > Infra mailing list
> > > > > > > Infra@ovirt.org
> > > > > > > http://lists.ovirt.org/mailman/listinfo/infra
> > > > > >
> > > > > >
> > > > > > --
> > > > > > David Caro
> > > > > >
> > > > > > Red Hat S.L.
> > > > > > Continuous Integration Engineer - EMEA ENG Virtualization R
> > > > > >
> > > > > > Tel.: +420 532 294 605
> > > > > > Email: dc...@redhat.com
> > > > > > IRC: dcaro|dcaroest@{freenode|oftc|redhat}
> > > > > > Web: www.redhat.com
> > > > > > RHT Global #: 82-62605
> > > > > >
> > > >
> > > > --
> > > > David Caro
> > > >
> > > > Red Hat S.L.
> > > > Continuous Integration Engineer - EMEA ENG Virtualization R
> > > >
> > > > Tel.: +420 532 294 605
> > > > Email: dc...@redhat.com
> > > > IRC: dcaro|dcaroest@{freenode|oftc|redhat}
> > > > Web: www.redhat.com
> > > > RHT Global #: 82-62605
> > > >
> >
> > --
> > David Caro
> >
> > Red Hat S.L.
> > Continuous Integration Engineer - EMEA ENG Virtualization R
> >
> > Tel.: +420 532 294 605
> > Email: dc...@redhat.com
> > IRC: dcaro|dcaroest@{freenode|oftc|redhat}
> > Web: www.redhat.com
> > RHT Global #: 82-62605
> >
> > ___
> > Infra mailing list
> > Infra@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> >
> 
> 
> -- 
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com

-- 
David Caro

Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R

Re: 3.6.1 branch is not treated as a stable branch, no CI as well

2015-12-02 Thread Eyal Edri 
Sandro,
I think we need to add this to the formal release process of ovirt, i.e:
 - when is a new branch added to gerrit hooks as stable branch
 - what kind of verification / ci we want to run on it..

e

On Wed, Dec 2, 2015 at 2:49 PM, David Caro  wrote:

> On 12/02 13:35, Sandro Bonazzola wrote:
> > On Tue, Dec 1, 2015 at 6:42 PM, David Caro  wrote:
> >
> > > On 12/01 19:37, Tal Nisan wrote:
> > > > Well, if the integration team is OK with that then I guess it's up
> to the
> > > > branch owner indeed and as said it will be very helpful for the
> backport
> > > > process if we indeed have CI jobs and gerrit hooks on the 3.6.1
> branch
> > > for
> > > > the following weeks until 3.6.1 is released
> > >
> > > Ok, waiting for reply from the integration team, not sure if all of
> them
> > > are
> > > monitoring the infra list though, you might ask on devel too (or cc
> them)
> > >
> >
> > ack on my side
>
> Added the 3.6.1 branch to the stable branches list, about the jobs, feel
> free
> to send a patch following the indications below (from my previous email)
> and
> I'll review+merge
>
> >
> >
> >
> > >
> > > >
> > > > On Tue, Dec 1, 2015 at 7:30 PM, David Caro  wrote:
> > > >
> > > > > On 12/01 19:25, Tal Nisan wrote:
> > > > > > Well, it's not my decision but of the integration team, for me
> as the
> > > > > > stable branches maintainer it will help a lot to have the gerrit
> > > hooks
> > > > > (I'd
> > > > > > say even a must) and CI (not a must but definitely nice to have)
> > > > >
> > > > >
> > > > > I disagree on that, I think that it's the projects owners that
> should
> > > know
> > > > > what do they want to test and when, not the integration team.
> > > > >
> > > > > In any case, can you ask whoever makes the decision to ack?
> > > > >
> > > > > >
> > > > > > On Tue, Dec 1, 2015 at 7:23 PM, David Caro 
> wrote:
> > > > > >
> > > > > > >
> > > > > > > So a couple questions here:
> > > > > > >
> > > > > > >  * Who decides which branches are stable?
> > > > > > >  * Who decides which branches have ci?
> > > > > > >
> > > > > > > In the latter, you can easily add the extra branch to the vdsm
> > > project
> > > > > > > yaml:
> > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > >
> https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=blob;f=jobs/confs/projects/vdsm/vdsm_standard.yaml;hb=refs/heads/master
> > > > > > >
> > > > > > > There on line 55, just define another version:
> > > > > > >
> > > > > > >  - 3.6.1:
> > > > > > >  branch: ovirt-3.6.1
> > > > > > >
> > > > > > > And the jobs will be created automatically once merged
> > > > > > >
> > > > > > >
> > > > > > > (I know, it needs a bit of a cleanup, and we are working on
> even
> > > not
> > > > > > > having to
> > > > > > > change any yaml, but for now it's what we have)
> > > > > > >
> > > > > > > On 12/01 10:52, Tal Nisan wrote:
> > > > > > > > The 3.6.1 branch is not treated by the hooks as a stable
> branch
> > > [1]
> > > > > > > > Aside for that, CI is not running on new patches there
> > > > > > > >
> > > > > > > > [1]
> > > > > > > >
> > > > > > > >- Check TM::SKIP, not in a monitored branch
> (ovirt-engine-3.6
> > > > > > > >ovirt-engine-3.6.0 ovirt-engine-3.5 ovirt-engine-3.4
> > > > > ovirt-engine-3.3
> > > > > > > >engine_3.2 engine_3.1 ovirt-engine-3.5.2
> ovirt-engine-3.4.0
> > > > > > > >ovirt-engine-3.3.4 ovirt-engine-3.3.3 ovirt-engine-3.3.2
> > > > > > > ovirt-engine-3.3.1)
> > > > > > > >- Check merged to previous::IGNORE, Not in stable branch
> > > > > > > >(['ovirt-engine-3.6', 'ovirt-engine-3.6.0',
> > > 'ovirt-engine-3.5',
> > > > > > > >'ovirt-engine-3.4', 'ovirt-engine-3.3',
> 'ovirt-engine-3.5.2',
> > > > > > > >'ovirt-engine-3.4.0', 'ovirt-engine-3.3.4',
> > > 'ovirt-engine-3.3.3',
> > > > > > > >'ovirt-engine-3.3.2', 'ovirt-engine-3.3.1'])
> > > > > > >
> > > > > > > > ___
> > > > > > > > Infra mailing list
> > > > > > > > Infra@ovirt.org
> > > > > > > > http://lists.ovirt.org/mailman/listinfo/infra
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > David Caro
> > > > > > >
> > > > > > > Red Hat S.L.
> > > > > > > Continuous Integration Engineer - EMEA ENG Virtualization R
> > > > > > >
> > > > > > > Tel.: +420 532 294 605
> > > > > > > Email: dc...@redhat.com
> > > > > > > IRC: dcaro|dcaroest@{freenode|oftc|redhat}
> > > > > > > Web: www.redhat.com
> > > > > > > RHT Global #: 82-62605
> > > > > > >
> > > > >
> > > > > --
> > > > > David Caro
> > > > >
> > > > > Red Hat S.L.
> > > > > Continuous Integration Engineer - EMEA ENG Virtualization R
> > > > >
> > > > > Tel.: +420 532 294 605
> > > > > Email: dc...@redhat.com
> > > > > IRC: dcaro|dcaroest@{freenode|oftc|redhat}
> > > > > Web: www.redhat.com
> > > > > RHT Global #: 82-62605
> > > > >
> > >
> > > --
> > > David Caro
> > >
> > > Red Hat S.L.
> > > Continuous Integration Engineer - EMEA ENG

Re: 3.6.1 branch is not treated as a stable branch, no CI as well

2015-12-01 Thread David Caro 
On 12/01 19:37, Tal Nisan wrote:
> Well, if the integration team is OK with that then I guess it's up to the
> branch owner indeed and as said it will be very helpful for the backport
> process if we indeed have CI jobs and gerrit hooks on the 3.6.1 branch for
> the following weeks until 3.6.1 is released

Ok, waiting for reply from the integration team, not sure if all of them are
monitoring the infra list though, you might ask on devel too (or cc them)

> 
> On Tue, Dec 1, 2015 at 7:30 PM, David Caro  wrote:
> 
> > On 12/01 19:25, Tal Nisan wrote:
> > > Well, it's not my decision but of the integration team, for me as the
> > > stable branches maintainer it will help a lot to have the gerrit hooks
> > (I'd
> > > say even a must) and CI (not a must but definitely nice to have)
> >
> >
> > I disagree on that, I think that it's the projects owners that should know
> > what do they want to test and when, not the integration team.
> >
> > In any case, can you ask whoever makes the decision to ack?
> >
> > >
> > > On Tue, Dec 1, 2015 at 7:23 PM, David Caro  wrote:
> > >
> > > >
> > > > So a couple questions here:
> > > >
> > > >  * Who decides which branches are stable?
> > > >  * Who decides which branches have ci?
> > > >
> > > > In the latter, you can easily add the extra branch to the vdsm project
> > > > yaml:
> > > >
> > > >
> > > >
> > https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=blob;f=jobs/confs/projects/vdsm/vdsm_standard.yaml;hb=refs/heads/master
> > > >
> > > > There on line 55, just define another version:
> > > >
> > > >  - 3.6.1:
> > > >  branch: ovirt-3.6.1
> > > >
> > > > And the jobs will be created automatically once merged
> > > >
> > > >
> > > > (I know, it needs a bit of a cleanup, and we are working on even not
> > > > having to
> > > > change any yaml, but for now it's what we have)
> > > >
> > > > On 12/01 10:52, Tal Nisan wrote:
> > > > > The 3.6.1 branch is not treated by the hooks as a stable branch [1]
> > > > > Aside for that, CI is not running on new patches there
> > > > >
> > > > > [1]
> > > > >
> > > > >- Check TM::SKIP, not in a monitored branch (ovirt-engine-3.6
> > > > >ovirt-engine-3.6.0 ovirt-engine-3.5 ovirt-engine-3.4
> > ovirt-engine-3.3
> > > > >engine_3.2 engine_3.1 ovirt-engine-3.5.2 ovirt-engine-3.4.0
> > > > >ovirt-engine-3.3.4 ovirt-engine-3.3.3 ovirt-engine-3.3.2
> > > > ovirt-engine-3.3.1)
> > > > >- Check merged to previous::IGNORE, Not in stable branch
> > > > >(['ovirt-engine-3.6', 'ovirt-engine-3.6.0', 'ovirt-engine-3.5',
> > > > >'ovirt-engine-3.4', 'ovirt-engine-3.3', 'ovirt-engine-3.5.2',
> > > > >'ovirt-engine-3.4.0', 'ovirt-engine-3.3.4', 'ovirt-engine-3.3.3',
> > > > >'ovirt-engine-3.3.2', 'ovirt-engine-3.3.1'])
> > > >
> > > > > ___
> > > > > Infra mailing list
> > > > > Infra@ovirt.org
> > > > > http://lists.ovirt.org/mailman/listinfo/infra
> > > >
> > > >
> > > > --
> > > > David Caro
> > > >
> > > > Red Hat S.L.
> > > > Continuous Integration Engineer - EMEA ENG Virtualization R
> > > >
> > > > Tel.: +420 532 294 605
> > > > Email: dc...@redhat.com
> > > > IRC: dcaro|dcaroest@{freenode|oftc|redhat}
> > > > Web: www.redhat.com
> > > > RHT Global #: 82-62605
> > > >
> >
> > --
> > David Caro
> >
> > Red Hat S.L.
> > Continuous Integration Engineer - EMEA ENG Virtualization R
> >
> > Tel.: +420 532 294 605
> > Email: dc...@redhat.com
> > IRC: dcaro|dcaroest@{freenode|oftc|redhat}
> > Web: www.redhat.com
> > RHT Global #: 82-62605
> >

-- 
David Caro

Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R

Tel.: +420 532 294 605
Email: dc...@redhat.com
IRC: dcaro|dcaroest@{freenode|oftc|redhat}
Web: www.redhat.com
RHT Global #: 82-62605


signature.asc
Description: PGP signature
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: 3.6.1 branch is not treated as a stable branch, no CI as well

2015-12-01 Thread David Caro 

So a couple questions here:

 * Who decides which branches are stable?
 * Who decides which branches have ci?

In the latter, you can easily add the extra branch to the vdsm project yaml:

  
https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=blob;f=jobs/confs/projects/vdsm/vdsm_standard.yaml;hb=refs/heads/master

There on line 55, just define another version:

 - 3.6.1:
 branch: ovirt-3.6.1

And the jobs will be created automatically once merged


(I know, it needs a bit of a cleanup, and we are working on even not having to
change any yaml, but for now it's what we have)

On 12/01 10:52, Tal Nisan wrote:
> The 3.6.1 branch is not treated by the hooks as a stable branch [1]
> Aside for that, CI is not running on new patches there
> 
> [1]
> 
>- Check TM::SKIP, not in a monitored branch (ovirt-engine-3.6
>ovirt-engine-3.6.0 ovirt-engine-3.5 ovirt-engine-3.4 ovirt-engine-3.3
>engine_3.2 engine_3.1 ovirt-engine-3.5.2 ovirt-engine-3.4.0
>ovirt-engine-3.3.4 ovirt-engine-3.3.3 ovirt-engine-3.3.2 
> ovirt-engine-3.3.1)
>- Check merged to previous::IGNORE, Not in stable branch
>(['ovirt-engine-3.6', 'ovirt-engine-3.6.0', 'ovirt-engine-3.5',
>'ovirt-engine-3.4', 'ovirt-engine-3.3', 'ovirt-engine-3.5.2',
>'ovirt-engine-3.4.0', 'ovirt-engine-3.3.4', 'ovirt-engine-3.3.3',
>'ovirt-engine-3.3.2', 'ovirt-engine-3.3.1'])

> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra


-- 
David Caro

Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R

Tel.: +420 532 294 605
Email: dc...@redhat.com
IRC: dcaro|dcaroest@{freenode|oftc|redhat}
Web: www.redhat.com
RHT Global #: 82-62605


signature.asc
Description: PGP signature
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: 3.6.1 branch is not treated as a stable branch, no CI as well

2015-12-01 Thread David Caro 
On 12/01 19:25, Tal Nisan wrote:
> Well, it's not my decision but of the integration team, for me as the
> stable branches maintainer it will help a lot to have the gerrit hooks (I'd
> say even a must) and CI (not a must but definitely nice to have)


I disagree on that, I think that it's the projects owners that should know
what do they want to test and when, not the integration team.

In any case, can you ask whoever makes the decision to ack?

> 
> On Tue, Dec 1, 2015 at 7:23 PM, David Caro  wrote:
> 
> >
> > So a couple questions here:
> >
> >  * Who decides which branches are stable?
> >  * Who decides which branches have ci?
> >
> > In the latter, you can easily add the extra branch to the vdsm project
> > yaml:
> >
> >
> > https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=blob;f=jobs/confs/projects/vdsm/vdsm_standard.yaml;hb=refs/heads/master
> >
> > There on line 55, just define another version:
> >
> >  - 3.6.1:
> >  branch: ovirt-3.6.1
> >
> > And the jobs will be created automatically once merged
> >
> >
> > (I know, it needs a bit of a cleanup, and we are working on even not
> > having to
> > change any yaml, but for now it's what we have)
> >
> > On 12/01 10:52, Tal Nisan wrote:
> > > The 3.6.1 branch is not treated by the hooks as a stable branch [1]
> > > Aside for that, CI is not running on new patches there
> > >
> > > [1]
> > >
> > >- Check TM::SKIP, not in a monitored branch (ovirt-engine-3.6
> > >ovirt-engine-3.6.0 ovirt-engine-3.5 ovirt-engine-3.4 ovirt-engine-3.3
> > >engine_3.2 engine_3.1 ovirt-engine-3.5.2 ovirt-engine-3.4.0
> > >ovirt-engine-3.3.4 ovirt-engine-3.3.3 ovirt-engine-3.3.2
> > ovirt-engine-3.3.1)
> > >- Check merged to previous::IGNORE, Not in stable branch
> > >(['ovirt-engine-3.6', 'ovirt-engine-3.6.0', 'ovirt-engine-3.5',
> > >'ovirt-engine-3.4', 'ovirt-engine-3.3', 'ovirt-engine-3.5.2',
> > >'ovirt-engine-3.4.0', 'ovirt-engine-3.3.4', 'ovirt-engine-3.3.3',
> > >'ovirt-engine-3.3.2', 'ovirt-engine-3.3.1'])
> >
> > > ___
> > > Infra mailing list
> > > Infra@ovirt.org
> > > http://lists.ovirt.org/mailman/listinfo/infra
> >
> >
> > --
> > David Caro
> >
> > Red Hat S.L.
> > Continuous Integration Engineer - EMEA ENG Virtualization R
> >
> > Tel.: +420 532 294 605
> > Email: dc...@redhat.com
> > IRC: dcaro|dcaroest@{freenode|oftc|redhat}
> > Web: www.redhat.com
> > RHT Global #: 82-62605
> >

-- 
David Caro

Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R

Tel.: +420 532 294 605
Email: dc...@redhat.com
IRC: dcaro|dcaroest@{freenode|oftc|redhat}
Web: www.redhat.com
RHT Global #: 82-62605


signature.asc
Description: PGP signature
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: 3.6.1 branch is not treated as a stable branch, no CI as well

2015-12-01 Thread Tal Nisan 
Well, if the integration team is OK with that then I guess it's up to the
branch owner indeed and as said it will be very helpful for the backport
process if we indeed have CI jobs and gerrit hooks on the 3.6.1 branch for
the following weeks until 3.6.1 is released

On Tue, Dec 1, 2015 at 7:30 PM, David Caro  wrote:

> On 12/01 19:25, Tal Nisan wrote:
> > Well, it's not my decision but of the integration team, for me as the
> > stable branches maintainer it will help a lot to have the gerrit hooks
> (I'd
> > say even a must) and CI (not a must but definitely nice to have)
>
>
> I disagree on that, I think that it's the projects owners that should know
> what do they want to test and when, not the integration team.
>
> In any case, can you ask whoever makes the decision to ack?
>
> >
> > On Tue, Dec 1, 2015 at 7:23 PM, David Caro  wrote:
> >
> > >
> > > So a couple questions here:
> > >
> > >  * Who decides which branches are stable?
> > >  * Who decides which branches have ci?
> > >
> > > In the latter, you can easily add the extra branch to the vdsm project
> > > yaml:
> > >
> > >
> > >
> https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=blob;f=jobs/confs/projects/vdsm/vdsm_standard.yaml;hb=refs/heads/master
> > >
> > > There on line 55, just define another version:
> > >
> > >  - 3.6.1:
> > >  branch: ovirt-3.6.1
> > >
> > > And the jobs will be created automatically once merged
> > >
> > >
> > > (I know, it needs a bit of a cleanup, and we are working on even not
> > > having to
> > > change any yaml, but for now it's what we have)
> > >
> > > On 12/01 10:52, Tal Nisan wrote:
> > > > The 3.6.1 branch is not treated by the hooks as a stable branch [1]
> > > > Aside for that, CI is not running on new patches there
> > > >
> > > > [1]
> > > >
> > > >- Check TM::SKIP, not in a monitored branch (ovirt-engine-3.6
> > > >ovirt-engine-3.6.0 ovirt-engine-3.5 ovirt-engine-3.4
> ovirt-engine-3.3
> > > >engine_3.2 engine_3.1 ovirt-engine-3.5.2 ovirt-engine-3.4.0
> > > >ovirt-engine-3.3.4 ovirt-engine-3.3.3 ovirt-engine-3.3.2
> > > ovirt-engine-3.3.1)
> > > >- Check merged to previous::IGNORE, Not in stable branch
> > > >(['ovirt-engine-3.6', 'ovirt-engine-3.6.0', 'ovirt-engine-3.5',
> > > >'ovirt-engine-3.4', 'ovirt-engine-3.3', 'ovirt-engine-3.5.2',
> > > >'ovirt-engine-3.4.0', 'ovirt-engine-3.3.4', 'ovirt-engine-3.3.3',
> > > >'ovirt-engine-3.3.2', 'ovirt-engine-3.3.1'])
> > >
> > > > ___
> > > > Infra mailing list
> > > > Infra@ovirt.org
> > > > http://lists.ovirt.org/mailman/listinfo/infra
> > >
> > >
> > > --
> > > David Caro
> > >
> > > Red Hat S.L.
> > > Continuous Integration Engineer - EMEA ENG Virtualization R
> > >
> > > Tel.: +420 532 294 605
> > > Email: dc...@redhat.com
> > > IRC: dcaro|dcaroest@{freenode|oftc|redhat}
> > > Web: www.redhat.com
> > > RHT Global #: 82-62605
> > >
>
> --
> David Caro
>
> Red Hat S.L.
> Continuous Integration Engineer - EMEA ENG Virtualization R
>
> Tel.: +420 532 294 605
> Email: dc...@redhat.com
> IRC: dcaro|dcaroest@{freenode|oftc|redhat}
> Web: www.redhat.com
> RHT Global #: 82-62605
>
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: 3.6.1 branch is not treated as a stable branch, no CI as well

2015-12-01 Thread Tal Nisan 
Well, it's not my decision but of the integration team, for me as the
stable branches maintainer it will help a lot to have the gerrit hooks (I'd
say even a must) and CI (not a must but definitely nice to have)

On Tue, Dec 1, 2015 at 7:23 PM, David Caro  wrote:

>
> So a couple questions here:
>
>  * Who decides which branches are stable?
>  * Who decides which branches have ci?
>
> In the latter, you can easily add the extra branch to the vdsm project
> yaml:
>
>
> https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=blob;f=jobs/confs/projects/vdsm/vdsm_standard.yaml;hb=refs/heads/master
>
> There on line 55, just define another version:
>
>  - 3.6.1:
>  branch: ovirt-3.6.1
>
> And the jobs will be created automatically once merged
>
>
> (I know, it needs a bit of a cleanup, and we are working on even not
> having to
> change any yaml, but for now it's what we have)
>
> On 12/01 10:52, Tal Nisan wrote:
> > The 3.6.1 branch is not treated by the hooks as a stable branch [1]
> > Aside for that, CI is not running on new patches there
> >
> > [1]
> >
> >- Check TM::SKIP, not in a monitored branch (ovirt-engine-3.6
> >ovirt-engine-3.6.0 ovirt-engine-3.5 ovirt-engine-3.4 ovirt-engine-3.3
> >engine_3.2 engine_3.1 ovirt-engine-3.5.2 ovirt-engine-3.4.0
> >ovirt-engine-3.3.4 ovirt-engine-3.3.3 ovirt-engine-3.3.2
> ovirt-engine-3.3.1)
> >- Check merged to previous::IGNORE, Not in stable branch
> >(['ovirt-engine-3.6', 'ovirt-engine-3.6.0', 'ovirt-engine-3.5',
> >'ovirt-engine-3.4', 'ovirt-engine-3.3', 'ovirt-engine-3.5.2',
> >'ovirt-engine-3.4.0', 'ovirt-engine-3.3.4', 'ovirt-engine-3.3.3',
> >'ovirt-engine-3.3.2', 'ovirt-engine-3.3.1'])
>
> > ___
> > Infra mailing list
> > Infra@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
>
>
> --
> David Caro
>
> Red Hat S.L.
> Continuous Integration Engineer - EMEA ENG Virtualization R
>
> Tel.: +420 532 294 605
> Email: dc...@redhat.com
> IRC: dcaro|dcaroest@{freenode|oftc|redhat}
> Web: www.redhat.com
> RHT Global #: 82-62605
>
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: 3.6.1 branch is not treated as a stable branch, no CI as well

2015-12-01 Thread Eyal Edri 
On Tue, Dec 1, 2015 at 7:42 PM, David Caro  wrote:

> On 12/01 19:37, Tal Nisan wrote:
> > Well, if the integration team is OK with that then I guess it's up to the
> > branch owner indeed and as said it will be very helpful for the backport
> > process if we indeed have CI jobs and gerrit hooks on the 3.6.1 branch
> for
> > the following weeks until 3.6.1 is released
>
> Ok, waiting for reply from the integration team, not sure if all of them
> are
> monitoring the infra list though, you might ask on devel too (or cc them)
>

>From CI pov, +1 on enabling all gerrit hooks on any stable branch we add,
as far as jenkins jobs we have to be very carfeul with it, since it will
mean duplicating many jobs we have right now and not sure jenkins can
handle it.
either we decide on a limited must have sanity set of tests to run on
version branches (like 3.6.1) or we can suffice with the 3.6 jobs,
since they are a superset of 3.6.1 and if something fails there it means it
will fail 3.6.1, the otherway is very unlikely (i.e fail on 3.6.1 and not
3.6) so
this is why i think the extra resources and time per job that will be added
to jenkins won't worth adding all the jobs.

e.


>
> >
> > On Tue, Dec 1, 2015 at 7:30 PM, David Caro  wrote:
> >
> > > On 12/01 19:25, Tal Nisan wrote:
> > > > Well, it's not my decision but of the integration team, for me as the
> > > > stable branches maintainer it will help a lot to have the gerrit
> hooks
> > > (I'd
> > > > say even a must) and CI (not a must but definitely nice to have)
> > >
> > >
> > > I disagree on that, I think that it's the projects owners that should
> know
> > > what do they want to test and when, not the integration team.
> > >
> > > In any case, can you ask whoever makes the decision to ack?
> > >
> > > >
> > > > On Tue, Dec 1, 2015 at 7:23 PM, David Caro  wrote:
> > > >
> > > > >
> > > > > So a couple questions here:
> > > > >
> > > > >  * Who decides which branches are stable?
> > > > >  * Who decides which branches have ci?
> > > > >
> > > > > In the latter, you can easily add the extra branch to the vdsm
> project
> > > > > yaml:
> > > > >
> > > > >
> > > > >
> > >
> https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=blob;f=jobs/confs/projects/vdsm/vdsm_standard.yaml;hb=refs/heads/master
> > > > >
> > > > > There on line 55, just define another version:
> > > > >
> > > > >  - 3.6.1:
> > > > >  branch: ovirt-3.6.1
> > > > >
> > > > > And the jobs will be created automatically once merged
> > > > >
> > > > >
> > > > > (I know, it needs a bit of a cleanup, and we are working on even
> not
> > > > > having to
> > > > > change any yaml, but for now it's what we have)
> > > > >
> > > > > On 12/01 10:52, Tal Nisan wrote:
> > > > > > The 3.6.1 branch is not treated by the hooks as a stable branch
> [1]
> > > > > > Aside for that, CI is not running on new patches there
> > > > > >
> > > > > > [1]
> > > > > >
> > > > > >- Check TM::SKIP, not in a monitored branch (ovirt-engine-3.6
> > > > > >ovirt-engine-3.6.0 ovirt-engine-3.5 ovirt-engine-3.4
> > > ovirt-engine-3.3
> > > > > >engine_3.2 engine_3.1 ovirt-engine-3.5.2 ovirt-engine-3.4.0
> > > > > >ovirt-engine-3.3.4 ovirt-engine-3.3.3 ovirt-engine-3.3.2
> > > > > ovirt-engine-3.3.1)
> > > > > >- Check merged to previous::IGNORE, Not in stable branch
> > > > > >(['ovirt-engine-3.6', 'ovirt-engine-3.6.0',
> 'ovirt-engine-3.5',
> > > > > >'ovirt-engine-3.4', 'ovirt-engine-3.3', 'ovirt-engine-3.5.2',
> > > > > >'ovirt-engine-3.4.0', 'ovirt-engine-3.3.4',
> 'ovirt-engine-3.3.3',
> > > > > >'ovirt-engine-3.3.2', 'ovirt-engine-3.3.1'])
> > > > >
> > > > > > ___
> > > > > > Infra mailing list
> > > > > > Infra@ovirt.org
> > > > > > http://lists.ovirt.org/mailman/listinfo/infra
> > > > >
> > > > >
> > > > > --
> > > > > David Caro
> > > > >
> > > > > Red Hat S.L.
> > > > > Continuous Integration Engineer - EMEA ENG Virtualization R
> > > > >
> > > > > Tel.: +420 532 294 605
> > > > > Email: dc...@redhat.com
> > > > > IRC: dcaro|dcaroest@{freenode|oftc|redhat}
> > > > > Web: www.redhat.com
> > > > > RHT Global #: 82-62605
> > > > >
> > >
> > > --
> > > David Caro
> > >
> > > Red Hat S.L.
> > > Continuous Integration Engineer - EMEA ENG Virtualization R
> > >
> > > Tel.: +420 532 294 605
> > > Email: dc...@redhat.com
> > > IRC: dcaro|dcaroest@{freenode|oftc|redhat}
> > > Web: www.redhat.com
> > > RHT Global #: 82-62605
> > >
>
> --
> David Caro
>
> Red Hat S.L.
> Continuous Integration Engineer - EMEA ENG Virtualization R
>
> Tel.: +420 532 294 605
> Email: dc...@redhat.com
> IRC: dcaro|dcaroest@{freenode|oftc|redhat}
> Web: www.redhat.com
> RHT Global #: 82-62605
>
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>


-- 
Eyal Edri
Supervisor, RHEV CI
EMEA ENG Virtualization R
Red Hat Israel

phone:

3.6.1 branch is not treated as a stable branch, no CI as well

2015-12-01 Thread Tal Nisan 
The 3.6.1 branch is not treated by the hooks as a stable branch [1]
Aside for that, CI is not running on new patches there

[1]

   - Check TM::SKIP, not in a monitored branch (ovirt-engine-3.6
   ovirt-engine-3.6.0 ovirt-engine-3.5 ovirt-engine-3.4 ovirt-engine-3.3
   engine_3.2 engine_3.1 ovirt-engine-3.5.2 ovirt-engine-3.4.0
   ovirt-engine-3.3.4 ovirt-engine-3.3.3 ovirt-engine-3.3.2 ovirt-engine-3.3.1)
   - Check merged to previous::IGNORE, Not in stable branch
   (['ovirt-engine-3.6', 'ovirt-engine-3.6.0', 'ovirt-engine-3.5',
   'ovirt-engine-3.4', 'ovirt-engine-3.3', 'ovirt-engine-3.5.2',
   'ovirt-engine-3.4.0', 'ovirt-engine-3.3.4', 'ovirt-engine-3.3.3',
   'ovirt-engine-3.3.2', 'ovirt-engine-3.3.1'])
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra