Skip to content
Snippets Groups Projects
Commit 289eedc1 authored by Sunjung Park's avatar Sunjung Park :speech_balloon: Committed by Miguel Rincon
Browse files

Update UI text replacing 'catalog resource' with 'catalog project'

- Modify relevant UI text to enhance readability and ensure terminology consistency.
- Minor adjustments in associated documentation to reflect the change.

Changelog: changed
parent 7f4a0178
No related branches found
No related tags found
1 merge request!146077Replace catalog resource with catalog/component project
......@@ -16,8 +16,8 @@ import { DEFAULT_SORT_VALUE, SCOPE } from '../../constants';
export default {
i18n: {
fetchError: s__('CiCatalog|There was an error fetching CI/CD Catalog resources.'),
countFetchError: s__('CiCatalog|There was an error fetching the CI/CD Catalog resource count.'),
fetchError: s__('CiCatalog|There was an error fetching CI/CD Catalog projects.'),
countFetchError: s__('CiCatalog|There was an error fetching the CI/CD Catalog project count.'),
},
components: {
CatalogHeader,
......
= render Pajamas::BadgeComponent.new(s_('CiCatalog|CI/CD catalog resource'), variant: 'info', icon: 'catalog-checkmark', class: css_class, href: href)
= render Pajamas::BadgeComponent.new(s_('CiCatalog|CI/CD Catalog project'), variant: 'info', icon: 'catalog-checkmark', class: css_class, href: href)
......@@ -207,24 +207,24 @@ Only public and internal projects are discoverable in the CI/CD Catalog.
To publish a component project in the CI/CD catalog, you must:
1. Set the project as a catalog resource.
1. Set the project as a catalog project.
1. Publish a new release.
#### Set a component project as a catalog resource
#### Set a component project as a catalog project
To make published versions of a component project visible in the CI/CD catalog,
you must set the project as a catalog resource.
you must set the project as a catalog project.
Prerequisites:
- You must have the Owner role in the project.
To set the project as a catalog resource:
To set the project as a catalog project:
1. On the left sidebar, select **Search or go to** and find your project.
1. Select **Settings > General**.
1. Expand **Visibility, project features, permissions**.
1. Turn on the **CI/CD Catalog resource** toggle.
1. Turn on the **CI/CD Catalog project** toggle.
The project only becomes findable in the catalog after you publish a new release.
......@@ -236,7 +236,7 @@ However, publishing a component's releases in the catalog makes it discoverable
Prerequisites:
- The project must:
- Be set as a [catalog resource](#set-a-component-project-as-a-catalog-resource).
- Be set as a [catalog project](#set-a-component-project-as-a-catalog-project).
- Have a [project description](../../user/project/working_with_projects.md#edit-project-name-and-description) defined.
- Have a `README.md` file in the root directory for the commit SHA of the tag being released.
- Have at least one [CI/CD component in the `templates/` directory](#directory-structure)
......@@ -269,7 +269,7 @@ is published to the CI/CD catalog. Tags must use semantic versioning, for exampl
### Unpublish a component project
To remove a component project from the catalog, turn off the [**CI/CD Catalog resource**](#set-a-component-project-as-a-catalog-resource)
To remove a component project from the catalog, turn off the [**CI/CD Catalog resource**](#set-a-component-project-as-a-catalog-project)
toggle in the project settings.
WARNING:
......@@ -558,11 +558,11 @@ You can learn more by following a practical example for [migrating the Go CI/CD
### `content not found` message
You might receive an error message similar to the following when using the `~latest`
version qualifier to reference a component hosted by a [catalog resource](#set-a-component-project-as-a-catalog-resource):
version qualifier to reference a component hosted by a [catalog project](#set-a-component-project-as-a-catalog-project):
```plaintext
This GitLab CI configuration is invalid: component 'gitlab.com/my-namespace/my-project/my-component@~latest' - content not found`
```
The `~latest` behavior [was updated](https://gitlab.com/gitlab-org/gitlab/-/issues/429707)
in GitLab 16.7. It now refers to the latest published version of the catalog resource. To resolve this issue, [create a new release](#publish-a-new-release).
in GitLab 16.7. It now refers to the latest published version of the catalog project. To resolve this issue, [create a new release](#publish-a-new-release).
......@@ -10542,10 +10542,10 @@ msgstr ""
msgid "CiCatalog|Back to the CI/CD Catalog"
msgstr ""
 
msgid "CiCatalog|CI/CD Catalog resource"
msgid "CiCatalog|CI/CD Catalog project"
msgstr ""
 
msgid "CiCatalog|CI/CD catalog resource"
msgid "CiCatalog|CI/CD Catalog resource"
msgstr ""
 
msgid "CiCatalog|Component ID not found, or you do not have permission to access component."
......@@ -10614,10 +10614,10 @@ msgstr ""
msgid "CiCatalog|There was a problem fetching the CI/CD Catalog setting."
msgstr ""
 
msgid "CiCatalog|There was an error fetching CI/CD Catalog resources."
msgid "CiCatalog|There was an error fetching CI/CD Catalog projects."
msgstr ""
 
msgid "CiCatalog|There was an error fetching the CI/CD Catalog resource count."
msgid "CiCatalog|There was an error fetching the CI/CD Catalog project count."
msgstr ""
 
msgid "CiCatalog|This project is no longer a CI/CD Catalog resource."
......@@ -67,7 +67,7 @@
it 'marks the project as a CI/CD Catalog' do
visit project_path(project_with_ci_components)
expect(page).to have_content('CI/CD catalog resource')
expect(page).to have_content('CI/CD Catalog project')
end
context 'and there are no releases' do
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment