Move some tests to GH Actions

[mariolenz]

SUMMARY

Move some tests to GH Actions.

ISSUE TYPE

• Feature Pull Request

COMPONENT NAME

ADDITIONAL INFORMATION

#1746

[softwarefactory-project-zuul]

Build succeeded.
https://ansible.softwarefactory-project.io/zuul/buildset/6bf428ffe3724d8a9bc1f9802fd13cc2

✔️ ansible-tox-linters SUCCESS in 8m 53s
✔️ build-ansible-collection SUCCESS in 9m 14s
❌ ansible-test-sanity-docker-devel FAILURE in 11m 19s (non-voting)
✔️ ansible-test-sanity-docker-milestone SUCCESS in 10m 52s (non-voting)
✔️ ansible-test-sanity-docker-stable-2.13 SUCCESS in 11m 09s
✔️ ansible-test-sanity-docker-stable-2.14 SUCCESS in 11m 32s
✔️ ansible-test-units-community-vmware-python38 SUCCESS in 7m 11s
✔️ ansible-galaxy-importer SUCCESS in 4m 13s

[mariolenz]

recheck

[softwarefactory-project-zuul]

Build succeeded.
https://ansible.softwarefactory-project.io/zuul/buildset/3feb1514050f4b3787da9644291f79eb

✔️ ansible-tox-linters SUCCESS in 8m 24s
✔️ build-ansible-collection SUCCESS in 9m 11s
❌ ansible-test-sanity-docker-devel FAILURE in 10m 24s (non-voting)
✔️ ansible-test-sanity-docker-milestone SUCCESS in 10m 20s (non-voting)
✔️ ansible-test-sanity-docker-stable-2.13 SUCCESS in 9m 48s
✔️ ansible-test-sanity-docker-stable-2.14 SUCCESS in 11m 14s
✔️ ansible-test-units-community-vmware-python38 SUCCESS in 5m 57s
✔️ ansible-galaxy-importer SUCCESS in 3m 53s

[mariolenz]

@jillr Could you please review this PR? Ideally in combination with ansible/ansible-zuul-jobs#1803

[jillr]

@mariolenz Do you want me to update the branch protections after this merges for the new checks? (IMO you should have access to do this yourself for this repo. I'm happy to give you maintainer permissions on the repo but you need admin for branch protections, I'd like to double check with the community team before changing admin rights on a collection just to be in communication with them about it. What do you think?)

[mariolenz]

Do you want me to update the branch protections after this merges for the new checks? (IMO you should have access to do this yourself for this repo. I'm happy to give you maintainer permissions on the repo but you need admin for branch protections, I'd like to double check with the community team before changing admin rights on a collection just to be in communication with them about it. What do you think?)

This looks like another discussion to to me... maybe even two discussions. But there are so many other things to do at the moment that I suggest to move it / them to the future. I don't want to loose track, you know? There are several PRs and issues I have to work on, then there is the question about the future of the CI... oh, and I have a main job, also ;-)

I'll merge this PR and will backport it to the stable-2.x branch (stable-1.x is EOL so we can ignore it). Let's discuss branch protection and maintainer / admin permissions at another time.

[softwarefactory-project-zuul]

Build succeeded (gate pipeline).
https://ansible.softwarefactory-project.io/zuul/buildset/eef6787c29724bb78c0450715c1ed6a9

✔️ ansible-tox-linters SUCCESS in 8m 26s
✔️ build-ansible-collection SUCCESS in 7m 17s
✔️ ansible-test-sanity-docker-stable-2.13 SUCCESS in 13m 40s
✔️ ansible-test-sanity-docker-stable-2.14 SUCCESS in 10m 44s
✔️ ansible-test-units-community-vmware-python38 SUCCESS in 8m 24s
✔️ ansible-galaxy-importer SUCCESS in 6m 04s

[softwarefactory-project-zuul]

Pull request merge failed: Resource not accessible by integration, You may need to manually rebase your PR and retry.