[Test Automation] Add schedule job as accepted job for PRs and cron jobs#270
[Test Automation] Add schedule job as accepted job for PRs and cron jobs#270ConnorHack wants to merge 9 commits intometa-llama:mainfrom
Conversation
ConnorHack
requested review from
ashwinb,
dltn,
hardikjshah,
raghotham and
yanxi0830
as code owners
facebook-github-bot
added
the
CLA Signed
| run: | ||
| shell: bash # default shell to run all steps for a given job. | ||
| runs-on: ${{ inputs.runner != '' && inputs.runner || 'llama-models-gha-runner-cpu' }} | ||
| runs-on: ${{ inputs.runner != '' && inputs.runner || github.repository_owner == 'meta-llama' && 'llama-models-gha-runner-cpu' || 'llama-models-fork-gha-runner-cpu' }} |
There was a problem hiding this comment.
can you comment what these substrings mean? why "fork"?
There was a problem hiding this comment.
Our self-hosted runners are initially set up using Cloud Terraform code. Each runner has distinct attributes, including:
- A generic label for the runner
- A specific repository URL
When testing from a fork, a separate runner is required to run independently of the main runner. This is because the forked repository URL differs from the main repository URL, and each runner can only point to one repository.
I adjusted this line so it automatically determines what name to use based on if the repository owner is meta-llama. If it is, then we use the default runner for the main repository. If not, then we use the runner that targets the fork.
|
@ashwinb anything else needed to ship this? |
4 participants
What does this PR do?
Updates CI/CD testing to the schedule workflow job for PRs, manual dispatch, and cron jobs.
Test Plan