3 MAINTAINER

TOC

• Owership for Ansible work
• Search items from Ansible
• Sync from the Ansible ansible repo
  • Auto sync
  • Need force update(sync) the VSChina/Ansible repo
• Auto run integration test for all azure modules
  • Use Travis CI to run integration test
  • Scale the test on Travis CI

Owership for Ansible work

• Ansible Cloud Modules for Azure - Owner: @yuwzho @zikalino
• Ansible CI - Owner: @yuwzho
• Ansible Playbook Role to release latest Azure Module - Owner:
• Ansible Playbook Sample - Owner: @zikalino
• Ansible Extension - Owner: @yungezz
• Ansible on CloudShell - Owner: @yuwzho
• Ansible Landing Page - Owner: @kyliel
• Ansible Community Working group - Owner: @kyliel

Search items from Ansible

• Module bug report
• Inventory bug report
• Feature request
• Module bug fix pull request
• Inventory bug fix pull request

Sync from the Ansible ansible repo

It now uses Travis-CI to run a auto sync job every day to sync changes from Ansible/ansible repos' devel branch to this devel branch.

Auto sync

If you cannot wait for the next auto-sync, go to the Travis CI's VSChina/ansible travis branch, click the restart build.

Need force update(sync) the VSChina/Ansible repo

If there is something unexpected happen, make our devel branch is conflict with Ansible/ansible devel branch, and cannot sync from it.

1. Click our repo's Settings, temporarily close the protected of devel branch
2. Go to the Travis CI's VSChina/ansible for-push branch, click the restart build
3. Don't forget to re-open the protect for devel branch again

Auto run integration test for all azure modules

Use Travis CI to run integration test

It uses Travis CI to run all the ansible azure module's integration test in one build every week. The purpose is to see whether there is a breaking change from the Azure Rest API. To run the integration test, it uses "Java Tooling Tests with TTL = 2 Days" subscription.

Scale the test on Travis CI

Because of the time limit of CI platform, it runs integration tests in several jobs in the one build. Each job has an id to identify which sequence of test in the test list should run. At the very beginning, it contains 3 jobs, and each job runs 8 integration test. If the number of integration test is increase out of range, add another id in matrix