-
Notifications
You must be signed in to change notification settings - Fork 162
[worker] Add worker from turtle-v2 #3268
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
base: main
Are you sure you want to change the base?
Conversation
We'll source `.direnv/test` secrets in CI directly
ac763be to
5e00ef2
Compare
|
Size Change: +82 kB (+0.15%) Total Size: 55 MB
|
e509d68 to
833de30
Compare
# This is the 1st commit message: Use `GCS` from `@expo/build-tools` # The commit message #2 will be skipped: # fixup! Use `GCS` from `@expo/build-tools`
d07514d to
6fd3287
Compare
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #3268 +/- ##
==========================================
- Coverage 51.90% 49.25% -2.64%
==========================================
Files 632 670 +38
Lines 25874 27984 +2110
Branches 5438 5765 +327
==========================================
+ Hits 13427 13781 +354
- Misses 11327 13013 +1686
- Partials 1120 1190 +70 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
73c547b to
94c4f9c
Compare
94c4f9c to
6bf9ac6
Compare
a132a7b to
9970a4a
Compare
c427bac to
b8047fd
Compare
b8047fd to
9708f23
Compare
|
Subscribed to pull request
Generated by CodeMention |
hSATAC
left a comment
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.
Looks good to me overall, but I’ll let Doug give the final approval since he owns this code.
| provisioningProfileBase64: 'MjEzNwo=', | ||
| distributionCertificate: { | ||
| dataBase64: 'MjEzNwo=', | ||
| password: 'dominiksokal', |
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.
Just to confirm this is a dummy credential right?
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.
yea definitely. cc @dsokal your legacy lives on
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.
Confirmed. A dummy credential :)
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.
@sjchmiela try decoding the base64 ;)
| for platform in android ios; do | ||
| GCP_TARBALL="worker-$platform-sha1-$GITHUB_SHA.tar.gz" | ||
|
|
||
| if ! gsutil stat gs://eas-build-worker-tarballs/$GCP_TARBALL; then |
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.
It appears this is the first time gs://eas-build-worker-tarballs has been publicly exposed.
I reviewed the bucket’s access policy and it looks safe.
Adding a note here as this does expand our attack surface.
|
⏩ The changelog entry check has been skipped since the "no changelog" label is present. |
douglowder
left a comment
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.
Looks good -- thanks for the careful organization of commits!
Why
We want to streamline DX of the worker part of EAS. Part of it is colocating all code in one repository.
How
Copied code over to
eas-cli. Adjusted code — each commit represents a single piece of work towards adjusting code to this repository. The main changes are around removing dependency onturtle-v2internal libraries.One thing to figure out still is deployment process. I've added
build-and-deploy-workerwhich is capable of deploying to staging and production. The question is how to automate it. Inturtle-v2we have system tests. Should we just copy them over to here? (Don't like that.) Should we streamline system tests now and instead of having this weirdturtle-v2-examplerepo, create project on the go? Should we deploy worker manually for now?I think I'd rather deploy manually for now?
Test Plan
Deployed worker to staging. Ran system tests. They succeeded!! https://github.com/expo/turtle-v2/actions/runs/20042956545/job/57535011098