QA (public) » openQA Project (public)

Well, the problem here is the time that this spend installing the packages during the building.
This could be a problem because of the weigth of the process (internal problem) or because the connectivity with the
repository mirrors (external problem).

I created this PR
https://github.com/os-autoinst/os-autoinst-distri-openQA/pull/70

An alternative option could be to have a pre-built image with only the installation process.
I am thinking we could create a Dockerfile-base file with the installation, that will always be executed
previously, therefore when real Dockerfile will try to build will got this part from the previous image.

ilausuch wrote:

Well, the problem here is the time that this spend installing the packages during the building.
This could be a problem because of the weigth of the process (internal problem) or because the connectivity with the
repository mirrors (external problem).

I created this PR
https://github.com/os-autoinst/os-autoinst-distri-openQA/pull/70

Okay, so this is bumping the timeout in case e.g. the worker is busy 🤔️

An alternative option could be to have a pre-built image with only the installation process.
I am thinking we could create a Dockerfile-base file with the installation, that will always be executed
previously, therefore when real Dockerfile will try to build will got this part from the previous image.

Can we publish and re-use the containers from compose.yml? That's already running for every PR.

It is not a reuse, because this could be dangerous and won't test this effectively. My point is to split the image in two. But after thinking in that, I don't believe it is a good solution:

• We don't have enough common installation process between the openQA containers (webui, worker,...)
• We will add confusion in the building process So I think we should discard this idea.

Merged. I'll wait some more test to check if this solution is really effective