# Ansible to adopt molecule and ansible-lint projects. **URL:** \ **Category:** Ansible Project\ **Tags:** ansible-lint, galaxy-ng\ **Created:** [September 26, 2018, 12:22pm UTC](https://forum.ansible.com/t/ansible-to-adopt-molecule-and-ansible-lint-projects/28657 "2018-09-26T12:22:28Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![tima](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/tima/32/854_2.png) [@tima](https://forum.ansible.com/u/tima)\ **Post date:** [September 26, 2018, 12:22pm UTC](https://forum.ansible.com/t/ansible-to-adopt-molecule-and-ansible-lint-projects/28657/1 "2018-09-26T12:22:28Z")
To support the continued growth of Ansible we are expanding Ansible Galaxy to include new functionality and tooling. A goal of this expansion is to provide a minimum viable level of quality checks for content on Ansible Galaxy. One of the first steps we are taking is adopting molecule and ansible-lint as official Red Hat Ansible projects. ansible-lint and molecule are great tools. They’ve been built and tested by the community that we see as essential parts of enhancing development of Ansible automation. By adopting these tools, Red Hat intends to invest resources working with the community to make them even better. We are very excited to integrate ansible-lint and molecule with the rest of the Ansible projects. We would like to thank Cisco, specifically John Dewey, for their work on molecule. Cisco’s willingness to transfer this project over to the Red Hat Ansible team lends great credence to their contributions to the open source ecosystem. We also want to thank Will Thames, the maintainer of ansible-lint, for his contributions developing a tool that has done so much for Playbook authors. We look forward to working with the communities that have made these projects what they are. We want to share further improvements with the broader Ansible community as well. So what happens now? The repos will be migrated to the Ansible organization on GitHub. The transition and roadmap will be iterated on gradually. Ideally, the community will help guide our decision making as we go forward. If you’re not familiar with these projects I encourage you to become more familiar with them and how they can make automating with Ansible even more simple and frictionless. [https://github.com/metacloud/molecule](https://github.com/metacloud/molecule) [https://molecule.readthedocs.io/en/latest/](https://molecule.readthedocs.io/en/latest/) [https://www.digitalocean.com/community/tutorials/how-to-test-ansible-roles-with-molecule](https://www.digitalocean.com/community/tutorials/how-to-test-ansible-roles-with-molecule) [https://groups.google.com/forum/#!forum/molecule-users](https://groups.google.com/forum/#!forum/molecule-users) [https://github.com/willthames/ansible-lint](https://github.com/willthames/ansible-lint) Watch this space for more in the coming weeks and months. ---
**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\ **Post date:** [October 22, 2018, 10:32am UTC](https://forum.ansible.com/t/ansible-to-adopt-molecule-and-ansible-lint-projects/28657/2 "2018-10-22T10:32:18Z")
Overview As previously announced, Ansible has adopted upstream maintenance for ansible-lint and Molecule. See [Sept 26th mailing list post](https://groups.google.com/forum/#!topic/ansible-project/ehrb6AEptzA) for the background. What will change: - GitHub repos for both projects - [GitHub - ansible/ansible-lint: ansible-lint checks playbooks for practices and behavior that could potentially be improved and can fix some of the most common ones for you](http://github.com/willthames/ansible-lint/) will move to [github.com/ansible/ansible-lint[1]](http://github.com/ansible/ansible-lint%5B1%5D) - [GitHub - ansible/molecule: Molecule aids in the development and testing of Ansible content: collections, playbooks and roles](http://github.com/metacloud/molecule) will move to [github.com/ansible/molecule[1]](http://github.com/ansible/molecule%5B1%5D) - All history (including Issues & PRs) will be migrated - Docker location for Molecule - Docker image will be published to [Quay](http://quay.io/repository/molecule) [1] - The existing [https://hub.docker.com/r/retr0h/molecule/](https://hub.docker.com/r/retr0h/molecule/) will not receive further updates. Details on how pull from the new location will be included in follow up email What will remain the same: - **Molecule** - PyPi package name [molecule](https://pypi.org/project/molecule/) - Continue to install with pip install molecule - Upgrade from previous versions seamlessly - Documentation at [https://molecule.readthedocs.io/en/latest/](https://molecule.readthedocs.io/en/latest/) - Community communications - [https://groups.google.com/forum/#!forum/molecule-users](https://groups.google.com/forum/#!forum/molecule-users) - #molecule-users on Freenode IRC - **Ansible-lint** - PyPi package name [ansible-lint](http://pypi.org/project/ansible-lint) - Continue to install with pip install ansible-lint - Upgrade from previous versions seamlessly Timing and next steps We will move the GitHub repos and make the associated updates the week of 29th October. Once the repo move has been completed and documentation has been rebuilt we will release new versions of both projects. We’ll send release announcements to the [ansible-announce mailing list](https://groups.google.com/forum/#!forum/ansible-announce) and to the relevant community lists. What you will need to do after the changes: - If you’ve checked out the code for either project, you’ll need to update your git remote. - If you’re using Molecule from [hub.docker.com](http://hub.docker.com), you’ll need to to update your docker registry. - We’ll provide more details when the changes have been made. To find out more Subscribe to the [ansible-announce mailing list](https://groups.google.com/forum/#!forum/ansible-announce) Kind regards, John “gundalow” Barker Ansible by Red Hat [1] Note, that these new URLs will not exist till the move is complete ---
**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\ **Post date:** [October 22, 2018, 11:20am UTC](https://forum.ansible.com/t/ansible-to-adopt-molecule-and-ansible-lint-projects/28657/3 "2018-10-22T11:20:58Z")
Overview As previously announced, Ansible has adopted upstream maintenance for ansible-lint and Molecule. See [Sept 26th mailing list post](https://groups.google.com/forum/#!topic/ansible-project/ehrb6AEptzA) for the background. What will change: - GitHub repos for both projects - [github.com/willthames/ansible-lint/](http://github.com/willthames/ansible-lint/) will move to [github.com/ansible/ansible-lint[1]](http://github.com/ansible/ansible-lint%5B1%5D) - [github.com/metacloud/molecule](http://github.com/metacloud/molecule) will move to [github.com/ansible/molecule[1]](http://github.com/ansible/molecule%5B1%5D) - All history (including Issues & PRs) will be migrated - Docker location for Molecule - Docker image will be published to [quay.io/repository/molecule](http://quay.io/repository/molecule) [1] - The existing [https://hub.docker.com/r/retr0h/molecule/](https://hub.docker.com/r/retr0h/molecule/) will not receive further updates. Details on how pull from the new location will be included in follow up email What will remain the same: - **Molecule** - PyPi package name [molecule](https://pypi.org/project/molecule/) - Continue to install with pip install molecule - Upgrade from previous versions seamlessly - Documentation at [https://molecule.readthedocs.io/en/latest/](https://molecule.readthedocs.io/en/latest/) - Community communications - [https://groups.google.com/forum/#!forum/molecule-users](https://groups.google.com/forum/#!forum/molecule-users) - #molecule-users on Freenode IRC - **Ansible-lint** - PyPi package name [ansible-lint](http://pypi.org/project/ansible-lint) - Continue to install with pip install ansible-lint - Upgrade from previous versions seamlessly Timing and next steps We will move the GitHub repos and make the associated updates the week of 29th October. Once the repo move has been completed and documentation has been rebuilt we will release new versions of both projects. We’ll send release announcements to the [ansible-announce mailing list](https://groups.google.com/forum/#!forum/ansible-announce) and to the relevant community lists. What you will need to do after the changes: - If you’ve checked out the code for either project, you’ll need to update your git remote. - If you’re using Molecule from [hub.docker.com](http://hub.docker.com/), you’ll need to to update your docker registry. - We’ll provide more details when the changes have been made. To find out more Subscribe to the [ansible-announce mailing list](https://groups.google.com/forum/#!forum/ansible-announce) Kind regards, John “gundalow” Barker Ansible by Red Hat [1] Note, that these new URLs will not exist till the move is complete ---
**Author:** ![Pablo\_Daniel\_Estigar](https://avatars.discourse-cdn.com/v4/letter/p/ecc23a/32.png) [@Pablo\_Daniel\_Estigar](https://forum.ansible.com/u/Pablo_Daniel_Estigar)\ **Post date:** [February 8, 2019, 3:21am UTC](https://forum.ansible.com/t/ansible-to-adopt-molecule-and-ansible-lint-projects/28657/4 "2019-02-08T03:21:17Z")
Hi all! I think it was really excelent to have molecule adopted by ansible and I use it on all my linux roles. Today I’m looking to have some way to use molecule to test my Windows roles too, at lease having driver with some cloud. But I can’t find any guide to go in this way. Also checking some of the 180+ roles that appears in galaxy with windows platform: [https://galaxy.ansible.com/search?order\_by=-relevance&keywords=&deprecated=false&platforms=Windows&page\_size=10&page=2](https://galaxy.ansible.com/search?order_by=-relevance&keywords=&deprecated=false&platforms=Windows&page_size=10&page=2) I don’t see any of them having a real test of windows deploy automated in any way. For example, just picking randomly some of them: This one has only syntax check: [https://github.com/brianshumate/ansible-nomad/blob/master/.travis.yml](https://github.com/brianshumate/ansible-nomad/blob/master/.travis.yml) And this one does nothing: [https://github.com/deekayen/ansible-role-chocolatey/blob/master/.travis.yml](https://github.com/deekayen/ansible-role-chocolatey/blob/master/.travis.yml) Have ansible core and windows people ever noticed it? I think I and the ansible community needs help here, as I couldn’t find any way to test my windows roles automatically yet. Cheers, Pablo.