’s Journey in Building and Deploying Frond-end Code
summary
Starts from ad hoc deployments, moves to an Angular CI/CD that served more than 700 modules and enforced a single build flavor, then to a Polymer/web‑component pipeline with a portal that deploys on every commit and tracks versions, using an ing web cli that proved too restrictive, and now to Azure DevOps templates plus custom tasks with migration ongoing; concrete results: per‑commit test deploys, visible component reuse, fewer full redeploys for library changes, and increased team autonomy and scalability.
AI-written summary · about
chapters (5)
related talks
47mCode and Deploy Angular to the Cloud
33mPractical AngularJS DevOps
16mBuilding ans scaling Angular apps on Azure
19mIn the Ocean of Angular Web Applications
19mDemystify module federation, and deployment strategy on AWS
23mFront-End Platform Engineering
05mMigrating a Portfolio of Front-End Apps to Angular
47mArchitecting for DevOps and Continuous Delivery
