You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Managing GIT repositories across multiple pillars-teams in Fusion Applications context

in Visual Builder 8 comments

Summary:

Need guidance on managing Visual Builder Studio .git files across pillars-teams converging on Production.

Content (please ensure you mask any confidential information):

Until recently Fusion Applications(FA) customers had one Visual Builder Studio (VBS) instance for Non-Production instances. With the advent of one VBS instance per FA instance the door has opened for more flexibility but centralized management/visibility on source code is not obvious.

Scenario: HCM, Finance-SCM and Production Support pillars each manage dedicated Fusion Applications instances inside a single tenancy. Ideally, we would like to identify a "master" VBS instance git repo in the tenancy to serve as the central git repository with which teams could clone from and merge to (not an "external" git reposiroty per se as all in the same tenancy) but could not find how to configure this topology.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!