- 3,741,934 Users
- 2,248,505 Discussions
- 7,862,083 Comments
- 5.1K All Categories
- 7 Introduce Yourself!
- 301 Community Feedback - NEW! (No Product Questions)
- 68 General Community Platform Concerns/Kudos/Feedback
- 56 Community Platform Bug Reports
- 67 How Do I Use the Community?
- 15 Where is the...? (Community Platform Locations)
- 11 Ideas and Suggestions for the Community Platform
- 65 Personal Document & Blog Archive
- 2 Community Programs
- 2 Get-Togethers
- 4.7K Certification Community
- 4.6K Certification Community Discussions
- 20 Oracle Certified Master Profiles
- 26 Oracle Database 12c Administrator Certified Master Profiles
- 41 Visual Builder Cloud Service
Two instance of VBS
We spun up two instances of OIC on different tenancies to isolate development and IDCS integration from our production OIC tenancy. With OIC, we have been using Visual Builder as you know to build applications and will move to VBS soon and centralize our team development. The challenge now is how do we centralize (if possible) our source code. Do we develop and check-in our code to our dev tenancy and then somehow run a build job to copy the source code to our production GIT tenancy and sync up the branches? Can the dev tenancy "reach" out to production tenancy? many organizations still have that "split" model of keeping dev in one place and production in another (I know how VB apps work in that there is dev|stage|publish, but I am speaking about source code here) and we want to follow this paradigm without getting into CLI tooling and use Visual Builder UI tools to make this happen.