---
title: "Discussion on \"Building CI/CD for Oracle APEX – Part 5: From Selected Changes to Versioned Release Artifacts\" | Hashnode"
description: "Discussion on \"Building CI/CD for Oracle APEX – Part 5: From Selected Changes to Versioned Release Artifacts\". How I turn selected database differences into versioned SQL artifacts, with explicit targets, human review and a separate deployment decision."
url: "https://hashnode.com/posts/building-ci-cd-for-oracle-apex-part-5-from-selected-changes-to-versioned-release-artifacts/6b0013833f04dc7284001b25"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Building CI/CD for Oracle APEX – Part 5: From Selected Changes to Versioned Release Artifacts](https://davidpataki.com/building-ci-cd-for-oracle-apex-part-5-from-selected-changes-to-versioned-release-artifacts?utm_source=hashnode&utm_medium=feed)

How I turn selected database differences into versioned SQL artifacts, with explicit targets, human review and a separate deployment decision.

14h ago · 5 min read · davidpataki.com  
Read the article

-   [#oracle-apex](https://hashnode.com/tag/oracle-apex)
-   [#oracle-database](https://hashnode.com/tag/oracle-database)
-   [#cicd](https://hashnode.com/tag/cicd)
-   [#devops](https://hashnode.com/tag/devops)

## Written by

[David Pataki](https://hashnode.com/@enrol)

@enrol · Budaörs, Hungary

  
[View profile](https://hashnode.com/@enrol)

Oracle Database & APEX Consultant | Oracle ACE Pro

Oracle ACE Pro, founder of Enrol Consulting, and Oracle Database and APEX developer with more than two decades of experience building data-driven business applications. I write about Oracle Database, APEX, cloud and AI-assisted development.

## Responses 1

Markdown supported · ⌘↵ to post

[OneLifeVibe](https://hashnode.com/@onelifevibe)

[11h ago](https://hashnode.com/posts/building-ci-cd-for-oracle-apex-part-5-from-selected-changes-to-versioned-release-artifacts/6b0013833f04dc7284001b25/comment/6b003a8e8ec420b77d55cacd)

Separating approval from execution is the part I found most valuable. Too many pipelines treat a generated script as ready to run once it exists, and keeping a human decision between the artifact and the deployment is a sensible guard. I also liked the point that selecting a difference does not make it safe to deploy. Versioning the installer so reviewers can see exactly which version was current at each step gives the audit trail real meaning instead of just a file name.
