Gitlab-CI status 'running' when completed
Summary
Using DAG (Directed Acyclic Graph), CI status still running when the jobs are completed.
Example Code
the example code as attached => .gitlab-ci.yml
What is the current bug behavior?
What is the expected correct behavior?
Designs
- Show closed items
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#2 (closed)
mentioned in issue gitlab-org/quality/triage-reports#2 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#3 (closed)
mentioned in issue gitlab-org/quality/triage-reports#3 (closed)
added devopsverify grouppipeline execution severity3 typebug labels
- 🤖 GitLab Bot 🤖 mentioned in issue #198983 (closed)
mentioned in issue #198983 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue #198992 (closed)
mentioned in issue #198992 (closed)
- Maintainer
Setting Category:Continuous Integration based on ~"group::continuous integration".
- 🤖 GitLab Bot 🤖 added Category:Continuous Integration label
added Category:Continuous Integration label
- 🤖 GitLab Bot 🤖 mentioned in issue #201659 (closed)
mentioned in issue #201659 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue #204665 (closed)
mentioned in issue #204665 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue #206829 (closed)
mentioned in issue #206829 (closed)
- Crystal Poole added priority3 label
added priority3 label
- 🤖 GitLab Bot 🤖 mentioned in issue #207765 (closed)
mentioned in issue #207765 (closed)
- Jason Yavorska changed milestone to %Backlog
changed milestone to %Backlog
- 🤖 GitLab Bot 🤖 added [deprecated] Accepting merge requests label
added [deprecated] Accepting merge requests label
- Jason Yavorska added DEPRECATE_pipeline dag label
added DEPRECATE_pipeline dag label
- 🤖 GitLab Bot 🤖 added sectionops label
added sectionops label
- 🤖 GitLab Bot 🤖 added grouppipeline authoring + 1 deleted label and removed grouppipeline execution label
added grouppipeline authoring + 1 deleted label and removed grouppipeline execution label
- Developer
@furkanayhan can you link your MR for fixing this ~bug?
Collapse replies - Maintainer
- Maintainer
@dhershkovitch I guess it's solved now:
- example config in the issue description: https://gitlab.com/furkanayhan/test-project/-/blob/65145361fb8569809a37c44add69133d197fd402/.gitlab-ci.yml
- pipeline: https://gitlab.com/furkanayhan/test-project/-/pipelines/464947175
closing...
1
- Dov Hershkovitch removed Category:Continuous Integration label
removed Category:Continuous Integration label
- Furkan Ayhan mentioned in merge request !48077 (closed)
mentioned in merge request !48077 (closed)
- 🤖 GitLab Bot 🤖 added vintage label
added vintage label
- Maintainer
Hi @waldy
,Thanks for raising this bug.
Contributions like this are vital to help make GitLab a better product.
We would be grateful for your help in verifying whether your bug report requires further attention from the team. If you think this bug still exists, and is reproducible with the latest stable version of GitLab, please comment on this issue.
This issue has been inactive for more than 12 months now and based on the policy for inactive bugs, will be closed in 7 days.
Thanks for your contributions to make GitLab better!
- 🤖 GitLab Bot 🤖 added stale label
added stale label
- Furkan Ayhan closed
closed
- 🤖 GitLab Bot 🤖 added Category:Pipeline Composition label
added Category:Pipeline Composition label