[MERGING TO TEST BRANCH] Use BuildJet runners for eden workflow #882
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit changes runners of composite `test.yml` workflow to BuildJet runners. They are more powerful and cheaper that the ones provided by GitHub. Note that this workflow is used by EVE repository. Switching to BuildJet runners and using new workflow should reduce time to run tests from 6 hours to approx. 1.5 hours. However, there are still some tests failing which needs further investigation Signed-off-by: Pavel Abramov <uncle.decart@gmail.com>
uncleDecart
changed the title
|
@giggsoff @milan-zededa @yash-zededa New runners are finally here, but LF-EDGE hasn't finalized bulling yet. So I'm raising this PR to merge it to new test branch I created so we can manually trigger To my best knowledge branching this way won't break anything in eden or in eve which is using master branch |
|
LGTM. |
milan-zededa
approved these changes
Jul 31, 2023
|
Few questions:
|
|
Runner workflow https://github.com/lf-edge/eden/actions/runs/5712658495 Yeah @giggsoff , you cannot use them in your fork, I believe I can parametrize it with some variable, will do that in master PR I'll add docs in new PR docs for now are here https://buildjet.com/for-github-actions/docs/getting-started/run-your-first-workflow |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit changes runners of composite
test.ymlworkflow to BuildJet runners. They are more powerful and cheaper that the ones provided by GitHub.Note that this workflow is used by EVE repository.
Switching to BuildJet runners and using new workflow should reduce time to run tests from 6 hours to approx. 1.5 hours.
However, there are still some tests failing which needs further investigation.
Why [MERGING TO TEST BRANCH]: LF-edge is still setting up billing process for BuildJet, we will merge this once it's done. Right now we can try it out and see if it's working by running action manually. Next step would be to check if changing workflow runners changes them while using composite workflow.
Checklist:
test.ymlworkflow and it uses BuildJet runners