Address validation job failure for DAST on-demand scan for runners with redefined $HOME variable

Proposal

Users that redefine the environment's HOME directory for the runner that is performing the scan will encounter issues with validating a site profile for on-demand DAST scan.

Users will see the following and not able to proceed with the scan:

• Site Profile's "Validation status" remains at Validating....
• The error /tmp/validate.sh: No such file or directory in the validation job log.

Proposal to address validation job failure for DAST on-demand scan for runners with redefined $HOME variable.

Workaround

• Working on a Zendesk knowledge base to reflect the workarounds: gitlab-com/support/support-pages!85 (merged)
  • Unset the HOME environment variable on the runner.
  • Use another runner without the HOME environment variable to run solely the validation job by temporarily disabling the affecting runner, and re-enabling after the job.