Skip to content
This repository has been archived by the owner on May 14, 2024. It is now read-only.

Document how to run tests with Ansible pre-releases #156

Closed
Andersson007 opened this issue Oct 27, 2022 · 7 comments
Closed

Document how to run tests with Ansible pre-releases #156

Andersson007 opened this issue Oct 27, 2022 · 7 comments
Assignees

Comments

@Andersson007
Copy link
Contributor

Andersson007 commented Oct 27, 2022

Summary

Relates to ansible/ansible#72226

Copied from the issue:

We are publishing more Ansible RCs than ever before.
Let's capitalize on this and document how we expect Ansible collection maintainers
to install Ansible pre-releases in CI systems and why they might want to do so.

See the full description.

Ideas?

@felixfontein
Copy link
Contributor

Is this about ansible-core pre-releases, or Ansible pre-releases? I would guess the former. In that case, almost all collection CIs I know already test against them, since they use the stable-2.x branches instead of installing ansible-core from PyPi.

@Andersson007
Copy link
Contributor Author

Is this about ansible-core pre-releases, or Ansible pre-releases? I would guess the former. In that case, almost all collection CIs I know already test against them, since they use the stable-2.x branches instead of installing ansible-core from PyPi.

I asked the same in the issue. and replied the same about ansible-core:)
Does it make any sense to test a collection against RC of Ansible on the collection's side (or is it possible in general?).

@gotmax23
Copy link
Contributor

Ansible (community package) is just a collection of collections so IMO it would only make sense for collections with dependencies on other collections to do this.

@Andersson007
Copy link
Contributor Author

Does anyone know if there's any documentation related to setting up CI (using GHA or AZP)?
I failed to find that in the collection testing doc page
Should we add a paragraph describing the GHA and AZP options in detail (including referencing to https://github.com/ansible-collections/collection_template/blob/main/.github/workflows/ansible-test.yml) to the doc page or maybe there's a better place? (maybe another doc or create a new separate doc?)
Ideas?
IMO it's an important topic which doesn't seem covered but should be

@felixfontein
Copy link
Contributor

@Andersson007 the collection template (https://github.com/ansible-collections/collection_template) contains a workflow or GHA. I don't think there is a good template for AZP based CI, probably also because that's kind of special. I'm not sure whether any but a few special collections use that.

Regarding docs, it's probably best to link to the collection template as an example for GHA.

@Andersson007
Copy link
Contributor Author

@felixfontein

Regarding docs, it's probably best to link to the collection template as an example for GHA.

Sure, i meant to say to add a paragraph with a high level overview of CI configuration-related stuff and, yep, linking to collection_template is a good thing to do imo.
Maybe we could also mention AZP there for collections where to run integration tests on several distros is important.
How about the place for the paragraph, that page or a dedicated one? Or we could start the paragraph on the page and then will see along the way if it's OK.

@mariolenz
Copy link
Contributor

@Andersson007 Please close this issue if done, or open a new forum topic and then close the issue with a pointer to the new discussion: Community-topics: Archiving the repo

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants