Source code

Use Bitbucket to access and manage the source code of your applications.

Available resources

Guidewire provides a Bitbucket license. The number of licensed users depends on the number of developers in your cloud projects.

Guidewire doesn't preconfigure any Bitbucket plugins. You can request plugins from a list of supported plugins maintained by Guidewire. If a plugin isn't on the list, you can submit a case in Guidewire Community or a Jira ticket.

Roles and permissions

Access permissions to your Bitbucket projects depend on groups. For details, see Access Cloud Platform apps and services.

For details on how to set up your identity provider and create required groups, see Authentication.

To check the default permissions and how to customize them, see Repository settings.

Initial provisioning

As a part of the initial CI/CD provisioning, Guidewire creates a Bitbucket project for every logical star system.

This project contains source code and configuration repositories for all your applications. Guidewire creates the project name from the star system ID. For example, ABC for a star system with the abc ID.

Example

A tenant has two logical star systems:

• Car insurance for car insurance only.

• Property insurance for property insurance only.

For each of these two star systems, Guidewire creates a Bitbucket project:

• Car insurance for the Car insurance star system.

• Property insurance for the Property insurance star system.

For the car insurance line of their business, the tenant plans to develop PolicyCenter with claims Jutro app. Guidewire creates the following repositories for Car insurance star system:

PolicyCenter

Configuration

InsuranceConfiguration

claims

Repositories

Guidewire creates repositories for every Bitbucket project.

Source code repositories

For the {starsystemID} Bitbucket project, Guidewire creates the following repositories:

• For InsuranceSuite applications

  There's a separate repository for each of your applications: ClaimCenter, BillingCenter, ContactManager, or PolicyCenter.

• DigitalPortals

  Source code for EnterpriseEngage applications.

• Configuration

  For storing static analysis inspection profiles and runtime properties.

• GuidewireTestingFramework

  Source code of the testing framework.

• InsuranceConfiguration

  Used by Life Cycle Management (LCM) to store configuration.

Optional repositories, which Guidewire creates based on your contract:

• For Jutro applications

  There's a separate repository for each of your applications.

• DataMgmt

  Added when DataHub and InfoCenter are created and enabled as a single unit (DHIC extension).

Repository settings

You can customize repository settings so that they better fit your development practices. For details, see Repository settings.

Branches

During provisioning, Guidewire creates the following branches in source code repositories:

• refs/heads/develop

  Default branch where you can make changes to application code.

• refs/heads/gw-releases

  Branch where Guidewire pushes the source code for ski releases and patches.

• refs/heads/master

  Branch that stores the official source code and release history.

Unused branches

There's no limit to the number of branches in your Bitbucket projects. Guidewire recommends that you delete branches that you no longer use. When you delete unused branches, you reduce the number of branches that need to be transferred. You also limit the risk of problematic branches persisting. For example, branches with large binary files outside of Large File Storage (LFS).

Access Bitbucket

You can log into Bitbucket from Guidewire Home. You can access Bitbucket only from a dev star system. The code is available for deploying in pre-production and production star systems only through build promotion.

To access Bitbucket:

1. Select a dev star system.

2. From Apps, select Planets or select it from your pinned apps.

3. Select a planet.

4. Select the Source code link.

For details on using Bitbucket, see Bitbucket documentation.