badfrenzy.blogg.se - Github android studio tutorial

We got rid of what I identified as the main pain points of our former CI on Google Cloud Build : In terms of maintenance, the whole team found it easier to read, write and customize. As a result, the day to day developer experience remained the same, meaning that we didn’t miss anything we were used to. This first version of our brand new CI provided all the features our former CI did. Step back and analyse the results Features and maintenance Here are the steps of our former CI flow: 💡 If you are new to GitHub Actions, I recommend the official documentation or the Learning Lab. Each runner can run a single job at a time.

Runners: A runner is a server that runs your workflows when they’re triggered.

You can write your own actions, or you can find actions to use in your workflows in the GitHub Marketplace

Actions: a custom application for the GitHub Actions platform that performs a complex but frequently repeated task.

Events: An event is a specific activity in a repository that triggers a workflow run.

Each step is either a shell script that will be executed, or an action that will be run

Job: A job is a set of steps in a workflow that execute on the same runner.

Workflow: A workflow is a configurable automated process that will run one or more jobs.

GitHub Actions relies on 5 main concepts, that I will summarize here quoting the GitHub Actions documentation: Since we already had a workflow running our instrumented tests on GitHub Actions (my colleague Thibault wrote an article here) and our backend team’s CI/CD was also on this same platform, we quickly decided to go for this option. Discovering GitHub Actions and creating a first workflow

Our CI was back to its working state, but it was clear that we needed a better CI, that would be more reliable, that we could customize and use to effectively support our development processes. The developers who built them had already left the company, so it took a lot of digging to finally understand how it worked, what was broken and how to fix it. The CI relied on several Docker images but they weren’t really documented. However, new issues appeared, harder to understand than the first one. Fortunately, I quickly found a solution to fix this issue using the official CLI (Command Line Interface). A third-party service we used to distribute our releases ( AppCenter) changed its API and broke the curl calls that were used until then. It worked quite well, until… one day, it stopped working.

When I onboarded at Innovorder in September 2021, the Android team had a CI setup running on Google Cloud Build.