The ovirt-containers project is no longer maintained.

Is there such a project around? How do we find it?

Currently only KubeVirt might be a candidate, but this is why I think we should wait for @Fabian Deutsch to return from PTO and comment on it.

We don't want to support this use case just like we don't want to support nightly building of node or appliance. But its the closest we can get to the building via CQ as long as we don't finish implementing it.

We do it for node and appliance because those projects are required for oVirt, we can't say the same for ovirt-containers, which is dead AFAIK and we can't say if the same need for a similar project ( i.e one repo containing multiple projects ) will be required.

We should focus on finding a relevant project to test it on and not implement something we won't use, if we don't have it, we should either create a test project or wait for the oVirt/KubeVirt team to provide info on it.

Shouldn't 'build-artifacts.sh' do that after the recent work Daniel Belenky did? Doesn't it mean each build is already deployed to 'ovirtinfra' repo on dockerhub?

Just because build-artifacts can do something doesn't mean anything is using that capability. This ticket is essentially about adding a job that will utilize this capability in a relatively frequent manner.

we should just find a new project that should be built as a container and use it for testing.

Is there such a project around? How do we find it?

I just want to avoid us working on something that won't be used or needed, that's all.
And I believe supporting the use case of nightly build of a project like 'ovirt-containers' isn't needed, at least not as first priority.

We don't want to support this use case just like we don't want to support nightly building of node or appliance. But its the closest we can get to building via CQ as long as we don't finish implementing it.

I don't want the 1st time we start running the container build code frequently to be when it is embedded into the CQ flow.

Are we gonna keep working on container building and releasing code at all?

Yes.

If so, we need to have a build job that builds some containers soon, otherwise we can`t really know if the code we're working on works well or not.

Shouldn't 'build-artifacts.sh' do that after the recent work @Former user did? Doesn't it mean each build is already deployed to 'ovirtinfra' repo on dockerhub? we should just find a new project that should be built as a container and use it for testing.

I just want to avoid us working on something that won't be used or needed, that's all.
And I believe supporting the use case of nightly build of a project like 'ovirt-containers' isn't needed, at least not as first priority.

@Eyal Edri Are we gonna keep working on container building and releasing code at all?

If so, we need to have a build job that builds some containers soon, otherwise we can`t really know if the code we're working on works well or not.

We don't want to find out that for e.g. DockerHub blocks use once we will actually need to quickly deliver a production release process for containers.