[oVirt Jenkins] standard-enqueue - Build #6956 - FAILURE!
------=_Part_304_831800607.1510762884944 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/standard-enqueue/6956/ Build Name: #6956 Build Description: Gerrit: 82230 - mom (3.6, 4.0, 4.1, master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/82230 - title: Use ping2 RPC method to test connection - project: mom - branch: master - author: Andrej Krejcir <akrejcir@redhat.com> ------=_Part_304_831800607.1510762884944--
Hi Martin, Andrej, Do you guys still need the 3.6 and 4.0 build jobs, given that there not going to be any more 4.0 and 3.6 oVirt releases? Since the jobs exists, the system is trying to release their results into those no-longer existing releases. This results in messages like the forwarded one spamming our infra list. Could you remove that jobs building for obsolete oVirt versions? Thanks, Barak. On 15 November 2017 at 18:21, <jenkins@jenkins.phx.ovirt.org> wrote:
Build: http://jenkins.ovirt.org/job/standard-enqueue/6956/ Build Name: #6956 Build Description: Gerrit: 82230 - mom (3.6, 4.0, 4.1, master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/82230 - title: Use ping2 RPC method to test connection - project: mom - branch: master - author: Andrej Krejcir <akrejcir@redhat.com> _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
We do not really need them. Where do you disable them? Is removing automation files enough or do we have to post a change to the special repo with all the YAMLs? Martin On Wed, Nov 15, 2017 at 5:49 PM, Barak Korren <bkorren@redhat.com> wrote:
Hi Martin, Andrej,
Do you guys still need the 3.6 and 4.0 build jobs, given that there not going to be any more 4.0 and 3.6 oVirt releases?
Since the jobs exists, the system is trying to release their results into those no-longer existing releases. This results in messages like the forwarded one spamming our infra list.
Could you remove that jobs building for obsolete oVirt versions?
Thanks, Barak.
On 15 November 2017 at 18:21, <jenkins@jenkins.phx.ovirt.org> wrote:
Build: http://jenkins.ovirt.org/job/standard-enqueue/6956/ Build Name: #6956 Build Description: Gerrit: 82230 - mom (3.6, 4.0, 4.1, master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/82230 - title: Use ping2 RPC method to test connection - project: mom - branch: master - author: Andrej Krejcir <akrejcir@redhat.com> _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
On 16 November 2017 at 10:24, Martin Sivak <msivak@redhat.com> wrote:
We do not really need them. Where do you disable them? Is removing automation files enough or do we have to post a change to the special repo with all the YAMLs?
I'm afraid you have to do this by changing YAML in the 'jenkins' repo for now. Removing the automation files will just cause the jobs to vote -1 for "file not found" errors... Let me know if you need my help to do this. -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
participants (3)
-
Barak Korren -
jenkins＠jenkins.phx.ovirt.org -
Martin Sivak