MSAMM
Back to course

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

Source control, and why a visual tool still needs it

Lesson 139 of 176 · 2 min

What is ACTUALLY STORED, what A DIFF LOOKS LIKE, and THE HISTORY THAT ANSWERS "WHEN DID THIS CHANGE". Module 2 Lesson 5 said every page is JSON you can read. This is what that makes possible, and it is the reason a visual tool still belongs in source control. WHAT IS STORED IS THE FILES BEHIND THE DESIGNER. Pages, flows, chains, variable declarations, connection definitions — all of it text, all of it committable. The tool is an editor over those files, so source control here works the way it works anywhere. A DIFF LOOKS LIKE STRUCTURED DATA RATHER THAN CODE, AND IT IS LESS READABLE THAN A CODE DIFF AND MUCH MORE USEFUL THAN NOTHING. A changed property, an added element, a reordered list. You will not read it comfortably; you can absolutely see WHERE something changed, which is most of the value. AND REORDERING IS THE ONE THAT…

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