Closed vitorguidi closed 1 month ago
We need the ability to maneuver code between 3.7 and 3.11 in order to rollback potential failure scenarios. This branch serves this purpose.
How to deploy:
PYTHON=python3.7 ./local/install_deps.sh python3.7 -m pipenv shell
regular butler command
Windows used to delete all of clusterfuzz files during update task, and this was resolved in #4025. This was added as the second commit in this PR
This, when deployed, will switch the k8s cronjobs to fetch the production code release and run python 3.7
Motivation
We need the ability to maneuver code between 3.7 and 3.11 in order to rollback potential failure scenarios. This branch serves this purpose.
How to deploy:
outside of pipenv
PYTHON=python3.7 ./local/install_deps.sh python3.7 -m pipenv shell
within pipenv
regular butler command
Gotchas
Windows used to delete all of clusterfuzz files during update task, and this was resolved in #4025. This was added as the second commit in this PR
This, when deployed, will switch the k8s cronjobs to fetch the production code release and run python 3.7