CD/CI are methods frequently used to deliver apps to customers making use of automation into the stages of the app development. The main concepts attributed to CD and CI are Continuous Integration for CI and Continuous Delivery and/or Continuous Deployment for CD.
But even though all three are part of the software delivery process, each has its own requirements, and more importantly, benefits. So, understanding the differences between them it’s crucial to properly implementing them.
Hi! I'm Carlos, a student coursing the second year Bachelor's degree in Video Game Design and Development at UPC university. In this repository I'll capture my research about Automated builds CI+CD which I had to perform along this second semester.
I hope you enjoy it!
- What is CI/CD? -> https://www.redhat.com/en/topics/devops/what-is-ci-cd
- Intro to Continuous Integration, Continuous Delivery, and Continuous Deployment -> https://www.indellient.com/blog/whats-the-difference-between-continuous-integration-continuous-delivery-and-continuous-deployment/
- Continuous integration vs. delivery vs. deployment -> https://www.atlassian.com/continuous-delivery/principles/continuous-integration-vs-delivery-vs-deployment
- Understanding GitHub Actions -> https://docs.github.com/en/actions/learn-github-actions/understanding-github-actions
- How to Use Github Actions to Automate Your Repository Builds -> https://www.cloudsavvyit.com/15207/how-to-use-github-actions-to-automate-your-repository-builds/
- CI/CD for C/C++ games using GitHub Actions -> https://thatonegamedev.com/cpp/ci-cd-for-c-c-games-using-github-actions/
- How to automate the MSI Building with GitHub Actions -> https://www.youtube.com/watch?v=T_Rj3_M-m8I
- Introduction to Markdown: https://www.ionos.es/digitalguide/paginas-web/desarrollo-web/tutorial-de-markdown/