Dynamic baseline

[vio]

Problem

When comparing bundle analysis, the baseline report is the latest job corresponding to the base branch(ex: main branch).

For reports related to long-lived commits in a feature branch, commits in a branch checkout from other non-base branch, or for projects that rely on multiple base branches, the baseline can be different than the actual git change. As a result, the bundle analysis comparison can show irelevant differences:

For example:

• feature-b#commit-d is compared with the latest job in the base branch, main#commit-c". It should be compared with feature-b#commit-b`
• feature-a#commit-e is compared with the latest job in the base branch, main#commit-c". It should be compared with main#commit-a`

Solution

Extract the corresponding base branch and commit for a build, and try to infer the closest available baseline.

[vio]

Base branch support is now available for GitHub actions that run during pull_request events or on workflow_run triggered by a pull request. Job 4 corresponding to feature-b#commit D is now compared to the latest job in the base branch(feature-a branch).

To test it, you can use version @relative-ci/agent@5.1.0-beta.5 or relative-ci/agent-action@3.1.0-beta.5

[spaceemotion]

@vio hey there, we're currently using beta 4, but can't seem to find beta 5 for relative-ci/agent-action - is that an unreleased Github Action?

[vio]

@spaceemotion yes, relative-ci/agent-action@v3.1.0-beta.* are not stable releases. However, can you please give it another try now? We recently released beta.5 and the git tag was not properly set. Let me know if you still have issues.

[vio]

Dynamic baseline branch is now available on:

• https://github.com/relative-ci/agent/releases/tag/v5.1.0
• https://github.com/relative-ci/agent-action/releases/tag/v3.1.0