CI/CD: Could you please explain your strategy?
See original GitHub issueHi, 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?
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
What Is CI/CD and How Does It Work? - Synopsys
CI and CD stand for continuous integration and continuous delivery/continuous deployment. In very simple terms, CI is a modern software development practice ...
Read more >CI/CD pipelines explained: Everything you need to know
Planning to implement CI/CD? This comprehensive guide explores the stages of a CI/CD pipeline, its pros and cons, best practices and more.
Read more >What is CI/CD? Continuous integration and ... - InfoWorld
CI/CD is a best practice for devops and agile development. Here's how software development teams automate continuous integration and delivery ...
Read more >CI/CD: Continuous Integration & Delivery Explained
CI/CD is a way of developing software in which you can release updates at any time without problems. Here's what it takes.
Read more >CI/CD: What Is It & Why Is It Important for DevOps?
Continuous integration (CI) is an automation strategy meant to solve the challenges of merge conflicts between individual developers' code and ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
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.
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.