Deployment Strategy Using Studio and GitHub Repository - Publishing in Global Scope

[Laurie Marlowe1]

Hello,

We have the following deployment strategy set up for custom scoped applications and want to do the same for global changes in order to peer review changes prior to promoting from the DEV branch to the TEST branch, and then moving to PROD branch, plus publishing to My Company Applications.  They way we have this set up does not seem to be ideal for the global scope.  Let me explain the set up:

• In GitHub there is a repository called Global Customizations with dev, test, and prod(main) branches.
• In Studio there is a scoped application called Global Customizations in the global scope.
• When catalog items and flows are created for the Service Catalog, we must set our scope to Global Customizations.
• When development is complete, we commit our changes to the DEV branch.
• We have a catalog item we submit to Promote & Deploy (via Cloudbees) to the TEST branch.
• When deployment is complete, we go into GitHub and request a review/approval from other team members.
• Once approved, we go into Studio in the TEST environment, and apply remote changes.
• UAT takes place in our test environment instance.
• Once UAT passes we submit the catalog item to Promote & Deploy (via Cloudbees) to the PROD branch.
• HERE'S WHERE WE HAVE THE ISSUE
• Back in Studio, in the TEST environment we switch the branch to PROD and apply remote changes (so everything is in Studio in the test instance.
• Then we publish in the test environment so the changes my be installed in our production instance from My Company Applications.

The issue is all the teams global changes to catalog items whether new or updated, are in the Global Customizations scope.  So when published EVERYTHING is published in one lump.  And EVERYTHING is published from My Company Applications.  EVERYTHING...and it is growing bigger, and bigger.  Let's say there are 50 catalog items in the Global Customizations - and each has a flow, client scripts, business rules, UI Policies, etc. (and it's growing constantly).

How can we do this differently, so we do not have to publish EVERYTHING each time?  We don't want a repository for each global change we make.  Breaking the Global Customizations scope could be broken into smaller new scopes, but I think it is just recreating what we have, and those will grow as well (plus having to decide which scope the new catalog items should go into).

We want to have Peer Reviews.

Another issue is I may publish and need to wait for the change window, and another team member may need to do the same, but for a different catalog item, but everything is in the one Global Customizations scope?

Thoughts?

Please and thank you in advance,

Laurie

[Noel6]

We have the same problem! Unfortunately i don't have any help for you..