Set up release detection method

Boaz Dremer Updated by Boaz Dremer

Set up release detection method

LinearB uses 3 different methods to detect releases of code. By default LinearB regards tags as the indication of code released.

Tags

Without any additional configuration every commit that appears in a tagged branch will be considered as code that was released. If tags are used for other purposes as well, you will be able to set up a regular expression that indicates prefix/suffix of tag names that are used for releases. In this case only the tags that match the specified regular expression will be considered as releases.

In order to set up tags regular expression you will need to go to Settings -> Configure -> Release Detection and add the regular expression in the text box under "Use tags for releases"

PRs to a Dedicated Branch

The second method for detecting releases is for organizations that use a dedicated branch/es for releases and open a PR when merging. In this case every PR that is merged to this release branch is considered as released. In order to use this method the user should select the option "Detect my releases by Pull Requests to a dedicated branch" and should specify a regular expression that matches the branch/es that is used for releases. (By default the "release" branch is master)

Merges to a Dedicated Branch

The third method for detecting releases is for organizations that use a dedicated branch/es for releases. In this case every branch that is merged to this release branch is considered as released. In order to use this method the user should select the option "Detect my releases by direct merged to a dedicated branch" and should specify a regular expression that matches the branch/es that is used for releases. (By default the "release" branch is master)

How did we do?

Connect Github with a personal access token

Jira (cloud) connection guide

Contact