Troubleshooting: Ansible Tower - Project - External SCM vs HTTP_PROXY

troubleshooting-ansible-project-externalscm-http_proxy.txt

# CentOS Linux release 7.2.1511 (Core) 
# Python 2.7.5
# Ansible Version
# 1.9.4
# Ansible Installation Method
# yum
# Tower Version
# 2.4.3
# Troubleshooting: Ansible Tower - Project - External SCM vs HTTP_PROXY
# Error messages: "unable to access 'https://github.com/ansible/tower-example.git/': Failed connect to github.com:443; Connection timed out"

# We can set the proxy information in the playbook that Tower uses to run the SCM update. To do that, we would need to add the 
# environment: keyword and specify the proxy info (http://docs.ansible.com/ansible/playbooks_environment.html). So, for Tower, 
# the update playbook is located in ./usr/lib/python2.7/site-packages/awx/playbooks/project_update.yml

$ vi /usr/lib/python2.7/site-packages/awx/playbooks/project_update.yml

# Add the content below:

- hosts: all
  ...

  environment:
    http_proxy: http://USERNAME:PASS@proxy.com:8080
    https_proxy: http://USERNAME:PASS@proxy.com:8080

  tasks:
  ...

Thanks ygorth! This is just what I needed.
On Ubuntu 14.04.4 LTS the path to project_update.yml is:
/usr/lib/python2.7/dist-packages/awx/playbooks/project_update.yml

you're welcome! 👍