PR Deploy Time and Multiple Release Branches

[hype-kb]

Hello,
we are working with release branches in our Git repository, ie we have a continuous (potentially unstable) main branch from which we create a new release branch every few months. Deployments are only made from the release branches.
As far as I understand the PR Deploy Time is based on the commits between the current deployment and the previous deployment.

In our case the previous deployment can however be anything:
a) a deployment from a different branch or
b) a newer version of the same branch

Is scenario a) supported or is there a workaround possible? I assume we would need some kind of grouping (eg by _cicd_scope_id_ or by allowing more distinct values for _Environment')?
Update: Could we just send a different repo_url for each branch (we are sending deployment info via the webhook)? Or is the repo_url required to match repos.url ? (I just noticed that cicd_deployment_commits.repo_id is not filled even though the repo_url matches...)

Scenario b) might be even more difficult to solve - or is this covered already?

Best regards,
Ka

[dosubot[bot]]

Hello @hype-kb! I'm here to help you with any bugs, questions, or contributions you have. Let's tackle this together!

The current implementation of PR Deploy Time calculates the time between deployments by associating PRs with deployments through commit differences between consecutive deployments. However, handling deployments from different branches (scenario a) and newer versions of the same branch (scenario b) presents challenges.

For scenario a, you can customize the deployment tracking to support grouping by _cicd_scope_id_ or other identifiers. The code already includes logic to group successful deployments by cicd_scope_id, repo_url, and environment. You can extend this logic to include other identifiers by modifying the conditions in the grouping logic ^[1].

For scenario b, there is no specific information available on how the current system handles newer versions of the same branch being deployed. This might require additional customization or logic to track such deployments effectively.

Using the 'Environment' parameter can also help manage deployments from different branches by associating each branch with a specific environment, ensuring that deployments are tracked and managed accordingly ^[2][3].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}