Display all changes between two pipeline builds

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Update( Feb 9th 2024)

Based on our research, we don't have enough customer interest to build the UI. See suggestions for proposed workarounds.

Release notes

Problem to solve

When a pipeline executes, it only displays the commit that triggered the build. For the customer, nightly builds include multiple commits. Users want to see all the commits that happened between the nightly builds so that 1) When a bug is discovered - they (Simone) can quickly check if a change was made in the area where the bug was found 2) During the last stages of release - they (Rachel) want to confirm if only approved commits are making it through.

Proposal

A GUI display that provides the following

  1. List all the pipeline builds that have occured on this branch
  2. List all the changes between the prior build and the latest on this branch.

Workaround

  1. Use the Compare Branches feature (Example) (Note: We can potentially consider building a link to the page from the Pipeline Details page)
  2. Use the New Included Merge Requests per Deployment

Intended users

Simone

Rachel

Feature Usage Metrics

Does this feature require an audit event?

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.

Edited by 🤖 GitLab Bot 🤖