Do the CI support creating a github releases + assets?

I'm currently rolling my own makefile to create a release, with a binary file as assets. Does standard CI have something to publish artifacts in GH releases? ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 87544, 1 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-4.2" change queue including change 87544,1 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87459,1 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures.

[CQ]: 87466, 3 (ovirt-provider-ovn) failed "ovirt-4.2" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-4.2" change queue including change 87466,3 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 87418,2 (ovirt-provider-ovn) that this change depends on or is based on, was detected as the cause of the testing

[JIRA] (OVIRT-1895) CI votes not forwarded on commit message change

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=35821#comment-35821 ] Daniel Belenky commented on OVIRT-1895: --- It's a known bug that's coming from the Gerrit Trigger Plugin,

[oVirt Jenkins] ovirt-node-ng_ovirt-4.2-pre_build-artifacts-el7-x86_64 - Build # 221 - Fixed!

Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2-pre_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2-pre_build-artifacts-el7-x86_64/221/ Build Number: 221 Build Status: Fixed Triggered By: Started by timer

[JIRA] (OVIRT-1895) CI votes not forwarded on commit message change

Yedidyah Bar David created OVIRT-1895: - Summary: CI votes not forwarded on commit message change Key: OVIRT-1895 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1895 Project: oVirt -

[CQ]: 87517,1 (ovirt-dwh) failed "ovirt-4.2" system tests

Change 87517,1 (ovirt-dwh) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the

[CQ]: 87509, 3 (ovirt-engine-metrics) failed "ovirt-4.2" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-4.2" change queue including change 87509,3 (ovirt-engine-metrics) failed. However, this change seems not to be the root cause for this failure. Change 87454,1 (ovirt-engine-metrics) that this change depends on or is based on, was detected as the cause of the

[CQ]: 42386f6 (ovirt-ansible-cluster-upgrade) failed "ovirt-4.2" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-4.2" change queue including change 42386f6 (ovirt-ansible-cluster-upgrade) failed. However, this change seems not to be the root cause for this failure. Change a11d8a2 (ovirt-ansible-cluster-upgrade) that this change depends on or is based on, was detected as

[CQ]: 87489,7 (ovirt-engine-metrics) failed "ovirt-4.2" system tests

Change 87489,7 (ovirt-engine-metrics) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details

[CQ]: 87284, 1 (ovirt-engine-api-model) failed "ovirt-4.2" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-4.2" change queue including change 87284,1 (ovirt-engine-api-model) failed. However, this change seems not to be the root cause for this failure. Change 86692,1 (ovirt-engine-api-model) that this change depends on or is based on, was detected as the cause of the

[CQ]: 87489, 7 (ovirt-engine-metrics) failed "ovirt-master" system tests

Change 87489,7 (ovirt-engine-metrics) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further

[CQ]: 87289, 1 (ovirt-engine-api-model) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 87289,1 (ovirt-engine-api-model) failed. However, this change seems not to be the root cause for this failure. Change 86700,9 (ovirt-engine-api-model) that this change depends on or is based on, was detected as the cause of

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 191 - Fixed!

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/191/ Build Number: 191 Build Status: Fixed Triggered By: Started by timer - Changes Since Last

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #1196

See -- Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace

[JIRA] (OVIRT-1895) CI votes not forwarded on commit message change

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-1895: Epic Link: OVIRT-400 > CI votes not forwarded on commit message change >

[JIRA] (OVIRT-1895) CI votes not forwarded on commit message change

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-1895: Resolution: Duplicate Status: Done (was: To Do) > CI votes not forwarded on commit

[JIRA] (OVIRT-1895) CI votes not forwarded on commit message change

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-1895: Component/s: Gerrit/git Epic Link: OVIRT-400 Issue Type: Bug (was: By-EMAIL) > CI

[JIRA] (OVIRT-1895) CI votes not forwarded on commit message change

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=35824#comment-35824 ] Barak Korren commented on OVIRT-1895: - [~d...@redhat.com] this had been reported many times in the past

Re: Do the CI support creating a github releases + assets?

On 13 February 2018 at 11:59, Roy Golan wrote: > I'm currently rolling my own makefile to create a release, with a binary > file as assets. > Does standard CI have something to publish artifacts in GH releases? > We don't have built-in support for it (And probably never will,

Jenkins build is back to normal : system-sync_mirrors-epel-el6-x86_64 #1197

See ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra