Cross-project pipelines appear to be `Starter`
Description
It's been discovered during implementation of https://gitlab.com/gitlab-org/gitlab-ee/issues/8997 that cross-project pipelines do not have proper product tier checks.
trigger:
feature has been build on top of existing code
I'm a little confused, perhaps it was done on purpose. How should we proceed here?
Designs
- Show closed items
Relates to
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- Grzegorz Bizon added licensing 💌 + 1 deleted label
added licensing 💌 + 1 deleted label
- Contributor
I don't believe it was done on purpose. That said, you can do the same thing by curling the API, correct? It's the dashboards and visualizations around cross-project pipelines that are really the valuable part, esp. if the curling statement is true.
- Author Maintainer
@jlenny Yes, using
curl
andtrigger
is basically the same. The problem is that on the docs page https://docs.gitlab.com/ee/ci/multi_project_pipelines.html and our features comparison page https://about.gitlab.com/features/ we claim that this is aPremium
feature. - Contributor
I'd be ok with allowing the triggers to work in all cases, but have the cross-project views be premium. But it's @brendan 's call.
- Author Maintainer
It makes sense. I need to check if graphs are also in a wrong tier then.
- Contributor
I agree with @jlenny. That is in line with many of our other decisions around tiering.
- Cynthia "Arty" Ng marked this issue as related to #7366 (closed)
marked this issue as related to #7366 (closed)
- Maintainer
Setting devopsverify ~"group::ci and runner" based on ~"Verify".
- 🤖 GitLab Bot 🤖 added devopsverify grouppipeline execution labels
added devopsverify grouppipeline execution labels
- 🤖 GitLab Bot 🤖 mentioned in issue #13110 (closed)
mentioned in issue #13110 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue #13277 (closed)
mentioned in issue #13277 (closed)
- 🤖 GitLab Bot 🤖 added [deprecated] Accepting merge requests label
added [deprecated] Accepting merge requests label
- Jason Yavorska added Category:Continuous Integration label
added Category:Continuous Integration label
- 🤖 GitLab Bot 🤖 removed [deprecated] Accepting merge requests label
removed [deprecated] Accepting merge requests label
- 🤖 GitLab Bot 🤖 added Enterprise Edition label
added Enterprise Edition label
- Luca Kisielius added 1 deleted label and removed Category:Continuous Integration licensing 💌 labels
added 1 deleted label and removed Category:Continuous Integration licensing 💌 labels
- Luca Kisielius added Category:Continuous Integration label and removed 1 deleted label
added Category:Continuous Integration label and removed 1 deleted label
- Matija Čupić removed 1 deleted label
removed 1 deleted label
- 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 bridge pipelines label
added bridge pipelines 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
- Mark Nuzzo added typebug label
added typebug label
- 🤖 GitLab Bot 🤖 added vintage label
added vintage label
- Maintainer
Hi @grzesiek
👋 ,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
- Mark Nuzzo added severity3 label
added severity3 label
- Maintainer
Hi @grzesiek
👋 ,Based on the policy for inactive bugs, this issue is now being closed.
If you think this bug still exists, and is reproducible with the latest stable version of GitLab, please reopen this issue.
Thanks for your contributions to make GitLab better!
- 🤖 GitLab Bot 🤖 closed
closed
- 🤖 GitLab Bot 🤖 added auto closed label
added auto closed label
- 🤖 GitLab Bot 🤖 added Category:Pipeline Composition label
added Category:Pipeline Composition label