3.6.1 branch is not treated as a stable branch, no CI as well
Tal Nisan
tnisan at redhat.com
Tue Dec 1 17:37:20 UTC 2015
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 <dcaro at redhat.com> 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 <dcaro at redhat.com> 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 at 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 at 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&D
>
> Tel.: +420 532 294 605
> Email: dcaro at redhat.com
> IRC: dcaro|dcaroest@{freenode|oftc|redhat}
> Web: www.redhat.com
> RHT Global #: 82-62605
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/infra/attachments/20151201/020350c7/attachment.html>
More information about the Infra
mailing list