Now, let’s walk through the flow, how it’s going to work, and what the advantages are before we implement it all. When a new code is pushed to a particular GIT repository/AWS CodeCommit branch, then following steps will take place:
- Jenkins will first build and then run the test cases (Jenkins listening to a particular branch through Git webhooks).
- If the test cases fail, it will notify us and stop the further after-build actions.
- If the test cases are successful, it will go to post-build action.
In our case, the application is ready to be deployed and is merged with the master branch of the application. So, Jenkins will pull the latest revision and build it.
- Later on, Jenkins will push the latest code in the zip file format ...
