-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Gutenberg/embedded build no jitpack #11896
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
Gutenberg/embedded build no jitpack #11896
Conversation
Internally, passing down a "jitpack" flag to emulate the nested gutenberg-mobile build, which behind the scenes uses Node and Yarn to install the needed gutenberg-mobile RN dependencies to build.
On CircleCI, the JS bundle is build by a dedicated job to avoid out of memory issues when doing it embedded in the gradle build.
To try and avoid the out of memory issue (exit code 137) that seems to be happening.
The gb-mobile JS bundle has already been built and shared as via a CircleCI attached workspace so, no need for the nested submodules that only contribute JS code anyway.
…r-db-update-script When upgrading from older version do not go through migration script steps.
…-open-external-link Fix crash on opening external url
Generated by 🚫 dangerJS |
# Conflicts: # .circleci/config.yml
|
You can trigger optional UI/connected tests for these changes by visiting CircleCI here. |
|
You can test the changes on this Pull Request by downloading the APK here. |
…ild-no-jitpack Build gutenberg-mobile locally without JitPack # Conflicts: # .circleci/config.yml
5d1a9c5 to
1faee8d
Compare
9802254 to
aca31b1
Compare
|
👋 @cameronvoell and @chipsnyder . I think I've resolved the issues you both observed in doing debug builds with the avoid-jetpack changes in #11893 . Would you care to give this PR a try? |
|
Ran through the following builds with no problem 🥳 🚀 Nice work!
|
chipsnyder
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.
Test results here: #11896 (comment)
Same results as Chip here #11896 (comment) Looks good! |
|
👋 @hypest ! I added a couple of changes on top of yours here. Would appreciate it if you could take a look since you're the most familiar with this.
|
|
I think the no-jitpack solution was merged to develop via #11921 so, not sure if this PR is needed anymore? |
|
I don't think we need this PR now that the release branch was merged back to develop. |
Stop using jitpack
To test:
wp.BUILD_GUTENBERG_FROM_SOURCEis false./gradlew assembleVanillaReleasefrom the command linewp.BUILD_GUTENBERG_FROM_SOURCEis true./gradlew assembleWasabiDebugfrom the command linePR submission checklist:
RELEASE-NOTES.txtif necessary.