![]() What we can do is maintain our own self-hosted runners, for which we can choose the hardware configuration. ![]() The problem is, GitHub Actions does not provide more powerful runners. On the graphics above we saw that our build time got significantly worse, but with a much less powerful VM, which seems totally coherent. The builds were significantly cheaper, but we had no plan to prioritize lower cost over a worse feedback loop on our pull requests. In particular, the gradle build step lasted around 16 minutes on GitHub Actions versus 7 minutes on Cloud Build. So I compared the performance of both, focusing on the time wasted on each workflow run and their cost.Ĭomparison between GitHub Action and Google Cloud Build for our workflowsĪs you can see, each build lasted about twice as long as previously □. Build timeĪs I said before, my first goal was to provide the team with a CI that would be at least as good as the former one. Instead, we just need to maintain one yaml file that defines the workflows, the runners it uses, the events that trigger it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |