[ https://ovirt-jira.atlassian.net/browse/OVIRT-904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24160#comment-24160 ] Greg Sheremeta commented on OVIRT-904: -------------------------------------- [~bkorren@redhat.com]
are you doing that manually
Yes, completely manual
I'm not sure oVirt's own infra would be the best place, because Patternfly is not strictly an oVirt project.
True. However, we've talked about renaming the rpm to 'ovirt-patternflyX' to reflect the fact that it's only used by us. In that case, it might make sense to move it to our infra.
False CI-1 due to unreachable copr-be.cloud.fedoraproject.org -------------------------------------------------------------
Key: OVIRT-904 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-904 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: danken Assignee: infra
Many patches on https://gerrit.ovirt.org/#/q/topic:passthroughMigration fail CI due to failure: repodata/repomd.xml from patternfly: [Errno 256] No more mirrors to try. http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-7...: [Errno 14] curl#7 - "Failed connect to copr-be.cloud.fedoraproject.org:80; No route to host" http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-7...
-- This message was sent by Atlassian JIRA (v1000.620.0#100023)