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&D

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