Skip to content

Add new pkg-registry-deploy job

Dillon Louden requested to merge djloude/buyer-experience:feature-provide-build-artifact-for-offline-deployment into main

Step 1: What is changing in this MR?

Added a new CI job pkg-registry-deploy that depends on the production-deploy job and simply takes the full public directory which contains the about.gitlab.com website built html files, compresses and publishes them as a generic package in the projects package registry. This MR is to aid self-hosted GitLab users that are behind extreme firewalls or conduct work in an offline environment easy access to obtain and deploy the about.gitlab.com site within their own network. The two largest driving factors of this are The Pricing page with supported features by license tier and the consistently updated Blog written by GitLab experts!

The added job is created in a way that allows easy modification and supports standard CI_JOB variables allowing the public.tar.gz directory be published to the package registry on specific tags, commits or any build. This can also allow for package overwriting in an effort to save space in the registry!

Thank you in advance for the consideration!

Step 2: Ensure that your changes comply with the following, where applicable:

  • I, the Assignee, have run Axe tools on any updated pages, and fixed the relevant accessibility issues.
  • These changes meet a specific OKR or item in our Quarterly Plan.
  • These changes work on both Safari, Chrome, and Firefox.
  • These changes have been reviewed for Visual Quality Assurance and Functional Quality Assurance on Mobile, Desktop, and Tablet.
  • These changes work with our Google Analytics and SEO tools.
  • These changes have been documented as expected.

Step 3: Add the appropriate labels for triage

This MR will have dex-approval::2-standard automatically applied, but please update it as follows. If deciding between two levels, go with the higher of the two: https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/sites/handbook/source/handbook/marketing/digital-experience/marketing-site-approval-process/index.html.md

Step 4: Tag the appropriate person for review

Depending on which label is used, you may tag the following people as a Reviewer on this MR: https://about.gitlab.com/handbook/marketing/digital-experience/marketing-site-approval-process/#step-3-tag-the-appropriate-people-for-review

Merge request reports