Using Jenkins to build your workloads
The developer tools provided by AWS can give you just about all the functionality that you need without any extra configuration or setup. There are instances where teams have already built parts of their Continuous Integration/Continuous Deployment (CI/CD) process around existing tooling and may want to retain some of the work that they have already poured time and effort into refining.
Teams that use the Jenkins server can be one of those cases. Along with its vast ecosystem of plugins, Jenkins can provide an extreme amount of functionality in the CI/CD process.
Many teams use Jenkins for the build stage of the CI process since, in Jenkins, it can feel easier to build the steps in shell scripts without a need to create additional buildspec
files.
The following diagram depicts Jenkins being used in conjunction with CodePipeline:
Jenkins itself...