MSAMM
Back to course

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

Rolling back

Lesson 144 of 176 · 3 min

Getting the previous version back QUICKLY, and THE USERS WHO ARE MID-TASK WHILE YOU DO IT. Every release needs an answer to "what if this is wrong", and the answer has to exist before it is needed rather than be worked out while a page is broken for everybody. THE MECHANISM IS THAT THE PREVIOUS VERSION STILL EXISTS AND CAN BE MADE LIVE AGAIN. Which is genuinely fast — and speed is the entire value, because a rollback happens while something is visibly wrong. SO THE FIRST RULE IS TO KNOW THE STEPS BEFORE YOU NEED THEM. Practise it once on something unimportant. Reading documentation while an application is broken is how a five-minute rollback becomes forty. THE SECOND IS THAT A ROLLBACK IS ANOTHER PUBLISH, WITH ALL OF LESSON 2'S CONSEQUENCES. Somebody is mid-task, and this time they are mid-task in a version that is about to be replaced…

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