MSAMM
Back to course

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

The promotion checklist

Lesson 143 of 176 · 2 min

What to change AFTER MOVING AND BEFORE ANYBODY IS LET IN. SKIPPING ONE ITEM IS HOW PRODUCTION WRITES TO A TEST SYSTEM. The checklist is short and the reason it exists as a checklist rather than as knowledge is that promotions happen under time pressure and memory is the first thing to go. ENDPOINTS FIRST, AND VERIFY THEM RATHER THAN SETTING THEM. Every connection, checked in the running application against where it should point. Setting a value is an intention; opening a page and reading the request in the network tab is a fact. CREDENTIALS SECOND, AND THE CHECK IS THAT THE OLD ONES DO NOT WORK. A credential replaced is easy to confirm; a credential that was left and happens to be valid in both environments is exactly the case that passes every positive test. DATA THIRD: THE REFERENCE DATA THE APPLICATION NEEDS IS PRESENT, AND NOTHING SEEDED FOR…

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