CI/CD tricks with Nx
summary
Nx detects affected projects and emits a JSON matrix that becomes one CI job per changed project, letting pipelines run only what changed. For Azure DevOps the pipeline prints affected apps, uses logging commands to save the matrix as a variable, publishes an artifact and fires downstream release pipelines via resource triggers; matrix entries can specify image/os (for example MacOS/Xcode for React Native), build tags and custom build commands. For CircleCI the setup workflow either injects JSON params or has NX generate a full dynamic config file so only needed workflows run.
AI-written summary · about
chapters (6)
- 0:00Introduction to CI/CD
- 1:30Pipeline Optimization
- 3:45Azure DevOps Strategies
- 6:00Azure Release Management
- 9:15CircleCI Dynamic Pipelines
- 10:52Conclusion and Q&A
related talks
52mFrontend, Backend, CI: Improve Your Devflow with Nx
29mThe One Repo To Rule Them All - Unleashing The Power Of Nx
43mNxify your Angular app
20mSpeed up your CI & Save the Environment
28mConsolidate, Enhance, Scale: End-to-End Angular Monorepo Management with Nx
49mModern CI/CD Pipeline with Azure DevOps
04h 00mNx Conf Lite 2022
16mBuilding ans scaling Angular apps on Azure