# Collections using AZP: container update

**URL:** <https://forum.ansible.com/t/collections-using-azp-container-update/6281>\
**Category:** Project Discussions\
**Tags:** news-for-maintainers, azure, windows, azp, ci\
**Created:** [June 10, 2024, 6:11pm UTC](https://forum.ansible.com/t/collections-using-azp-container-update/6281 "2024-06-10T18:11:30Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [June 10, 2024, 6:11pm UTC](https://forum.ansible.com/t/collections-using-azp-container-update/6281/1 "2024-06-10T18:11:30Z")

</div>

_(Copying over [Container update for Azure Pipelines projects · Issue #71 · ansible-collections/news-for-maintainers · GitHub](https://github.com/ansible-collections/news-for-maintainers/issues/71) 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](https://github.com/ansible-collections/community.crypto/pull/766)
- 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

---

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [June 10, 2024, 6:28pm UTC](https://forum.ansible.com/t/collections-using-azp-container-update/6281/2 "2024-06-10T18:28:24Z")

</div>

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](https://github.com/ansible-collections/community.general/pull/8483)

---

<div class="post-metadata">

**Author:** ![jooola](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jooola/32/737_2.png) [@jooola](https://forum.ansible.com/u/jooola)\
**Post date:** [June 12, 2024, 8:44am UTC](https://forum.ansible.com/t/collections-using-azp-container-update/6281/3 "2024-06-12T08:44:35Z")

</div>

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.