Updating an Integration's Release
Repo Settings
- Repository URL: A link to the repository Bitbucket, Azure, or Github.
- Repository Tracking Branch: You can tell us the branch to track for releases. Every time we see this branched pushed we will create a new Release.
- Repository Path: Path to PANDIUM.yaml relative to the root of the repository. If left blank, we will look for the file in the root.
Upon running a normal sync, the source control looks for the URL paths in your repository denoted on your integrations. It will build a new release for the first integration in which it finds changes in the codebase. This sync can be set to run on a schedule but many prefer to run it manually as needed.
- 1.If you are working on one integration at a time, it might behoove you to use force build. First, run an init sync on your source control tenant. This will populate a list of all integrations in your account.
- 2.Click into the configurations of your source control tenant. Under 'force build' select the integration you would like to force build. Save the configurations.
- 3.On the source control tenant, select 'Force Build' under the sync options.
- 4.The force build sync will always create a new release of the integration you have selected to force build.
Upon navigating back to your selected integration's configuration page where you set your repository settings, you will see a "Default Release" selector. The default release will be the version of the integration that your customers will automatically be provisioned upon installing the integration from your marketplace. There must be a default release selected for your customers to install the integration.