Skip to content

Conversation

@SergioEstevao
Copy link
Contributor

@SergioEstevao SergioEstevao commented May 12, 2020

Stop using jitpack

To test:

  • 1
    • wp.BUILD_GUTENBERG_FROM_SOURCE is false
    • Run ./gradlew assembleVanillaRelease from the command line
  • 2
    • wp.BUILD_GUTENBERG_FROM_SOURCE is true
    • Run ./gradlew assembleWasabiDebug from the command line

PR submission checklist:

  • I have considered adding unit tests where possible.
  • I have considered adding accessibility improvements for my changes.
  • I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.

hypest and others added 30 commits May 8, 2020 01:44
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.
malinajirka and others added 2 commits May 12, 2020 09:45
…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
@SergioEstevao SergioEstevao requested review from dratwas and maxme May 12, 2020 09:34
@peril-wordpress-mobile
Copy link

peril-wordpress-mobile bot commented May 12, 2020

Warnings
⚠️ PR is missing at least one label.
⚠️ PR is not assigned to a milestone.

Generated by 🚫 dangerJS

@peril-wordpress-mobile
Copy link

peril-wordpress-mobile bot commented May 12, 2020

You can trigger optional UI/connected tests for these changes by visiting CircleCI here.

@peril-wordpress-mobile
Copy link

peril-wordpress-mobile bot commented May 12, 2020

You can test the changes on this Pull Request by downloading the APK here.

hypest added 2 commits May 12, 2020 10:54
…ild-no-jitpack

Build gutenberg-mobile locally without JitPack
# Conflicts:
#	.circleci/config.yml
@SergioEstevao SergioEstevao changed the base branch from develop to gutenberg/after_1.28.0 May 12, 2020 14:26
@mchowning mchowning force-pushed the gutenberg/embedded-build-no-jitpack branch from 5d1a9c5 to 1faee8d Compare May 12, 2020 22:25
@mchowning mchowning force-pushed the gutenberg/embedded-build-no-jitpack branch from 9802254 to aca31b1 Compare May 13, 2020 13:01
@mchowning
Copy link
Contributor

👋 @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?

@chipsnyder
Copy link
Contributor

Ran through the following builds with no problem 🥳 🚀 Nice work!

BUILD_GUTENBERG_FROM_SOURCE set to false:

  • ./gradlew assembleVanillaDebug
  • ./gradlew assembleVanillaRelease
  • ./gradlew assembleWasabiDebug
  • ./gradlew assembleWasabiRelease

BUILD_GUTENBERG_FROM_SOURCE set to true:

  • ./gradlew assembleVanillaDebug
  • ./gradlew assembleVanillaRelease
  • ./gradlew assembleWasabiDebug
  • ./gradlew assembleWasabiRelease

Copy link
Contributor

@chipsnyder chipsnyder left a 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)

@cameronvoell cameronvoell self-requested a review May 13, 2020 19:05
@cameronvoell
Copy link
Contributor

👋 @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?

Same results as Chip here #11896 (comment) Looks good!

@mchowning
Copy link
Contributor

👋 @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.

  1. We were having issues building from source with these changes because we need to not build the JSBundle when building from source, so in aca31b1 I updated the buildGutenbergMobileJSBundle variable to insure that it was never true if wp.BUILD_GUTENBERG_FROM_SOURCE is true.
  2. There were some CI failures on the "Ensure Assets Folder Existsstage because we were trying to create the assets folder, but CI reported that the folder already existed. I updated the commands frommkdirtomkdir -p` to avoid this in 2e91423.

@hypest
Copy link
Contributor

hypest commented May 18, 2020

I think the no-jitpack solution was merged to develop via #11921 so, not sure if this PR is needed anymore?

@SergioEstevao
Copy link
Contributor Author

I don't think we need this PR now that the release branch was merged back to develop.
Closing it for now, if we need to have something from this branch we can cherry-pick later on.

@SergioEstevao SergioEstevao deleted the gutenberg/embedded-build-no-jitpack branch May 18, 2020 13:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.