Skip to content

chore: add dependency code to prevent broken pipelines when implementing new public sector page feature

Megan Filo requested to merge 3978-eng-add-a-what-s-new-section-to-the-top-of-the-public-sector-site into main

Related to #3978

I need to add a new section to a solutions page. This requires a net new component, so I need to update the Solutions page build logic. Unfortunately, I cannot add a new component without breaking pipelines for everyone using draft content.

This MR adds a work around that, once merged, I can work without blocking the rest of our team.

Here is the Contentful entry for the new component link + it now uses the component name solutions-cta-showcase

Example of broken pipeline without this code: https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/jobs/7531469174#L1690

Note: This MR review app was built with the new component in draft. Once the build finished, I removed the new entry from Contentful so it wouldn't break future pipelines.

Review app of Public Sector page: https://3978-eng-add-a-what-s-new-section-to-the-top-of-the-public-sect.about.gitlab-review.app/solutions/public-sector/

Edited by Megan Filo

Merge request reports