---
title: "Comment by Abhinav Sharma on \"Building CI/CD for Oracle APEX – Part 1: Why Exports Are Not Enough\" | Hashnode"
description: "The export-as-deployment-artifact model breaks the same way in a lot of stacks. Treating current state plus an event history as the source of truth makes diffs"
url: "https://hashnode.com/posts/building-ci-cd-for-oracle-apex-part-1-why-exports-are-not-enough/6ad91376d6efd7eaf6d3e0f1/comment/6ad91adfcdd62a63814fd366"
---

[Discussion](https://hashnode.com/posts/building-ci-cd-for-oracle-apex-part-1-why-exports-are-not-enough/6ad91376d6efd7eaf6d3e0f1)

Comment [Building CI/CD for Oracle APEX – Part 1: Why Exports Are Not Enough](https://hashnode.com/posts/building-ci-cd-for-oracle-apex-part-1-why-exports-are-not-enough/6ad91376d6efd7eaf6d3e0f1)

[Abhinav Sharma](https://hashnode.com/@abhinavs1920)

[Oct 21](https://hashnode.com/posts/building-ci-cd-for-oracle-apex-part-1-why-exports-are-not-enough/6ad91376d6efd7eaf6d3e0f1/comment/6ad91adfcdd62a63814fd366)

The export-as-deployment-artifact model breaks the same way in a lot of stacks. Treating current state plus an event history as the source of truth makes diffs reviewable instead of just regenerated.