commit | 9c59fb87e21180876571b720e1a78a6bc14f375b | [log] [tgz] |
---|---|---|
author | Borjan Tchakaloff <borjan@steadymonkey.eu> | Fri Feb 07 11:49:41 2020 +0100 |
committer | Borjan Tchakaloff <borjan@steadymonkey.eu> | Fri Feb 07 18:32:55 2020 +0100 |
tree | 1fef221dd1ab56c13cadf35a8b005780152654e0 | |
parent | 5c58b7700f93a967152f1f45da0bbd473fe359be [diff] |
Class-ify the viSer suite deployment methods Clean-up any previous deployment before deploying the suite again. Previous reports will be lost. Issue: INFRA-236 Change-Id: I246af3c41140c9a936d0b5b561903cab34003be0
Deployment script to install and configure the SmartViser solution on devices.
Install the required dependencies in a virtual environment:
% python3 -mvenv venv % . ./venv/bin/activate (venv) % pip install -r requirements.txt
Follow instructions at https://gitlab.fairphone.software/fp/wiki/wikis/fp2/m/gms/sanity#prepare-a-device
Follow (and potentially adapt) instructions on how to run sanity check at https://gitlab.fairphone.software/fp/wiki/wikis/fp2/m/gms/sanity#run-the-sanity-check
Install the pre-commit
hook to setup the toolchain:
(venv) % pip install -r requirements-dev.txt (venv) % pre-commit install
The toolchain can be run independently of the hook. On the staged changes only:
(venv) % pre-commit run
Or on all files:
(venv) % pre-commit run --all-files
To keep things simple, and avoid installing extra software, this repository relies on standard Python tools (pip
and the venv
module).
The abstract dependencies are specified in setup.py
while the actual dependencies (i.e. the required and transitive dependencies) are pinned in dedicated requirements files. This ensures reproducibility.