Run CI for micropipenv about aicoe-ci HOT 10 CLOSED

I maintain this container image ready with all dependencies micropipenv needs for testing and I know how to configure it in Travis. So, if the Travis is a way to go, I can prepare something. I don't know much about Centos CI.

Recently, @encukou has prepared tox github action with mentioned container so we might try that as well. But I have zero experience with GH actions.

from aicoe-ci.

we can extend the pipeline to run the tox test with the container image for micropipenv. I will include a sample to the existing pipeline, and we can check the compatibility with it. @fridex
and Thanks @frenzymadness for the pointing to the container image :)

from aicoe-ci.

I've tried three possibilities here:

1. Pure Travis config & result — Simple configuration and the tests run on Ubuntu which should make no difference because we depends only on Python packages from PyPI.
2. Travis with Fedora container config & result — Closer to our target environment and new Pythons are available in Fedora sooner than in Travis.
3. GH actions with Fedora container testing PR — Looks good to me as well, has nice integration to GH but the action itself is still in pre-release (but maintained by fedora-python).

from aicoe-ci.

Travis with Fedora container implemented in thoth-station/micropipenv#87

This issue can be closed.

from aicoe-ci.

Let's close this, micropipenv is tested with Travis CI now. If there is a plan to add support for Thoth CI, we can still do it besides Travis as discussed on the call.

Thanks @frenzymadness @harshad16 👍

from aicoe-ci.

CC @harshad16 @frenzymadness @goern

from aicoe-ci.

we can extend the pipeline to run the tox test with the container image for micropipenv.

What pipeline do you mean?

from aicoe-ci.

we can extend the pipeline to run the tox test with the container image for micropipenv.

What pipeline do you mean?

we developed aicoe-ci based on openshift-pipeline/tekton-pipeline, it runs checks as task(similar to a job). Earlier as i stated we can embed another task for tox test, based upon the container image earlier mentioned in the thread.

from aicoe-ci.

So, which one we want to use?

from aicoe-ci.

Ack, tox test is already included in the pipeline. However, it needs to be refined more, it would run in parallel with the Travis test. It wouldn't cause any issue in the pull request.

from aicoe-ci.