Summary:
This removes Bintray/JCenter specific code and replaces it with a new plugin recommended by [Chris Banes](https://chris.banes.dev/publishing-to-maven-central/).
Pull Request resolved: https://github.com/facebook/flipper/pull/1914
Test Plan:
Manually uploaded as snapshot and full release, but with this setup still requires all sorts of manual setup, including GPG. Next PR will include automation for this.
CI here should also verify that I didn't split this diff up incorrectly.
Reviewed By: jknoxville
Differential Revision: D26367350
Pulled By: passy
fbshipit-source-id: faa6b488d6c95bc643d2f9328362e29fb4b05ded
Summary:
This PR adds a github action to publish pods on a new tag. It also tries to fix a race condition which happens when we try to publish FlipperKit pod. During the release of FlipperKit pod, we rely on the newly published Flipper Pod, and sometimes the release of Flipper Pod takes a time to get updated in the cocoapods trunk.
This is a known issue by the Cocoapods and they will be shipping a fix to this in Cocoapods 1.10. Till then we can keep retrying for 5 times.
Ref: https://github.com/CocoaPods/CocoaPods/issues/9502#issuecomment-579486258
## Changelog
- Adds Github actions to publish cocoapods.
- Removes the Circle CI config to publish on cocoapods
Pull Request resolved: https://github.com/facebook/flipper/pull/1083
Test Plan: I tested this action by running it on this PR and it worked fine.
Reviewed By: jknoxville
Differential Revision: D21348084
Pulled By: priteshrnandgaonkar
fbshipit-source-id: f33f3cdef43ae032ad42c94db72323212e40ec67
Summary:
This PR sets up Circle CI to publish pods when github release is made. This PR also updates the Flipper-Folly pod as it didn't build on 32 bit architecture, because `thread_local` was not supported.
Automated publish of cocoapods through Circle CI.
Pull Request resolved: https://github.com/facebook/flipper/pull/445
Reviewed By: danielbuechele
Differential Revision: D15333975
Pulled By: priteshrnandgaonkar
fbshipit-source-id: 7db68efeeebbe344213917f10f9f3ce4132e8cbc
Summary:
Apparently this seems to be the only way to make build work, with the updated licenses. It also follows the same strategy as Travis.
I am using double pipe in `sdkmanager` command execution, to avoid breaking the build, because `sdkmanager` returns exit code 141 in case it meets the requirements requested. (e.g.: `yes | sdkmanager --licenses` returns 141, which in turn breaks the build due to `set -eo pipefail` Bash flags, that CircleCI is using in order to execute any scripts)
For the record, I tried the following solutions, that did not work:
* Add accepted license SHA in Android SDK licenses folder.
* Accept all licenses prior to running the other jobs (with a separate job, working as a dependency to the rest of the Workflow jobs) (`yes | sdkmanager --licenses`)
* Accept all licenses prior to executing any Gradle command (without a separate job) (`yes | sdkmanager --licenses`)
Pull Request resolved: https://github.com/facebook/flipper/pull/362
Differential Revision: D13817430
Pulled By: passy
fbshipit-source-id: d8c95fc5b9202306dd50ea103b6e90142e73ef61
Summary:
Android SDK license SHA has been updated as of January 16, 2019 so it needs to be re-accepted. This is only needed for CircleCI since in Travis setup `sdkmanager` is used in order to accept the Licenses.
Pull Request resolved: https://github.com/facebook/flipper/pull/359
Differential Revision: D13751841
Pulled By: passy
fbshipit-source-id: f3d84277f06bedf06b7a766429d9f7e3275bb516
Summary:
Use CircleCI 2.1 for common executors and remove the common build step
as this is already done by Travis. Instead, focus on publishing either
snapshots or releases.
Pull Request resolved: https://github.com/facebook/flipper/pull/289
Reviewed By: jknoxville
Differential Revision: D10216413
Pulled By: passy
fbshipit-source-id: cfbc52c43187339ae6cb1c486d81e7c40216e86b
Summary:
Snapshots should only ever be published off of master.
Pull Request resolved: https://github.com/facebook/flipper/pull/288
Reviewed By: danielbuechele
Differential Revision: D10161974
Pulled By: passy
fbshipit-source-id: dca8463ff80de9d407758405c24e6511bef534d1
Summary:
On tags, build and publish artifacts to bintray. The encrypted accounted creds are for a `flipperfbbot` account on Bintray I created for this.
Pull Request resolved: https://github.com/facebook/flipper/pull/266
Reviewed By: priteshrnandgaonkar
Differential Revision: D9848181
Pulled By: passy
fbshipit-source-id: cf9150b2352a9ce972c48533ce15e8e75aa908fe
Summary:
This is so much faster! This should allow us to more easily publish snapshots.
Pull Request resolved: https://github.com/facebook/flipper/pull/257
Reviewed By: danielbuechele
Differential Revision: D9630067
Pulled By: passy
fbshipit-source-id: 64c633933a971cc15371d2ee90c184e13b98e06a
