Skip to content

Remove Starter tier badge from Jenkins page

Craig Norris requested to merge docs-rem-starter-jenkins into master

What does this MR do?

The How to run Jenkins in development environment (on macOS) doc page is the last doc page that includes the **(STARTER)** EoS tier badge in the page title. As such, this MR only replaces this tier badge with the **(FREE)** tier badge, based on links to https://docs.gitlab.com/ee/integration/jenkins.html which has the Free tier badge.

Please confirm with the Ecosystem group that this page is associated with the appropriate tier, and make any needed changes as appropriate.

Author's checklist

To avoid having this MR be added to code verification QA issues, don't add these labels: feature, frontend, backend, ~"bug", or database

Review checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

  • If the content requires it, ensure the information is reviewed by a subject matter expert.
  • Technical writer review items:
    • Ensure docs metadata is present and up-to-date.
    • Ensure the appropriate labels are added to this MR.
    • If relevant to this MR, ensure content topic type principles are in use, including:
      • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
      • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
      • Any task steps should be written as a numbered list.
      • If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
  • Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
  • Ensure a release milestone is set.
Edited by Craig Norris

Merge request reports