3.6.1 branch is not treated as a stable branch, no CI as well
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'])
--2qXFWqzzG3v1+95a Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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=3Djenkins.git;a=3Dblob;f=3Djobs/confs/p= rojects/vdsm/vdsm_standard.yaml;hb=3Drefs/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 =20 [1] =20 - 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
--=20 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 --2qXFWqzzG3v1+95a Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJWXdehAAoJEEBxx+HSYmnDuGgH/3mjCym9zo0iR3X+A2qgHqLt lGG+850LY9vLSPHRVHFPG1GsHKSwWoG7vW4sg6a370RXOMwRDDDv7VJI15FCTDt+ 9U3kqnrkQh7CLaZIT28c5MyaG48rJcI8gIyXLVkxKsHc4eskNVLrUXiYqwD3wgw9 cHJlobaZ6cQnU1UvPmrEzc/i9drzyBthHMN6bGwcIBK5Oe4prN2wOJmPpXsEHFQB iSuzUryaKMbgP1USuv+3DcWo+ez+tEzpfF3JviUsGqmnoU1ajZaJbdcQ77FelNyG UOFykppUbJ5RYBqKyteUxRoZTZNsFBpCrADKOy17HXmLjtkdeGcaVwBIb37yShE= =Pp9B -----END PGP SIGNATURE----- --2qXFWqzzG3v1+95a--
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 <dcaro@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/v...
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
--5CUMAwwhRxlRszMD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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?
=20 On Tue, Dec 1, 2015 at 7:23 PM, David Caro <dcaro@redhat.com> wrote: =20
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=3Djenkins.git;a=3Dblob;f=3Djobs/confs=
/projects/vdsm/vdsm_standard.yaml;hb=3Drefs/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
--=20 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 --5CUMAwwhRxlRszMD Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJWXdlEAAoJEEBxx+HSYmnDA5EH/REzZiduqvPPkWgqFiYseJ4X 5WeUorY7sxpdOE2yC5+IMeIaIUcbAw5Usl3UIWADLaBPctrzOxjty5Y9LZfEqYzy y+rTO0MCxrZ0+v/7C+UrBepk3kqzIaksDyshYVUuuhjuHBYq6IiTxFyGVaq32et0 Y3bg3nbB6YcQETRs4kuxgCJb55aIh5FSyz8Q+08nM+kZ8IopR54RvS7YUQNazc9L eoNsLVSFGwVe/xjEfPgF5ugBbvUQ8Hlzm8dvNNipIXUplLeBc6jyhybgCu7bZULe H5gVD/K3wfWLqQQ6Lqh/0/X+0Q2/kSPpnYzT6eNNnWOTJWYvvnZ81F6wQFi1qrk= =5ZAU -----END PGP SIGNATURE----- --5CUMAwwhRxlRszMD--
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@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@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/v...
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
-- 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
--5L6AZ1aJH5mDrqCQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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)
=20 On Tue, Dec 1, 2015 at 7:30 PM, David Caro <dcaro@redhat.com> wrote: =20
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 k= now 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@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 proj=
ect
yaml:
https://gerrit.ovirt.org/gitweb?p=3Djenkins.git;a=3Dblob;f=3Djobs/confs= /projects/vdsm/vdsm_standard.yaml;hb=3Drefs/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
-- 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
--=20 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 --5L6AZ1aJH5mDrqCQ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJWXdwCAAoJEEBxx+HSYmnDw6EH/0mYtklXp9RnT+7r6f1fEZ+r EBJ6HVrY1ffLKjj8VaW8l4Xdu1WnprpxZhT9xNyg0DUfcu/vU/XznTE6Qerulfzr wIMvh8B51ozvST+/IGler9Zm0iHQBaLvwE/2kea2yLw5ubYHg7nhTdflDpeCBEYA aN+Ti7rX8qpfBXUI9tKRjDsCovhKBKZ8Uu867qgiBUhHZ/Vob1HNBVbg6pmWsbmI yZWyC/tK2UPeVNRCWd6fWGLfM4S9YoOAJBnWHRV0mMw3bh3BG2rRpu7nig/3nqD4 eAPLPLIpMAMkObNNpakvZIr0AX2RNK+6PF8k4LX+2WYDaTciS1AmO8N/couqf94= =GZ02 -----END PGP SIGNATURE----- --5L6AZ1aJH5mDrqCQ--
On Tue, Dec 1, 2015 at 7:42 PM, David Caro <dcaro@redhat.com> 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 <dcaro@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
(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@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
hooks project
yaml:
https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=blob;f=jobs/confs/projects/v...
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
-- 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
-- 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
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- Eyal Edri Supervisor, RHEV CI EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)
On Tue, Dec 1, 2015 at 6:42 PM, David Caro <dcaro@redhat.com> 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 <dcaro@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
(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@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
hooks project
yaml:
https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=blob;f=jobs/confs/projects/v...
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
-- 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
-- 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
_______________________________________________ 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
On Tue, Dec 1, 2015 at 6:42 PM, David Caro <dcaro@redhat.com> wrote: =20
On 12/01 19:37, Tal Nisan wrote:
Well, if the integration team is OK with that then I guess it's up to=
--XuV1QlJbYrcVoo+x Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 12/02 13:35, Sandro Bonazzola wrote: the
branch owner indeed and as said it will be very helpful for the backp= ort 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 the= m)
=20 ack on my side
=20 =20 =20
On Tue, Dec 1, 2015 at 7:30 PM, David Caro <dcaro@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=
Added the 3.6.1 branch to the stable branches list, about the jobs, feel fr= ee to send a patch following the indications below (from my previous email) and I'll review+merge 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 shou= ld 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@redhat.com> wro=
te:
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=3Djenkins.git;a=3Dblob;f=3Djobs/confs= /projects/vdsm/vdsm_standard.yaml;hb=3Drefs/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 bran= ch [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
-- 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
-- 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
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
=20 =20 --=20 Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
--=20 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 --XuV1QlJbYrcVoo+x Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJWXujiAAoJEEBxx+HSYmnDXdoH/iIvovokhhIRgtXSGS8jM/kU 1ELwJHtorALrnGS4/PywlYcv/TrC53W5cSM58pRuv1X5TEcxVe7UjI/xmj93F1VJ i/9HHA1SdMyP7HliNR2XQfWvCV3brV/2ZG85Wl8+yxaHUKAWhm5N15QX/WUr9/Kt V3ZESZ9Otn2FjC7os4ZDGULwK555oR1mrKKPWpf9YkzfmefN45JJ0SZTr/ZlOI17 X5/vSdyY+jy53x78rIXGYGcE7IY22mZRk8W3gxSEWtdSO6ZEFspteSjS/aVd4Kjl 1AoiBtEc6M9fB5iAhk4bLMsW6s9mL0SH+KnvAw+teBMdE8M+sgCTVsrvPcbPLCI= =xqJL -----END PGP SIGNATURE----- --XuV1QlJbYrcVoo+x--
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 <dcaro@redhat.com> wrote:
On Tue, Dec 1, 2015 at 6:42 PM, David Caro <dcaro@redhat.com> 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
are monitoring the infra list though, you might ask on devel too (or cc
On 12/02 13:35, Sandro Bonazzola wrote: them 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 <dcaro@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@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/v...
> > 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 >
-- 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
-- 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
_______________________________________________ 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&D
Tel.: +420 532 294 605 Email: dcaro@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&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)
On Wed, Dec 2, 2015 at 2:00 PM, Eyal Edri <eedri@redhat.com> 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 <dcaro@redhat.com> wrote:
On Tue, Dec 1, 2015 at 6:42 PM, David Caro <dcaro@redhat.com> 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
are monitoring the infra list though, you might ask on devel too (or cc
On 12/02 13:35, Sandro Bonazzola wrote: them 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 <dcaro@redhat.com>
wrote:
On 12/01 19:25, Tal Nisan wrote: > Well, it's not my decision but of the integration team, for me
> 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@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
as the project
> > yaml: > > > > > >
https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=blob;f=jobs/confs/projects/v...
> > > > 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 > >
-- 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
-- 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
_______________________________________________ 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&D
Tel.: +420 532 294 605 Email: dcaro@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&D Red Hat Israel
phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
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 <sbonazzo@redhat.com> wrote:
On Wed, Dec 2, 2015 at 2:00 PM, Eyal Edri <eedri@redhat.com> 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 <dcaro@redhat.com> wrote:
On Tue, Dec 1, 2015 at 6:42 PM, David Caro <dcaro@redhat.com> 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
are monitoring the infra list though, you might ask on devel too (or cc
On 12/02 13:35, Sandro Bonazzola wrote: them 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 <dcaro@redhat.com>
wrote:
> On 12/01 19:25, Tal Nisan wrote: > > Well, it's not my decision but of the integration team, for me
> > 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@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
as the project
> > > yaml: > > > > > > > > > >
https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=blob;f=jobs/confs/projects/v...
> > > > > > 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 > > > > > -- > 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 >
-- 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
_______________________________________________ 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&D
Tel.: +420 532 294 605 Email: dcaro@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&D Red Hat Israel
phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
-- Eyal Edri Supervisor, RHEV CI EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)
participants (4)
-
David Caro -
Eyal Edri -
Sandro Bonazzola -
Tal Nisan