-
-
Notifications
You must be signed in to change notification settings - Fork 4
Sync binaries on aws #70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
4d50b27
to
b21cf26
Compare
d97c22c
to
20e7804
Compare
c09333a
to
69e9bfd
Compare
Where do those provision sketches come from? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added some suggestions to improve readability and (a bit) robustness of the Python script.
We could also add the following lines to the .gitignore
for the generated provisioning stuff:
# Provisioning binaries and metadata
firmware/binaries
firmware/provision/**/build
from the old provisioning python script |
2d93b48
to
c74654c
Compare
c5c0ee9
to
5eac31c
Compare
Co-authored-by: Giuseppe Lumia <[email protected]>
Co-authored-by: Giuseppe Lumia <[email protected]>
5eac31c
to
48d915a
Compare
This is the first step to decouple actual provisioning binaries from this repo The provisioning sketches have been introduced in the repo: whenever a change is made on the sketches, the CI will regenerate and upload the new binaries on aws.
This is the first step to decouple actual provisioning binaries from this repo The provisioning sketches have been introduced in the repo: whenever a change is made on the sketches, the CI will regenerate and upload the new binaries on aws.
Motivation
we want to decouple actual binaries from this repo, this brings the following advantages:
device create
from any directory, since binaries are no more tied to a certain folderChange description
the actual download of the binaries has been implemented in other pr #74