ovir-3.6 branch for vdsm-jsonrpc-java
I created new vdsm-jsonrpc-java branch for 3.6. Can someone please update jenkins 3.6 jobs to use new branch and apply verification rules for stable branches similar to ovirt-engine? Thanks, Piotr
--sU4rRG038CsJurvk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 02/02 15:17, Piotr Kliczewski wrote:
I created new vdsm-jsonrpc-java branch for 3.6. Can someone please update jenkins 3.6 jobs to use new branch and apply verification rules for stable branches similar to ovirt-engine?
I can guide you through it if you want, as a starter, take a look here: https://gerrit.ovirt.org/gitweb?p=3Djenkins.git;a=3Dblob;f=3Djobs/confs/pro= jects/vdsm-jsonrpc-java/vdsm-jsonrpc-java_standard.yaml;h=3D2fbf0698dc7045d= 790aabb5d5d5382077a69f47d;hb=3DHEAD there all you have to do is change the two line after 'version:' on line 18, so instead of using branch master for 3.6 version uses your new branch, if the tests have not changed it will use those automatically. If you also want to have jobs for master branch, you can also add to the same version dict the values: version: - 3.6: branch: ovirt-3.6 - master: branch: master That will create the jobs for master branch and version (called vdsm-jsonrpc-java_master_*). Ping me on irc if you have issues or it's not clear in any way and we'll do it together. Cheers!
=20 Thanks, Piotr _______________________________________________ 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 --sU4rRG038CsJurvk Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJWsMMuAAoJEEBxx+HSYmnD/tIIAI4b4yCm5sURJYZCXRYWxAri q2BNUWx329EHRhAmjl2InBY1dEsh++DvwJlUj3lYvc4oPCDYnOXhIaR1g9tFHqk4 8kepQ5sboFouv0tj3jl25/d1Cql+cFlY1ztWpCfFrVZrVeBiGQloFW5OvRznLdzI 3N754iZgMhsDeFV9IyBUAkvTu7Ncu6CglHeew7IfSCouPCbAtN0ZvebvBGtVu01D am7RAD18ajQpVT3dKQl5LlIcWRE/cv2jXooDLYTReeX1nrm4/vVk6A+ICS2SkqtV dTyAI0WQg9iUcghULRy2TFT8rqzhPVAW4FjFyNSPn1j/WrHxbzQeGtyzmy2KAHI= =40H9 -----END PGP SIGNATURE----- --sU4rRG038CsJurvk--
David, I will follow the guide and ask questions if any. Thanks, Piotr On Tue, Feb 2, 2016 at 3:54 PM, David Caro <dcaro@redhat.com> wrote:
On 02/02 15:17, Piotr Kliczewski wrote:
I created new vdsm-jsonrpc-java branch for 3.6. Can someone please update jenkins 3.6 jobs to use new branch and apply verification rules for stable branches similar to ovirt-engine?
I can guide you through it if you want, as a starter, take a look here:
https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=blob;f=jobs/confs/projects/v...
there all you have to do is change the two line after 'version:' on line 18, so instead of using branch master for 3.6 version uses your new branch, if the tests have not changed it will use those automatically.
If you also want to have jobs for master branch, you can also add to the same version dict the values:
version: - 3.6: branch: ovirt-3.6 - master: branch: master
That will create the jobs for master branch and version (called vdsm-jsonrpc-java_master_*).
Ping me on irc if you have issues or it's not clear in any way and we'll do it together.
Cheers!
Thanks, Piotr _______________________________________________ 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
participants (2)
-
David Caro -
Piotr Kliczewski