github
/
developer-roadmap
mirror of https://github.com/kamranahmedse/developer-roadmap.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update ci-cd.md (#5807)

Browse Source
feat/mobile
Sion Kang 6 months ago committed by Kamran Ahmed
parent 1bc3464102
commit d5249cc90e
1 changed files with 2 additions and 2 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Unified View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 4
      src/data/question-groups/backend/content/ci-cd.md

4
src/data/question-groups/backend/content/ci-cd.md
Unescape View File

@ -1,8 +1,8 @@
There are multiple considerations to have while setting up Continuous Integration and Continuous Delivery pipelines: There are multiple considerations to have while setting up Continuous Integration and Continuous Delivery pipelines:
- **Using source control** as the trigger for the entire process (git for example). The build pipelines for your backend services should get executed when you push your code into a specific branch. - **Using source control** as the trigger for the entire process (git for example). The build pipelines for your backend services should get executed when you push your code into a specific branch.
- **Pick the right CI/CD** platform for your needs, there are many out there such as GitHub, Gitlab CI, CircleCI and more. - **Pick the right CI/CD** platform for your needs, there are many out there such as GitHub Actions, GitLab CI/CD, CircleCI and more.
- Make sure you have **automated unit tests** that can be executed inside these pipelines. - Make sure you have **automated unit tests** that can be executed inside these pipelines.
- **Automatic deployment** should happen only if all tests are executed successfully, otherwise, the pipeline should fail, preventing broken code from reaching any environment. - **Automatic deployment** should happen only if all tests are executed successfully, otherwise, the pipeline should fail, preventing broken code from reaching any environment.
- **Use an artifact repository** such as JFrog Artifactory or Nexus Repository to store successfully built services. - **Use an artifact repository** such as JFrog Artifactory or Nexus Repository to store successfully built services.
- Finally, consider setting up a **rollback strategy** in case something goes wrong and the final deployed version of your service is corrupted somehow. - Finally, consider setting up a **rollback strategy** in case something goes wrong and the final deployed version of your service is corrupted somehow.

Write Preview
Loading…
Cancel
Save