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.

Android studio github integration