Repositories for oVirt Node Automated Testing
--=-HM/jIZRuDzn6poEp/ELo Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hey, I'm working on bringing automated testing to oVirt Node. The current code is hosted at [1], but it would be nice if I could host at least the ovirt specific client and the ovirt specififc testsuites on the ovirt infrastructure. Is there anything specififc for me to do, besides asking for these repos? Greetings fabian -- [1] https://gitorious.org/ovirt/ --=-HM/jIZRuDzn6poEp/ELo Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAABAgAGBQJP40D3AAoJEC9+uOgSHVGUp3AP/1uok4aur6bwbffzfwcp13Bc ZuxqGKkiBAtJwyvAJp9Le4q4270pczhgDewqht8rEdCLqta7FL2fHVY2kfPZ65Uw xFEuyrbUOg1WXjos3aQhhemOuH3gXMppvzNJ+7OM+MryBLaFdkI19vD+HENy8Zw3 cRNud1bs1X2eiPAGbOtdayVsilO3IsGB1yY6pePHBIv6rwZR/GYZJgllG+lFpApX rMXoqi6epvYn+5cKsAetM6EtVZxI06klHouxyPUcO1ScvrNTSwrMiFB1Z7wBoYcW AOro9sSxnZFzaIdKvwZIS34qdGlZrkBmM4QQJwV0zjHb9cl1i/+1e0AtYQNnCXzJ jWhukG3KBKZqh4ypkQlllJ1PpPbwWQwQla40kl6+4hme2IQTfrWJ2CuddJePeTbZ JBjRDr1kfWvGIHH6mkNloOQrrlM526T4rBKl4OUvJ7m8/9Px+42i6tUiXPE84vVD u+QKUNFoxybS3m+Z5tbZNUkkkNKJvNyEX6+8wyWwyrwllwLgRHVbw5Q2EUHBVDma ELy9eRGnXEDdRrO2VL0XcLFSUbtfN6l/BgAjmlYnqbhZxTs7Pa3adrXuhbimJ+FA GY1124DOK6uM9mP00H11eP0A/A2aG7+p9wfpB+tr6LjKJ0l3exzPU0Mu/mzU876i +TV/uL8Wm85RHWJpPamT =EwVV -----END PGP SIGNATURE----- --=-HM/jIZRuDzn6poEp/ELo--
----- Original Message -----
From: "Fabian Deutsch" <fabiand@redhat.com> To: infra@ovirt.org Sent: Thursday, June 21, 2012 6:42:46 PM Subject: Repositories for oVirt Node Automated Testing
Hey,
I'm working on bringing automated testing to oVirt Node.
The current code is hosted at [1], but it would be nice if I could host at least the ovirt specific client and the ovirt specififc testsuites on the ovirt infrastructure.
Is there anything specififc for me to do, besides asking for these repos?
I assume we need a git repo for all automated testing in jenkins. i suggest creating one repo 'jenkins' with subdirs for each project (i.e ovirt-engine,ovirt-node,etc... ). another option is to have a separate branch for each project.. thoughts? e.
Greetings fabian
-- [1] https://gitorious.org/ovirt/
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
--=-BOYpKdMNZu9vIFYoQl8I Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Am Donnerstag, den 21.06.2012, 11:46 -0400 schrieb Eyal Edri:
From: "Fabian Deutsch" <fabiand@redhat.com> To: infra@ovirt.org Sent: Thursday, June 21, 2012 6:42:46 PM Subject: Repositories for oVirt Node Automated Testing =20 Hey, =20 I'm working on bringing automated testing to oVirt Node. =20 The current code is hosted at [1], but it would be nice if I could host at least the ovirt specific client and the ovirt specififc testsuites on the ovirt infrastructure. =20 Is there anything specififc for me to do, besides asking for these repos? =20 I assume we need a git repo for all automated testing in jenkins. =20 i suggest creating one repo 'jenkins' with subdirs for each project (i.e = ovirt-engine,ovirt-node,etc... ). another option is to have a separate branch for each project..=20 =20
=20 ----- Original Message ----- thoughts?=20
I'd be happy with the one-subdir-per-subproject approach, but I wouldn't go with the branch solution. Greetings fabian --=-BOYpKdMNZu9vIFYoQl8I Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAABAgAGBQJP40H6AAoJEC9+uOgSHVGUYawP/iWGi9tg4EBqJOLf3kOGKlmi ck4iNcau8ntMpZqarUzIEdo8VrVWD30olgSSG1qA5B6KWDTOPgfBoJKEz0m8MGaM 9cu0aj2x8SU7pEsErRMF6AsE8z/QY3bZyc21gfUO3+4+vB5OtiL8BnX8lYcU2z1n Yw22nyyeEjrixn6yMNUKN1bOxXyfrXMMRFli6aDhjWSHNzbMFEboZ17OAbUZ92XW GnXzVElCc4YreJGi+zR/JD8BKtMEx0qcKb6miDK0i6woAwWSPBr1c4CR77jYUGCI Opzmh7D45ClaCC4/qb7HeTAD3LjIb6P5A6B+6uNjn8md4NbZrmMgi0Ni7Lf+lpeV OW+1OMoNGlupGeVQtd72Jp1lckJtywaQeWqsCh45buDvjZ0TWr9pvhigrj9NcSxD 9+qY9rcQXpPlOypZ6vcPRl4A9V4fRdFsifIoUixDZpyqcx1ynykmTz2V1xB1pvfe LL3D4LMu8Idv7DLcU4JZqbg4ZLaEl/0WKmWq5oFczHfpkf6BBlrTHYpsPWpCLx// J9WTVVzqMRMDfCGBGFgRVyxLmqRXAIr6ePDWf/Jpc+GSGhZsshHa1NVNLhD0Ol0R Qixf4REiPbSv7A657rJkxrjmlI5WhCiR3NDLNrfJ+ECXHNPWhzRo/NeFt/LxjHKH pJchC8X2ZWc+pWRB6MY2 =gt6w -----END PGP SIGNATURE----- --=-BOYpKdMNZu9vIFYoQl8I--
On Thu, 2012-06-21 at 17:47 +0200, Fabian Deutsch wrote:
Am Donnerstag, den 21.06.2012, 11:46 -0400 schrieb Eyal Edri:
----- Original Message -----
From: "Fabian Deutsch" <fabiand@redhat.com> To: infra@ovirt.org Sent: Thursday, June 21, 2012 6:42:46 PM Subject: Repositories for oVirt Node Automated Testing
Hey,
I'm working on bringing automated testing to oVirt Node.
The current code is hosted at [1], but it would be nice if I could host at least the ovirt specific client and the ovirt specififc testsuites on the ovirt infrastructure.
Is there anything specififc for me to do, besides asking for these repos?
I assume we need a git repo for all automated testing in jenkins.
i suggest creating one repo 'jenkins' with subdirs for each project (i.e ovirt-engine,ovirt-node,etc... ). another option is to have a separate branch for each project..
thoughts?
I'd be happy with the one-subdir-per-subproject approach, but I wouldn't go with the branch solution.
Problem with having 1 repo for all projects is ownership. Who can commit changes to the repo. Do we have a long list of committers? Do we have a limited list? Also, there is the fact that I might be testing only engine and don't want anything from node or vdsm. We already have a ovirt-engine-sdk-tests repo. I think we should continue along those lines with a separate ovirt-node-tests repo, vdsm-tests repo, etc... Mike
Greetings fabian _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Is it going to be managed though gerrit? Or are you looking for something simpler? If simpler the maybe gitolite is an good choice? I use it in my day job. From what I have read there is no option other then a custom hook to limit write access to folders a git limitation not gitolite limitation but you can limit it by branches. Thanks Robert On 06/21/2012 12:08 PM, Mike Burns wrote:
Am Donnerstag, den 21.06.2012, 11:46 -0400 schrieb Eyal Edri:
----- Original Message -----
From: "Fabian Deutsch"<fabiand@redhat.com> To: infra@ovirt.org Sent: Thursday, June 21, 2012 6:42:46 PM Subject: Repositories for oVirt Node Automated Testing
Hey,
I'm working on bringing automated testing to oVirt Node.
The current code is hosted at [1], but it would be nice if I could host at least the ovirt specific client and the ovirt specififc testsuites on the ovirt infrastructure.
Is there anything specififc for me to do, besides asking for these repos? I assume we need a git repo for all automated testing in jenkins.
i suggest creating one repo 'jenkins' with subdirs for each project (i.e ovirt-engine,ovirt-node,etc... ). another option is to have a separate branch for each project..
thoughts? I'd be happy with the one-subdir-per-subproject approach, but I wouldn't go with the branch solution. Problem with having 1 repo for all projects is ownership. Who can commit changes to the repo. Do we have a long list of committers? Do we have a limited list? Also, there is the fact that I might be testing only engine and don't want anything from node or vdsm. We already have a ovirt-engine-sdk-tests repo. I think we should continue along those
On Thu, 2012-06-21 at 17:47 +0200, Fabian Deutsch wrote: lines with a separate ovirt-node-tests repo, vdsm-tests repo, etc...
Mike
Greetings fabian _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
On Thu, 2012-06-21 at 12:32 -0400, Robert Middleswarth wrote:
Is it going to be managed though gerrit? Or are you looking for something simpler? If simpler the maybe gitolite is an good choice? I use it in my day job. From what I have read there is no option other then a custom hook to limit write access to folders a git limitation not gitolite limitation but you can limit it by branches.
Most likely through gerrit. And the gerrit interface does support restrictions based on branch, though I don't like the branch-by-branch approach. I'd still prefer separate repos for separate projects. Mike
Thanks Robert
On 06/21/2012 12:08 PM, Mike Burns wrote:
Am Donnerstag, den 21.06.2012, 11:46 -0400 schrieb Eyal Edri:
----- Original Message -----
From: "Fabian Deutsch"<fabiand@redhat.com> To: infra@ovirt.org Sent: Thursday, June 21, 2012 6:42:46 PM Subject: Repositories for oVirt Node Automated Testing
Hey,
I'm working on bringing automated testing to oVirt Node.
The current code is hosted at [1], but it would be nice if I could host at least the ovirt specific client and the ovirt specififc testsuites on the ovirt infrastructure.
Is there anything specififc for me to do, besides asking for these repos? I assume we need a git repo for all automated testing in jenkins.
i suggest creating one repo 'jenkins' with subdirs for each project (i.e ovirt-engine,ovirt-node,etc... ). another option is to have a separate branch for each project..
thoughts? I'd be happy with the one-subdir-per-subproject approach, but I wouldn't go with the branch solution. Problem with having 1 repo for all projects is ownership. Who can commit changes to the repo. Do we have a long list of committers? Do we have a limited list? Also, there is the fact that I might be testing only engine and don't want anything from node or vdsm. We already have a ovirt-engine-sdk-tests repo. I think we should continue along those
On Thu, 2012-06-21 at 17:47 +0200, Fabian Deutsch wrote: lines with a separate ovirt-node-tests repo, vdsm-tests repo, etc...
Mike
Greetings fabian _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
On 06/21/2012 08:24 PM, Mike Burns wrote:
On Thu, 2012-06-21 at 12:32 -0400, Robert Middleswarth wrote:
Is it going to be managed though gerrit? Or are you looking for something simpler? If simpler the maybe gitolite is an good choice? I use it in my day job. From what I have read there is no option other then a custom hook to limit write access to folders a git limitation not gitolite limitation but you can limit it by branches.
Most likely through gerrit. And the gerrit interface does support restrictions based on branch, though I don't like the branch-by-branch approach. I'd still prefer separate repos for separate projects.
Mike
Thanks Robert
On 06/21/2012 12:08 PM, Mike Burns wrote:
Am Donnerstag, den 21.06.2012, 11:46 -0400 schrieb Eyal Edri:
----- Original Message -----
From: "Fabian Deutsch"<fabiand@redhat.com> To: infra@ovirt.org Sent: Thursday, June 21, 2012 6:42:46 PM Subject: Repositories for oVirt Node Automated Testing
Hey,
I'm working on bringing automated testing to oVirt Node.
The current code is hosted at [1], but it would be nice if I could host at least the ovirt specific client and the ovirt specififc testsuites on the ovirt infrastructure.
Is there anything specififc for me to do, besides asking for these repos? I assume we need a git repo for all automated testing in jenkins.
i suggest creating one repo 'jenkins' with subdirs for each project (i.e ovirt-engine,ovirt-node,etc... ). another option is to have a separate branch for each project..
thoughts? I'd be happy with the one-subdir-per-subproject approach, but I wouldn't go with the branch solution. Problem with having 1 repo for all projects is ownership. Who can commit changes to the repo. Do we have a long list of committers? Do we have a limited list? Also, there is the fact that I might be testing only engine and don't want anything from node or vdsm. We already have a ovirt-engine-sdk-tests repo. I think we should continue along those
On Thu, 2012-06-21 at 17:47 +0200, Fabian Deutsch wrote: lines with a separate ovirt-node-tests repo, vdsm-tests repo, etc...
+1 to using gerrit +1 to repo by project unless any objections, I'll create this repo next week for fabian as a sub repo as part of the ovirt node project
--=-n2aZDN8SnOOw4Q/stNAS Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Am Donnerstag, den 21.06.2012, 21:23 +0300 schrieb Itamar Heim:
unless any objections, I'll create this repo next week for fabian as a=20 sub repo as part of the ovirt node project=20
Hey, did you already find some time to create the repo? Greetings fabian --=-n2aZDN8SnOOw4Q/stNAS Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAABAgAGBQJP8vQOAAoJEC9+uOgSHVGUSVwP/11RAm08t1PFDbi5IFJ3wIN4 C2KLFLtQWRVLV7I9ahDRli2H2Tv4dzX/cNYQ3+pmL01r1tMSXJvMuCZLM9elgKRf ajP/x51+sVHzhRxjIgctOX5B0GKtBv8DNl4zyzatO9YwOIAqQbfuYobRjIsKoXyE fwD17NsJs23VjWhzlwUjInlSZkaU1sieq/ra+tYfQkTLnnyhN5pUPqMoBPYJfzNw +UkDsyohCHVLff5igdq+rwgbfDIX6XI/Os5VPT5QQ+caqRKOhfBFEGTRxQiDD5ij AYoIw94E/uyT8/g0+HQVQ4nsyx5iqMA2+nvAg1rUdSO4srbd0SNglRs40q4bw82/ dLht0fhEjM5g2DrSs+XdRWuFiaj9S+4PfxYkKZCYK137wn/fR1ZpWOdgfpTAfyVL 4819LgCftOs6yDyFoL1/runpLyc9fjFJEVnE7w0cIJN8ETfjVYg7yFUZGzdw/8pc Tz+Zk7Rf2Sady54yhUa9U8t14ap9kJX5qLakM1X1lCAItaRjvOiDbZUwFjp7fbZM 1UTHjIgdF0swO9RLrcjJiT03O+51GTJrqENJ2OwhctWhsw6gRKv5bKbrHj1sO9rU jlxWsEMAG9OCxMq2J1y09McVLRGSQzQ5/FKRMXowmDquMpPpLoAJkyJ4f50l9YYC /JbTUes+mAhEQFIcOw8b =Pxdn -----END PGP SIGNATURE----- --=-n2aZDN8SnOOw4Q/stNAS--
On Tue, 2012-07-03 at 15:30 +0200, Fabian Deutsch wrote:
Am Donnerstag, den 21.06.2012, 21:23 +0300 schrieb Itamar Heim:
unless any objections, I'll create this repo next week for fabian as a sub repo as part of the ovirt node project
Hey,
did you already find some time to create the repo?
Oops, I think I was supposed to remind Itamar to create it, but I forgot to have someone remind me to remind Itamar.... Mike
Greetings fabian _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
On 07/03/2012 04:40 PM, Mike Burns wrote:
On Tue, 2012-07-03 at 15:30 +0200, Fabian Deutsch wrote:
Am Donnerstag, den 21.06.2012, 21:23 +0300 schrieb Itamar Heim:
unless any objections, I'll create this repo next week for fabian as a sub repo as part of the ovirt node project
Hey,
did you already find some time to create the repo?
Oops, I think I was supposed to remind Itamar to create it, but I forgot to have someone remind me to remind Itamar....
ovirt-node-tests it inherits the permissions from ovirt-node, so same set of permissions/maintainers for both.
Mike
Greetings fabian _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
--=-DknQiQc6DUOYFTrNt1kd Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Am Dienstag, den 03.07.2012, 17:15 +0300 schrieb Itamar Heim:
On 07/03/2012 04:40 PM, Mike Burns wrote:
On Tue, 2012-07-03 at 15:30 +0200, Fabian Deutsch wrote:
Am Donnerstag, den 21.06.2012, 21:23 +0300 schrieb Itamar Heim:
unless any objections, I'll create this repo next week for fabian as a sub repo as part of the ovirt node project
Hey,
did you already find some time to create the repo?
Oops, I think I was supposed to remind Itamar to create it, but I forgo= t to have someone remind me to remind Itamar....
=20 ovirt-node-tests it inherits the permissions from ovirt-node, so same set of=20 permissions/maintainers for both.
thanks - fabian --=-DknQiQc6DUOYFTrNt1kd Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAABAgAGBQJP8v7eAAoJEC9+uOgSHVGUUeYQAKdBEfEWH1pywTiPoLlhlPoc JmTWHI83B+TLZWNke48zLZfXUckusDG8i6+rmp1605l5+32E6FGDplfkyack0dau RSyA4iVGw2CcjSF8von1kSd8VyGQoda9CLt0MGHBLzlY9NNqV/bK4Qdx8Zq7PKeD NL8aCNtzMenKrbOHEGQsMbuCvXDwGJDjbN6O330Qr9Fsqva50hcm+Zij1N5jAkr2 rcl8o9bF755MsfMmtqO1tviVjGbWaWrGuFeY2L0Y5W43BCCQjVfjzT/dlBbJOAHy 3RBq/J+XbpkL89i1dFVPdBCN+GNsyDBPPRA2f/gdroi8vHmEgckb7O2ieZF2eUQt TOV3NvT7PPzPyYFj3WlVMCS1ocMUarfzLCb6Xs8HNLjLLpTsFapVBHopXMmwRTJb AHUN2qOa2N6zNkxoI3YyQJu+oXUqQNhW554QwocKTrbzDzvdDfMtNUdm4sPvzkyK jCnB6uwM5gfso7DjJIqlz3alSEpTnQvaIencGxOVdAmw7WtcCOjGR0r7MjUmPEx/ nFGcDUBm7B+Agmy8TYlfdbIpDWOUAL68hoPILabLNVKhnqcBTH+ObvFXIYHXhls/ 12DZWQymrp9W2UuS29OZ661C3WMhWDWuvWzDpm2SB9oS+z9kqTqJZuyPIn90z+6f 1B8XxlMB20WCTbWkjo// =9uPA -----END PGP SIGNATURE----- --=-DknQiQc6DUOYFTrNt1kd--
participants (5)
-
Eyal Edri -
Fabian Deutsch -
Itamar Heim -
Mike Burns -
Robert Middleswarth