Why your CI/CD processes should include your ERP systems
summary
Claims that two-speed IT is an illusion because ERP acts as an enterprise backbone tied to microservices via APIs, so independent cadences (yearly, quarterly, monthly) force constant braking and surprise during integration. Recommends bringing ERP into CI/CD for ERP with automated pipelines, integration tests and a shared deployment cadence. Describes building synchronized pipelines and cross-system integration tests that reduce dependency friction, and reports that harmonized release cycles cut unexpected rollbacks and coordination overhead in trials.
AI-written summary · about
related talks
17mCI/CD - Build/Deploy Automation
59mBridging the Gap Between Ops and Developers with CI/CD
29mMastering Multi-Cloud ERP Integration
51mBetter software, faster: principles of Continuous Delivery and DevOps
23mCI/CD: Conscious Uncoupling
11mCreate unfair competitive advantage w/CI/CD Pipelines
38mCI is Essential but not Sufficient for an Effective Application Delivery Workflow
27mArchitect CI/CD on Enterprise level