2/2/2024 0 Comments Github actions![]() As we entered a period of growth within our technology organization, we were faced with a large influx of new developers. Lastly, a less tangible factor was minimizing the overall developer friction when using our CI/CD system. If we introduced a new step or patched a bug in the template, developers would have to regenerate the entire pipeline to pick up the change, which would erase any customizations they had made. We also had limited ability to preserve user customizations across upgrades to the pipeline templates. Our repository of shared scripts offered only limited encapsulation, and would muddle the build history of an application, intermingling commits to the actual application repo with commits to our shared task repo. One of the shortcomings of our current system was the effort involved in sharing common tasks in the CI/CD pipeline. Level-up your skills at QCon New York (June 13-15, 2023)! Uncover emerging trends and practices from domain experts. Despite this, we encountered limitations in our ability to provide a platform that balanced consistency with flexibility. Why We Are Moving to ActionsĪt Thrivent, we had invested considerable effort over recent years into improving the developer experience of our CI/CD tooling, including building out automation to quickly generate application pipelines from templates along established golden paths. Finally, Actions felt capable of providing a foundation for an enterprise CI/CD ecosystem. What truly made this feature ready for enterprise adoption though, was the announcement in January of 2022 of the ability to share actions internally, giving platform engineering teams the power to package and publish common reusable steps without exposing them to the world. ![]() Then, in November 2021, came the announcement of reusable workflows, greatly expanding the ability to provide reusable pipelines that reduced the number of duplicate steps and boilerplate code, coming closer to parity with many more established CI/CD products. Shortly after launch came the introduction of self-hosted runners, an essential capability for allowing jobs to execute within existing internal corporate networks. ![]() This was due in part to limitations present in the platform during its infancy, including restrictions around the execution and sharing of Actions internally within enterprises.įortunately, in the time since the initial unveiling, Actions has taken steps to break down some of the barriers toward maintainable enterprise use. However, despite the inherent appeal in the design of the Actions platform, many organizations, especially large enterprises with established CI/CD systems, were understandably hesitant to make a move. When GitHub Actions was announced in the fall of 2019, it drew immediate attention for ushering in " the third wave of CI/CD platforms." The unique approach of building composable pipelines from reusable open-source building blocks presented clear potential for improving the efficiency and maintenance of CI/CD pipeline operations. Catching Up with the Evolution of Actions
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |