# Need help on new community.vmware CI

**URL:** <https://forum.ansible.com/t/need-help-on-new-community-vmware-ci/44349>\
**Category:** Collection Development\
**Tags:** azure, github, vmware, zuul\
**Created:** [August 21, 2025, 4:28pm UTC](https://forum.ansible.com/t/need-help-on-new-community-vmware-ci/44349 "2025-08-21T16:28:57Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\
**Post date:** [August 21, 2025, 4:28pm UTC](https://forum.ansible.com/t/need-help-on-new-community-vmware-ci/44349/1 "2025-08-21T16:28:57Z")

</div>

We’ve been running [community.vmware](https://github.com/ansible-collections/community.vmware) integration tests against vSphere 7 on Zuul for some time. This was quite cool because the tests used a real vCenter and real ESXi hosts. But this has been build by @goneri, who moved on to work on other stuff meanwhile. So there’s nobody at Red Hat anymore who has a good understanding about VMware vSphere.

It’s been quite clear for some time that this will stop sooner or later. And that nobody will work on vSphere 8 and later. See [here](https://github.com/ansible-collections/community.vmware/issues/1746) for more information.

To make a long story short, I’ve [removed the community.vmware integration tests from Zuul](https://github.com/ansible/ansible-zuul-jobs/pull/1916). They failed and trying to fix this didn’t seem worthwhile, since vSphere 7 will be EOL October, 2.

But those tests have been _extremely_ valuable, so it would be great to find a way running them again. Preferably with a real vCenter and real ESXi hosts, but [vcsim](https://hub.docker.com/r/vmware/vcsim) or something similar would be better than nothing.

My idea is to implement this with GitHub actions, Azure pipelines or (again) Zuul. But I have absolutely no idea how to do this, or even where to start. Any help would be much appreciated!

PS  
Just to make this clear, I don’t want to blame Red Hat at all. It’s absolutely my fault that I didn’t find a solution for this yet, or at least asked for help up until now. I’ve been forewarned 2 years ago, after all.