If you ever need to go back in time, you may have difficulty deploying again. As a project evolves, its CI configuration may change. The biggest reason for this choice is history. In spite of my past experience with Jenkins and TeamCity and our team’s experience with AWS (CodePipeline/CodeDeploy), I chose GitLab CI to standardize these projects.
Today, we’re just going to focus on the CI part.
Some needed upgrades from Node.js 0.10, some needed code fixes, and most needed CI. Recently, I was tasked with doing various maintenance tasks on a number of internal tools/projects. That’s why we focus on using tools like CloudFormation, Serverless, and CI, as well as building other tools. At Trek10, we always try to consider the need for automation and repeatability with everything that we do.
0 kommentar(er)
