We attempted to use drupal_tests with an install profile as its own independent repo, and we've found that everything hard-codes the path to modules/repo-name including:
We worked around this by adding a symlink from profiles/repo-name to modules/repo-name in our update-dependencies job, which then persisted to the rest of the jobs with the shared workspace. I'm not yet aware of the downsides.
We attempted to use drupal_tests with an install profile as its own independent repo, and we've found that everything hard-codes the path to modules/repo-name including:
We worked around this by adding a symlink from profiles/repo-name to modules/repo-name in our update-dependencies job, which then persisted to the rest of the jobs with the shared workspace. I'm not yet aware of the downsides.