Publishers were updated with a new jobs. - Kiril ----- Original Message -----
From: "Martin Sivak" <msivak@redhat.com> To: "Kiril Nesenko" <knesenko@redhat.com> Cc: infra@ovirt.org Sent: Tuesday, March 4, 2014 5:00:53 PM Subject: Re: Jenkins job for ovirt-scheduler-proxy releases
Hi,
Where are the links to your jobs ? I only provided the names in the email, the links are here:
http://jenkins.ovirt.org/user/msivak/my-views/view/All/job/ovirt-scheduler-p... http://jenkins.ovirt.org/user/msivak/my-views/view/All/job/ovirt-scheduler-p...
-- Martin Sivák msivak@redhat.com Red Hat Czech RHEV-M SLA / Brno, CZ
----- Original Message -----
Where are the links to your jobs ?
- Kiril
----- Original Message -----
From: "Martin Sivak" <msivak@redhat.com> To: infra@ovirt.org Cc: "Kiril Nesenko" <knesenko@redhat.com> Sent: Tuesday, March 4, 2014 4:23:36 PM Subject: Jenkins job for ovirt-scheduler-proxy releases
Hi,
dcaro helped me to create automatic Jenkins job for ovirt-3.3 and 3.4 releases of ovirt-scheduler-proxy packages.
Those are created using ovirt-scheduler-proxy_3.3_create_rpm and ovirt-scheduler-proxy_3.4_create_rpm job names directly from the respective git branches.
I would like to include them into the following collecting jobs so the artifacts are published automatically after we push and tag them in the branches.
- http://jenkins.ovirt.org/job/publish_ovirt_rpms_nightly_3.3/ - http://jenkins.ovirt.org/job/publish_ovirt_rpms_nightly_3.4/
So you think it would be possible to automatize it like that?
-- Martin Sivák msivak@redhat.com Red Hat Czech RHEV-M SLA / Brno, CZ