Ian Wienand 4fa8d2dd39
create-venv: make upgrade venv once per day
This was inspired by a similar change
I78a914f71cef687f09fcfee0f3f498b79d810f5d.  In the bootstrap-bridge
production, we are calling create-venv every time we fire off a set of
production jobs.  While it's good to keep the venv updated, it doesn't
need to happen hourly.

This writes the requirements to a file, and only installs it if the
template updates (i.e. if the venv is fresh, the dependencies updated
or we updated the daily timestamp).

Change-Id: I7a70b73fb907b923f47a2a0de72e21649c15e05f
2022-12-06 17:28:09 +11:00

55 lines
1.5 KiB
YAML

- name: Check directory is specified
assert:
that: create_venv_path is defined
- name: Ensure venv dir
file:
path: '{{ create_venv_path }}'
state: directory
# Xenial's default pip will try to pull in packages that
# aren't compatible with 3.5. Cap them
- name: Setup requirements for bionic
when: ansible_distribution_version is version('16.04', '==')
set_fact:
_venv_requirements:
- pip<21
- setuptools<51
# Bionic's default pip will try to pull in packages that
# aren't compatible with 3.6. Cap them
- name: Setup requirements for Bionic
when: ansible_distribution_version is version('18.04', '==')
set_fact:
_venv_requirements:
- pip<22
- setuptools<60
- name: Setup requirements for later era
when: ansible_distribution_version is version('20.04', '>=')
set_fact:
_venv_requirements:
- pip
- setuptools
# This is used to timestamp the requirements-venv.txt file. This
# means we will run --upgrade on the venv once a day, but otherwise
# leave it alone.
- name: Get current day
shell: 'date +%Y-%m-%d'
register: _date
- name: Write requirements
template:
src: requirements-venv.txt
dest: '{{ create_venv_path }}/requirements-venv.txt'
register: _venv_requirements_txt
- name: Create or upgrade venv
when: _venv_requirements_txt.changed
pip:
requirements: '{{ create_venv_path }}/requirements-venv.txt'
extra_args: '--upgrade'
virtualenv: '{{ create_venv_path }}'
virtualenv_command: '/usr/bin/python3 -m venv'