Our goal is to automate the SDLV (software develplment life cycle), to do this we have to separate the main goal into smaller ones.
- Firstly, we want to test our code works, thats what job one does.
- Secondly, we may be working with other developers so we will need to merge the codes collected in the repo if it works, this is what job two does.
- Thirdly, once we have our working code on the main branch we want to make it available to users, so we need to put the code onto an EC2 instance and run it. This is what job 3 does.
Continuous integration is the practice of frequently integrating code changes into a shared repository, ensuring early detection of integration errors and promoting collaboration among team members.
Continuous deployment is the automated process of releasing software changes into production environments after passing automated tests, enabling rapid and frequent delivery of updates to end-users.
A webhook is a mechanism that allows real-time communication between two applications, triggering events in one application based on actions or updates in another.
You would use Continuous Integration and Continuous Deployment (CI/CD) to automate software development processes, ensuring faster and more reliable delivery of updates, reducing manual errors, and improving overall efficiency.
Deploy is when the update or app goes live infront of users.
Delivered is using the scp/rsync command to get the update or app into production environment.
Delivery vs deploy depends on what business needs.
We would like to combine and test codes made by different developers quickly.To do this we would have to check the code works first then merge it to the main working branch.