Pipeline info box with "Will deploy to $env" way too high on merge request page

Summary

I'm reporting a display issue with merge request page /merge_requests/NN. If you have a lot of jobs with differet "environments" they "deploy" to, the pipeline info box on the page gets very long.

Steps to reproduce

  1. Start a project on GitLab.com
  2. Create .gitlab-ci.yml file with a lot (20) jobs in a branch, each with:
  environment:
    name: $CI_JOB_NAME  # just an example that creates unique environment names per job
  1. Submit a merge request to master with the change. The problem appears on the merge request page.
  2. Merge the merge request into master. The problem gets worse as second "pipeline info box" (for master) appears.

I specualate this is a common pattern with microservice "monoreposioties" with a lot of individual microservice deployments.

Example Project

(I can provide if necessary)

What is the current bug behavior?

The merge request page header is unusably long, reading the actual content is tedious.

The problem is worsened by the fact that the "pipeline info box" is apparently loaded asynchronously (and with relatively large delay), so the page content (e.g. comments) "jump" after some tome.

The problem is worsened by the fact that the "Will deploy to $env" is displayed also for manual jobs that may never get run.

What is the expected correct behavior?

The merge request page is well usable even when there are a log of "deployable" jobs in the pipeline.

Relevant logs and/or screenshots

image

Output of checks

This bug happens on GitLab.com.

Possible fixes

This could be solved by e.g. making the "pipeline info box" collapsible (from some threshold) and/or collapsed by default (from some threshold)

/cc @knyttl

Assignee Loading
Time tracking Loading