diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-11-22 06:11:41 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-11-22 06:11:41 +0300 |
commit | 9ff55fb235c23c9260305f5a96e2a1af8fed8f19 (patch) | |
tree | 1c35b6f03664fea4ec5cc7924867c2252cea56be /doc/ci/components | |
parent | e3736bd03e55076fb8d9f5b4cc4602b32d13b2ec (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/ci/components')
-rw-r--r-- | doc/ci/components/index.md | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/ci/components/index.md b/doc/ci/components/index.md index 3d46ec5bbd5..f7c23964606 100644 --- a/doc/ci/components/index.md +++ b/doc/ci/components/index.md @@ -473,3 +473,17 @@ can be converted to a CI/CD component: or making it [more efficient](../pipelines/pipeline_efficiency.md). 1. Leverage the `.gitlab-ci.yml` in the components repository to [test changes to the component](index.md#test-the-component). 1. Tag and [release the component](index.md#release-a-component). + +## Troubleshooting + +### `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](catalog.md#add-a-components-repository-to-the-catalog): + +```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](#release-a-component). |