lol

yeah, it's working using Standard CI now. https://gerrit.ovirt.org/#/c/71135/ Hopefully I can get it merged soon. had one comment on the patch so far, about the version/release getting bumped on every build for repo purposes. No other comments yet.

I think you need to be the one answering this question, not asking it...

once your new patches are merged, will we get patternfly from oVirt repos instead of copr?

NP, I'm just concerned if CI will keep failing because the copr repo isn't reliable.
If thats not an issue then we can wait for 4.2.

Also, if you are building it, we can add it to standard CI, and built it automatically.

We can move it.

How about we move it to ovirt's infra when we upgrade to patternfly3, which will happen for oVirt 4.2? I can name the rpm "ovirt-patternfly3". I'll need some help figuring out how to put it in the ovirt static repo.

What was the decision?
Can you move the patternfly to ovirt static repo?

> 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.

are you doing that manually, or do you have some automation built around it?

I'm not sure oVirt's own infra would be the best place, because Patternfly is not strictly an oVirt project.
Perhaps make travis run the build in Copr, and then take the result and push it to GitHub's artifact storage?
Another possibility is to use BinTray

We might eventually mirror this in oVirt infra to make CI resilient to changes there (see )

I maintain patternfly on copr. No one else uses it, so we can move it anywhere that makes sense.

is it possible to get pattenfly from other place than Copr?
We're seeing more and more failures on repos hosted by copr, we might want to find a more stable repo on other services.
Who is building/maintaining those builds?

Which projects are coming from Copr? Maybe they would like us to host their artifacts on resources.ovirt.org (And would happily make their CI systems update it with new builds)? Or perhaps they would push into Fedora? or EPEL? or CentOS? Or even just GitHub?

I guess if we setup out own mirrors for stuff it will solve our problems, but a project that only releases on copr has a problem IMO....