CI/CD: Could you please explain your strategy?

Hi, I’m looking at your github action workflows, and was wondering what is your release strategy

In general I see on every push you run - name: Build debug and check

but then

name: Build release
if: github.ref != 'refs/heads/master'
run: ./gradlew bundleRelease assembleRelease -Ptivi.versioncode=$BUILD_NUMBER --scan

- name: Publish to Play Store
if: github.ref == 'refs/heads/master'
run: ./gradlew publishRelease -Ptivi.versioncode=$BUILD_NUMBER --scan

Which confuse me. Are you building release apk for every non master commit, and deploying a release on every commit in master?

Also, I was wondering how could I ssh my signing keystore into the CI server but thats probably moot point, and I see you have them checked in just encrypted, and keys from that are in github secrets, correct? Also they keys from the keystore are there too?

[chrisbanes]

Maybe run the bigger set of checks every night, or every 2 nights or something?

CircleCI has the manual approval feature, where you set certain tasks to only run if you press a button too: https://circleci.com/blog/manual-job-approval-and-scheduled-workflow-runs/ Not sure if GitHub Actions has that though.

[chrisbanes]

No, the cache system has the notion of partial keys when restoring the cache. If there’s not a full match it will fall back to the most recent cache.

I’d recommend reading the docs for the Cache action.