Collections using AZP: container update

Project Discussions
, , , ,
1

(Copying over Container update for Azure Pipelines projects · Issue #71 · ansible-collections/news-for-maintainers · GitHub from @mattclay.)

Azure Pipelines Test Container Update

Projects using Azure Pipelines should use the current test container for all branches.

The current container is: quay.io/ansible/azure-pipelines-test-container:6.0.0

A report on each project’s status can be found below.

Checklist

  • ansible.ansible:devel
  • ansible.ansible:stable-2.14
  • ansible.ansible:stable-2.15
  • ansible.ansible:stable-2.16
  • ansible.ansible:stable-2.17
  • ansible.posix:main
  • ansible.windows:main
  • community.crypto:main
  • community.crypto:stable-1 [stable-1] Remove AZP, move all non-remote tests to GHA by felixfontein · Pull Request #766 · ansible-collections/community.crypto · GitHub
  • community.docker:main
  • community.docker:stable-2
  • community.general:main
  • community.general:stable-7
  • community.general:stable-8
  • community.general:stable-9
  • community.libvirt:main
  • community.network:main
  • community.network:stable-4
  • community.network:stable-5
  • community.postgresql:main
  • community.rabbitmq:main
  • community.windows:main
  • consoledot.edgemanagement:main
  • hetzner.hcloud:main
  • hetzner.hcloud:stable-1
  • hetzner.hcloud:stable-2
  • microsoft.ad:main
2

An example PR can be found here: CI: Bump Azure test container to 6.0.0 by felixfontein · Pull Request #8483 · ansible-collections/community.general · GitHub

3

I am the maintainer of the hetzner.hcloud collection, but we do not provide maintenance for the stable-1 and stable-2 branch anymore.

What would be the recommended changes to mark the stable-* branches as unmaintained?

I also would prefer to keep the branch around for the history.