[WIP] move a most of CI from ansible-network to ansible-content-actions for…

[yurnov]

move a most of CI from ansible-network to ansible-content-actions for #751

SUMMARY

This PR aims to unify the CI process for kubernetes.core with another ansible-collections.

ISSUE TYPE

CI

COMPONENT NAME

.github/workflows/changelog.yaml .github/workflows/integration-tests.yaml .github/workflows/linters.yaml .github/workflows/sanity-tests.yaml .github/workflows/unit-tests.yaml

ADDITIONAL INFORMATION

Refer:

• https://docs.ansible.com/ansible/latest/dev_guide/developing_collections_testing.html

[softwarefactory-project-zuul[bot]]

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

:heavy_check_mark: ansible-galaxy-importer SUCCESS in 4m 18s :heavy_check_mark: build-ansible-collection SUCCESS in 6m 53s

[gravesm]

A few comments before you spend too much time on this. Integration tests will likely never work on ansible-content-actions because there's too much set up specific to this collection. While we did previously consider moving sanity, linter and unit tests to ansible-content-actions, our understanding is that it is not in fact supported. Until we can get clarity around the state and future of that action, we're unlikely to switch CI over.

[yurnov]

A few comments before you spend too much time on this. Integration tests will likely never work on ansible-content-actions because there's too much set up specific to this collection. While we did previously consider moving sanity, linter and unit tests to ansible-content-actions, our understanding is that it is not in fact supported. Until we can get clarity around the state and future of that action, we're unlikely to switch CI over.

Thanks, @gravesm for that comment, I will close this PR to not waste time