У нас вы можете посмотреть бесплатно Automate Deployments With GitHub Actions CI/CD - Setting up Environments DEV, Prod. или скачать в максимальном доступном качестве, видео которое было загружено на ютуб. Для загрузки выберите вариант из формы ниже:
Если кнопки скачивания не
загрузились
НАЖМИТЕ ЗДЕСЬ или обновите страницу
Если возникают проблемы со скачиванием видео, пожалуйста напишите в поддержку по адресу внизу
страницы.
Спасибо за использование сервиса ClipSaver.ru
CI/CD pipelines using React, GitHub Actions, and Heroku. In this video We will be understanding the importance of CI CD, and we will implement CI CD setup on a brand-new project, which simulates how the projects are built at scale in Big Corporates and Startups. We will also see branches will be used to Test and QA the features without breaking the Production environment and enabling the smooth dev process. I will be using Heroku PaaS as the Platform to deploy our project and GitHub actions as the CI CD tool. CI/CD has three important terminologies that we need to understand before jumping into the code. Continuous integration is an automation process for engineers and developers that allows us to test new features in our code, making sure they work as expected. Continuous delivery comes next, ensuring that the new changes are well-tested, free of bugs, and ready to be deployed to the production environment. In the continuous deployment stage, changes to the application are deployed to production by merging to a specific branch, like master. Git and CI/CD strategy Let’s set up the CI/CD strategy for our example application. We’ll have one GitHub repository with two branches, master and develop. We’ll make a new feature branch from the develop branch, where we’ll develop a new feature and push those changes to its own feature. Then, we’ll create a pull request against the develop branch on GitHub. We’ll also have two CI/CD yml files for configuration, development and production. The development file is set up to trigger the CI/CD pipeline and deploy our changes to the Heroku development environment when we successfully merge a pull request into the develop branch. The production.yml file is set up to trigger a CI/CD pipeline for the production environment on Heroku when we pull the latest changes from the develop branch, merge develop into master, and finally push those changes to the remote master branch. References : https://blog.logrocket.com/ci-cd-pipe... https://github.com/marketplace/action... Profiles : LinkedIn: / saiprakash14 Twitter : / aseptemberguy GitHub : https://github.com/Saiprakashreddy14 Timestamps 0:00 Intro 2:22 What is CI CD 4:32 Start Project 24:30 Adding New feature