Enable using the JitPack mode of building from a parent project#2231
Enable using the JitPack mode of building from a parent project#2231
Conversation
|
Do we still want jitpack code in |
Actually, yes. This PR only removes the gutenberg-mobile bridge library building on Jitpack, but we still have the npm package forks be built on JitPack. Those repos are smaller and don't seem to pose an issue yet. |
|
The WPAndroid PR will target a release so, this PR shall also target |
c8bc57a to
846dcc6
Compare
|
cc @geriux since you're currently wrangling a hotfix release and this PR now targets master. Most probably, the hotfix will need to update after this lands on time. |
Cool! thanks for letting me know 👍 |
SergioEstevao
left a comment
There was a problem hiding this comment.
Building and running the demo app!
I did some smoke test on the demo app and it all looks ok.
And avoid involuntary package upgrades.
|
There's only one CI job pending on the WPAndroid PR (on this commit), which seems to be waiting for Firebase to queue the tests run, for more than 25mins now. I will start the merge domino since everything else is green at this point. Besides, that job will get re-triggered anyway. |
Addresses #2182
We currently experience high failure rate on JitPack building the gutenberg-mobile artifact for WPAndroid, so this PR tries to enable building the artifact and the JS bundle locally, by reusing the gradle-powered Node/RN build.
This mode is then used by WPAndroid. Related PR: wordpress-mobile/WordPress-Android#11833
To test:
PR submission checklist:
RELEASE-NOTES.txtif necessary.