Oracle Visual Builder: Applications That Outlive Their First Release · Module 14 · Source control, environments and publishing
Lab briefing · Promote and prove it is isolated
Lesson 147 of 176 · 3 min
Move an application BETWEEN TWO ENVIRONMENTS, complete THE CHECKLIST, and DEMONSTRATE IT CANNOT REACH THE SOURCE ENVIRONMENT. The third instruction is the lab. Promoting is a procedure; proving the old environment is unreachable is the only thing that establishes the promotion actually happened. MOVE SOMETHING WITH SEVERAL CONNECTIONS RATHER THAN ONE. A single-connection application is promoted correctly by accident. Two or three, with at least one address somewhere other than a connection — in a JavaScript function, or a link — is the realistic case, and it is Lesson 6's hunt in miniature. RUN LESSON 7'S CHECKLIST AND TICK IT LITERALLY, EVEN THOUGH YOU WROTE IT. The point of this lab is partly to find out how easy it is to do five of six while believing you did all of them. THEN PROVE THE NEGATIVE, WHICH IS THE HALF PEOPLE SKIP. The application working against the new environment proves…
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.
In this module: Module 14 · Source control, environments and publishing
- 1What a publish actually doesFree preview
- 2Versions, and living with two
- 3Source control, and why a visual tool still needs it
- 4Branching and more than one developer
- 5Environments, and what differs between them
- 6Making endpoints configurable
- 7The promotion checklist
- 8Rolling back
- 9Automating it
- 10What breaks: four promotion failures
- 11Lab briefing · Promote and prove it is isolated