Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Collection CI related actions needed #811

Closed
Andersson007 opened this issue Sep 26, 2022 · 2 comments · Fixed by #808
Closed

Collection CI related actions needed #811

Andersson007 opened this issue Sep 26, 2022 · 2 comments · Fixed by #808

Comments

@Andersson007
Copy link
Contributor

SUMMARY

Relates to ansible-collections/news-for-maintainers#24.

It's been detected that this repository contains ignore-2.14.txt file but not ignore-2.15.txt file.

Actions needed:

  • Copy tests/sanity/ignore-2.14.txt to tests/sanity/ignore-2.15.txt otherwise the CI will get failing.
  • If it's not done yet, add the stable-2.15 branch to your CI workflow files. If you use GitHub actions, see the content of .github/workflows or, if you use Azure Pipelines, community.postgresql/.azure-pipelines/azure-pipelines.yml. If not added, this will violate the Collection Requirements for collections included in the Ansible package.
  • Subscribe to and track the news-for-maintainers repository if you're not subscribed yet.
  • If it's not relevant for this repo, just close the issue.

To read more about the topic, see the Ignores guide.

To read more about the context, see the announcement.

Thank you!

@D3DeFi
Copy link
Contributor

D3DeFi commented Sep 26, 2022

@Andersson007 I've opened #808 3 days ago addressing this, but didn't merge right away as I've considering deprecating 2.10 and 2.11 tests, which would also drop python2.7/3.6 from our CI matrix, save sime time on builds and precious free CI minutes we are eating from Github Actions.

since I have your attention, can you add your opinion to #808?

@Andersson007
Copy link
Contributor Author

@D3DeFi cool, LGTM, thanks! I've put Fixes this issue in the PR

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

Successfully merging a pull request may close this issue.

2 participants