Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

upload to Google Play with GitHub Actions, remove Bitrise #4682

Merged
merged 8 commits into from
Oct 9, 2024

Conversation

connyduck
Copy link
Collaborator

@connyduck connyduck commented Sep 14, 2024

closes #4236

I hope I did everything correctly, we will find out after this is merged.

I am setting up the environment variables containing the keys so they are only available to actions that need them.

This should be easier to maintain, GitHub seems to be faster then Bitrise, and we no longer have two checks on every pull request.

@charlag
Copy link
Collaborator

charlag commented Sep 15, 2024

Looks good so far!


on:
push:
tags:
- '*'
pull_request:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
pull_request:
push:
branches:
- develop
pull_request:

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why? The action already that runs on develop already includes this action, this would run it twice?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You mean .github/workflows/populate-gradle-build-cache.yml? It has been deleted in this PR.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, I meant the deploy-test has uses: ./.github/workflows/check-and-build.yml and runs on develop, but it actually doesn't 😅
I'll fix that, thanks

- name: Copy CI gradle.properties
run: mkdir -p ~/.gradle ; cp .github/ci-gradle.properties ~/.gradle/gradle.properties

- name: Gradle Build Action
uses: gradle/gradle-build-action@v3
uses: gradle/actions/setup-gradle@v4
with:
cache-read-only: ${{ github.ref != 'refs/heads/main' && github.ref != 'refs/heads/develop' }}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
cache-read-only: ${{ github.ref != 'refs/heads/main' && github.ref != 'refs/heads/develop' }}

Comment on lines +19 to +27
- uses: r0adkll/sign-android-release@f30bdd30588842ac76044ecdbd4b6d0e3e813478
name: Sign Tusky Blue aab
id: sign_aab
with:
releaseDirectory: app/build/outputs/bundle/blueRelease
signingKeyBase64: ${{ secrets.KEYSTORE }}
alias: ${{ secrets.KEY_ALIAS }}
keyStorePassword: ${{ secrets.KEYSTORE_PASSWORD }}
keyPassword: ${{ secrets.KEY_PASSWORD }}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd prefer it if we don't touch the build.gradle files

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll address that in a separated PR.

Copy link
Collaborator

@Tak Tak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks reasonable to me? (I'm neither an expert in github actions nor in publishing to play store)

@connyduck
Copy link
Collaborator Author

Yeah, neither am I, I fully expect some kind of mistake but we will only know when we try it out.

@connyduck connyduck merged commit a04e95c into develop Oct 9, 2024
1 check passed
@connyduck connyduck deleted the migrate-to-gitlab-actions branch October 9, 2024 14:20
connyduck added a commit that referenced this pull request Oct 9, 2024
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.

Fully migrate Bitrise to GitHub Actions
4 participants