You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're ramping down our BuildKite usage and this project is one of the few left on it. How much work would it be to migrate to GH Actions/similar so that CI was under your span of control?
The text was updated successfully, but these errors were encountered:
Florian14
added
T-Task
Refactoring, enabling or disabling functionality, other engineering tasks
z-CI
Z-Actions
Changes to the GitHub automation in .github/workflows/
labels
Nov 7, 2022
Buildkite is used at the moment by this project to:
build APKs on every pull requests. This is also done by GitHub action, and Buildkite is more used as a backup CI here. Ideally the existing GitHub action could provide an easy way to install the generated APK (by QR code, etc.), to replace the current script we have to download and install APK by providing a buildkite build number.
build release (unsigned) APKs for the PlayStore. A new GitHub action has to be created to do this work, every time the main branch is pushed. The release script will need to be updated to.
We're ramping down our BuildKite usage and this project is one of the few left on it. How much work would it be to migrate to GH Actions/similar so that CI was under your span of control?
The text was updated successfully, but these errors were encountered: