Remove support for legacy CI triggers
For guidance on the overall deprecations, removals and breaking changes workflow, please visit https://about.gitlab.com/handbook/product/gitlab-the-product/#breaking-changes-deprecations-and-removing-features
Deprecation Summary
We officially deprecated legacy triggers in gitlab-ce%"10.0" (gitlab-ce#36748).
This issue is to schedule actual removal from the codebase. Legacy_triggers are no longer documented but if they are still being used this is a breaking change.
Breaking Change
Yes.
Affected Topology
Self Managed, SaaS
Affected Tier
- Free
- Premium
- Ultimate
Checklist
-
mention your stage's stable counterparts on this issue. For example, Customer Support, Customer Success (Technical Account Manager), Product Marketing Manager. -
@supadhyaya,@calebcooper,@jrreid@dzalbo,@jreporter- This is a breaking change for all users in %15.0 with likely no/little impact as legacy triggers haven't been able to be created since mid 2017 from what I can tell. - To see who the stable counterparts are for a product team visit product categories
- If there is no stable counterpart listed for Sales/CS please mention
@timtams - If there is no stable counterpart listed for Support please mention
@gitlab-com/support/managers - If there is no stable counterpart listed for Marketing please mention
@cfoster3
- If there is no stable counterpart listed for Sales/CS please mention
-
-
mention your GPM so that they are aware of planned deprecations. The goal is to have reviews happen at least two releases before the final removal of the feature or introduction of a breaking change.
Deprecation Milestone
%14.8 - This was previously announced but the removal was not completed as scheduled.