Awx: Projects start SCM update during jobs, even when "update on launch" is not checked.

[lsantiag86]

ISSUE TYPE

• Bug Report

COMPONENT NAME

• UI

SUMMARY

Projects start SCM updates even when the "update on launch" box is not checked on the project when a job starts. This is causing us issues when the internal gitlab server that has all of the our projects source code is down for maintenance or down at all. All of the jobs triggered fail because gitlab isn't available for the pull.
We also have an automated service roll that will trigger ansible tower when the gitlab server is alerting and that wont work either to fix the host, since it cant perform the pull.

ENVIRONMENT

• Tower 3.2.1
• Ansible 2.4.1.0

STEPS TO REPRODUCE

Run a job.
SCM sync happens before playbook begins

EXPECTED RESULTS

Run a job.
SCM sync only happens if "update on launch" is checked.

ACTUAL RESULTS

Run a job.
SCM sync happens before playbook begins

[wenottingham]

This is expected, there is a checkout that always happens, as there is no guarantee that on any specific Tower node the project is already checked out.

https://github.com/ansible/awx/pull/567 was added to AWX to allow for short-circuiting if the correct version is already checked out, for git only (other SCMs don't have enough info to support this.)

[tombenninger]

@wenottingham We're trying to use Tower as the primary tool for automation for all of our services, including our Git SCM where we develop and store our playbooks and other Ansible configurations.

I realize there's a bit of circular logic here between Ansible and Git, but it seems like a periodic sync and caching function would support this, and I suspect other people have the same issue. Would this be better treated as a feature request than a bug?

[wenottingham]

Already is, but there are many corner cases: https://github.com/ansible/awx/issues/289

[zx1986]

We have roles/requirements.yml, and every launch will run the roles update again, life wasting ...