GitLab Next

Summary

When expanding a child pipeline graph from the parent pipeline it does not refresh the jobs status anymore. If the child pipeline is not expanded the job statuses are refreshed correctly.

Steps to reproduce

In .gitlab-ci.yml:

job1:
  script:
    - sleep 30
job2:
  script:
    - sleep 50
child:
  trigger:
    include: child.yml
    strategy: depend

In child.yml:

child-1:
  script:
    - sleep 10
child-2:
  script:
    - sleep 30
child-3:
  script:
    - sleep 50

Run a pipeline and click on the downstream child pipeline to expand the graph. Notice that the jobs don't change status anymore. Collapsing the child pipeline graph does not reactivate the refresh either. You need to fully refresh the page.

I believe the same may occur when expanding multi-project downstream pipelines too.

When inspecting the network calls, on a complete page refresh the polling is used by the frontend and every 10 seconds calls pipeline.json to get fresh data. As soon as the child pipeline graph is expanded there are no network calls for the polling. It seems like frontend stops polling or does not reset it when expanded param is set.

What is the current bug behavior?

Pipeline graph stops refreshing jobs statuses for parent pipeline and the expanded downstream (child) pipeline.

What is the expected correct behavior?

Pipeline should refresh the statuses every 10 seconds according to the polling interval.

Relevant logs and/or screenshots