[example tests] Adding a clone and a deploy step to allow optimizations in CI. #3208
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 adds an example clone and deploy step that allows you to modify each top level repository before pulling in the rest of the example's dependencies. This allows us to not pull in a copy of mbed-os for each example in CI and instead symbolic link the already cloned copy, saving valuable time and disk space
|
/morph test |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
Outputmbed Build Number: 1006 All builds and test passed! |
|
@adbridge review? |
|
@bridadan Please add a section to the description showing an example of how you would use the new commands. |
|
Otherwise code changes LGTM 👍 |
|
@bridadan thanks for the description update, very useful. LGTM |
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.
Description
This adds an example clone and deploy step that allows you to modify
each top level repository before pulling in the rest of the example's
dependencies. This allows us to not pull in a copy of mbed-os for each
example in CI and instead symbolic link the already cloned copy, saving
valuable time and disk space
Status
READY
Migrations
If this PR changes any APIs or behaviors, give a short description of what API users should do when this PR is merged.
NO
Todos
How to use
These changes are intended mostly for use in CI. Currently importing the examples and their dependencies (including mbed-os for every example) takes upwards of 10 minutes and multiple GBs of disk space. This will both reduce the time and disk space for testing with one common mbed-os revision by allowing you to symbolic link to one specific repository. The flow would look like the following.
cd examplesclonecommand:python ../mbed-os/tools/examples/examples.py clonegitorhgcommand to clone just the top level example repoln -s ../../mbed-os mbed-osor use the equivalent command on your OSdeploycommand to finish pulling in each examples' dependencies (in this case, mbed-os is already present so it is not cloned):python ../mbed-os/tools/examples/examples.py deployAt this point, the examples are fully cloned. You can now use the rest of
examples.pyas you normally would.