From the course: Agile Software Development: Cloud Architecture

Unlock the full course today

Join today to access over 22,600 courses taught by industry experts or purchase this course individually.

Delivery process for the legacy application

Delivery process for the legacy application

From the course: Agile Software Development: Cloud Architecture

Start my 1-month free trial

Delivery process for the legacy application

- [Instructor] Let's review how the agile financial engineering team architected their code delivery pipeline for the agile core application. For source control, the team decided to retain their private GitHub repository. Since the AWS code pipeline integrates with GitHub, this was an easy choice. This was the source stage of the code pipeline. The code repository contain all the files needed to build the application's Docker image. Any code committed to the GitHub repository would trigger the build process, which is discussed next. For the build process, the engineering team was leaning towards retaining the existing Jenkins CI Build. This was technically feasible, because the build stage of code pipeline can point to Jenkin server to perform the build. But this approach would not solve the scalability issues the team had been facing. So the team switched to an alternate approach. For the build process, the team switched…

Contents