Install/Configure and manage pyenv
-
- EL 6
-
- EL 7
-
- Debian jessie
-
- Debian stretch
-
- Debian buster
-
- Ubuntu trusty
-
- Ubuntu xenial
-
- Ubuntu bionic
- See the defaults
- The git version of pyenv to install. Default:
master
- Whether or not to upgrade pyenv when ansible runs. Default:
true
- The full path to where pyenv will be installed. Default:
/opt/pyenv
- The full path to the profile script that activates pyenv. Default:
/etc/profile.d/pyenv.sh
- The user for PYENV_ROOT. Default:
root
- The group for PYENV_ROOT. Default:
root
- A list of pythons to install. Default:
- 2.6.9
- 2.7.15
- 3.4.8
- 3.5.5
- 3.6.6
- 3.7.0
- None
---
- name: An example playbook
hosts: all
roles:
- role: codylane.pyenv
pyenv_root: /var/lib/jenkins/.pyenv
pyenv_user: jenkins
pyenv_group: jenkins
pyenv_install_these_pythons:
- 2.6.9
- 2.7.15
- 3.7.0
MIT
-
We use the awesome invoke python library of wrapping how we test.
-
Molecule is being as a test harness but we use
invoke
to provide some additional bootstraping. -
We first setup our test environment, install pyenv, some pythons, our test requirements... etc.
.jenkins/init-pyenv
Usage: inv[oke] [--core-opts] travis [--options] [other tasks here ...]
Docstring:
Run our tests but help travis along
Options:
-d, --[no-]destroy
-p, --[no-]pty
-s, --scenario
- Here is an example of testing just the
default
molecule role
.jenkins/run-pyenv 'invoke travis'
- See .travis.yml for more info
- Cody Lane