Deployment fails if branch name is too long

[Aratz]

Description

When working on a deployment, a new folder is created at /vulpes/ngi/devel-<username>/<branch_name>.<date>.<commit hash>. However, if the branch name is too long, the ansible task [archive-verify-ws : install archive-verify service] will fail, probably because the path to the conda environment is too long. From some quick experiments, I found out this starts happening from 36 characters long.

Proposed solution

One solution could be to trunk the branch name when creating this folder. Since the folder name also contains the commit hash and the date, the risk of collision should be pretty low. There is still a risk that this problem occurs if the folder structure in the deployment folder is really deep.

Steps to reproduce:

git checkout main
ansible-playbook -i inventory.yml  install.yml -e deployment_environment=devel -e site=upps -t archive-verify
# Ultimately fails at but succeeds at task "archive-verify-ws : install archive-verify service"

git checkout -b branch_with_a_extremely_lengthy_name
ansible-playbook -i inventory.yml  install.yml -e deployment_environment=devel -e site=upps -t archive-verify
# Fails at task "archive-verify-ws : install archive-verify service":
# fatal: [deploy]: FAILED! => {"changed": false, "cmd": ["/vulpes/ngi/devel-adrienc/branch_with_a_extremely_lengthy_name.240306.414b002/sw/anaconda/envs/archive-verify-ws/bin/pip", "install", "-U", "."], "msg": "\n:stderr: env: ‘python3.9’: No such file or directory\n"}