ansible: create git repo under binary_tmp user

[richardlau]

Create the binary_tmp git repository under the home directory for the binary_tmp user to avoid permissions issues encountered when previously trying to create it under the iojs user.

This change will mean that for any machines that mount expanded storage as an additional disk, the binary_tmp users' home directory will need to be on the larger storage. In practice this means that the additional disk should be mounted at /home/ rather than /home/iojs/.

Fixes: #3732

[richardlau]

Draft while testing.

Tested on test-equinix-ubuntu2204-x64-2 (jenkins-workspace-8).

Planning to test on test-ibm-ubuntu2204-x64-3 (jenkins-workspace-6) once jobs finish running on it (as I'll need to remount the additional disk at /home/ instead of /home/iojs/).

The live binary_tmp git repository is running on test-equinix-ubuntu2204-x64-1 (jenkins-workspace-7) and I suspect the playbook with these changes will fall over as /home/binary_tmp/binary_tmp.git is a symbolic link (on the other machine(s) I've removed the link and target but if I remove the target on jenkins-workspace-7 then any in-flight fanned jobs would fail and none of the fanned jobs would be resumable). I may need to attempt to move and/or copy the git repo on this machine (~58GB) manually to the new location if we want to prevent the loss of data.

[richardlau]

Planning to test on test-ibm-ubuntu2204-x64-3 (jenkins-workspace-6) once jobs finish running on it (as I'll need to remount the additional disk at /home/ instead of /home/iojs/).

Remounted the disk on test-ibm-ubuntu2204-x64-3 (jenkins-workspace-6) at /home/ and tested the updated playbook there.

[richardlau]

The live binary_tmp git repository is running on test-equinix-ubuntu2204-x64-1 (jenkins-workspace-7) and I suspect the playbook with these changes will fall over as /home/binary_tmp/binary_tmp.git is a symbolic link (on the other machine(s) I've removed the link and target but if I remove the target on jenkins-workspace-7 then any in-flight fanned jobs would fail and none of the fanned jobs would be resumable). I may need to attempt to move and/or copy the git repo on this machine (~58GB) manually to the new location if we want to prevent the loss of data.

CI was quiet so I went ahead and did this:

• Removed /home/binary_tmp/binary_tmp.git symlink.
• Moved /home/iojs/build/binary_tmp.git to /home/binary_tmp/binary_tmp.git so that /home/binary_tmp/binary_tmp.git is the real git repository and not a symbolic link.
• Validated the update playbook runs against test-equinix-ubuntu2204-x64-1 (jenkins-workspace-7).
• Ran test builds to check that jobs could still write to/read from the binary_tmp git repository:
  • https://ci.nodejs.org/job/node-test-commit-windows-fanned/63111/
  • https://ci.nodejs.org/job/node-test-commit-arm-fanned/36838/