ci: Distribute iOS artifacts via CI #45
Draft
+435
−852
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Untested, unfinished.
Various Buildkite commands failed when using Makefile commands as the current working directory is not persisted with each new line.
Ensure correct gem installation directory.
dcalhoun
force-pushed
the
ci/distribute-ios-artifacts-via-ci
branch
from
4d99306
to
9c258b0
Compare
Reduce network bandwidth.
dcalhoun
force-pushed
the
ci/distribute-ios-artifacts-via-ci
branch
from
061211c
to
bdc0ac4
Compare
Swift package manager cannot download the arbitrary binary file during package installation. Instead, we provide a helper script to be run by the consuming developer after installing the GutenbergKit Swift package.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
Distribute iOS artifacts via CI.
Why?
Closes https://github.com/Automattic/dotcom-forge/issues/9919. Avoid unnecessary code review of build output.
How?
Add a Buildkite CI task uploading the artifacts to an S3 bucket, with can then be downloaded by the Swift package.
Testing Instructions
N/A, no user-facing changes.
Acessibility Testing Instructions
N/A, no user-facing changes.
Screenshots or screencast
N/A, no user-facing changes.