MSAMM
Back to course

Oracle Visual Builder: Applications That Outlive Their First Release · Module 14 · Source control, environments and publishing

Automating it

Lesson 145 of 176 · 3 min

When SCRIPTING A RELEASE STARTS TO PAY, and when A CHECKLIST SOMEBODY FOLLOWS IS STILL THE BETTER ANSWER. Automation is not automatically correct, and this is one of the places where the honest answer for a small estate is a piece of paper. THE CASE FOR AUTOMATION IS REPEATABILITY. A script does the same thing every time, cannot skip step five under pressure — Lesson 7's failure — and leaves a record of what it did. THE CASE AGAINST IS THAT IT IS SOFTWARE, AND SOFTWARE HAS TO BE MAINTAINED. A release script that has drifted from what a release now involves is worse than a checklist, because it runs confidently and does the wrong things. And nobody notices, because a release script is exercised rarely and read never. SO THE THRESHOLD IS FREQUENCY AND CONSEQUENCE RATHER THAN SOPHISTICATION. A release every few months, done by the person who built…

The full lesson is part of the course

The video, the complete written lesson and the module quiz are included in Oracle Visual Builder: Applications That Outlive Their First Release, with a certificate on completion and a fourteen-day refund window.

See the course and enrol9 free lessons

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 14 · Source control, environments and publishing

  1. 1What a publish actually doesFree preview
  2. 2Versions, and living with two
  3. 3Source control, and why a visual tool still needs it
  4. 4Branching and more than one developer
  5. 5Environments, and what differs between them
  6. 6Making endpoints configurable
  7. 7The promotion checklist
  8. 8Rolling back
  9. 9Automating it
  10. 10What breaks: four promotion failures
  11. 11Lab briefing · Promote and prove it is isolated