diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-04-20 06:17:54 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-04-20 06:17:54 +0300 |
commit | e3523242123f949261d968ec942c6dc10ad6c772 (patch) | |
tree | 7a26983ed5e8866051ee3cd3e9085ad074164ff8 /doc/ci/resource_groups/index.md | |
parent | 8277a5b4ba05fe11174397c689c66cef5c06fc38 (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/ci/resource_groups/index.md')
-rw-r--r-- | doc/ci/resource_groups/index.md | 63 |
1 files changed, 63 insertions, 0 deletions
diff --git a/doc/ci/resource_groups/index.md b/doc/ci/resource_groups/index.md index 118c94b4d15..d00a92169f1 100644 --- a/doc/ci/resource_groups/index.md +++ b/doc/ci/resource_groups/index.md @@ -254,3 +254,66 @@ deploy: resource_group: production environment: production ``` + +### Jobs get stuck in "Waiting for resource" + +Sometimes, a job hangs with the message `Waiting for resource: <resource_group>`. To resolve, +first check that the resource group is working correctly: + +1. Go to the job details page. +1. Select **View job currently using resource**. +1. Check the job status: + - If the status is `running` or `pending`, the feature is working correctly. Wait until the job finishes and releases the resource. + - If the status is not `running` or `pending`, the feature might not be working correctly. + [Open a new issue](https://gitlab.com/gitlab-org/gitlab/-/issues/new) with the following information: + - The job ID. + - The job status. + - How often the problem occurs. + - Steps to reproduce the problem. + +You can also get job information from the GraphQL API. You should use the GraphQL API if you use pipeline-level concurrency control with cross-project/parent-child pipelines because the trigger jobs are not accessible from the UI. + +To get job information from the GraphQL API: + +1. Go to the pipeline details page. +1. Select the **Jobs** tab and find the ID of the stuck job. +1. Go to [GraphiQL explorer](../../api/graphql/index.md#graphiql). +1. Run the following query: + + ```graphql + { + project(fullPath: "<fullpath-to-your-project>") { + name + job(id: "gid://gitlab/Ci::Bridge/<job-id>") { + name + detailedStatus { + action { + path + buttonTitle + } + } + } + } + } + ``` + + The `job.detailedStatus.action.path` field contains the job ID using the resource. + +1. Run the following query and check `job.status` field according to the criteria above. You can also visit the pipeline page from `pipeline.path` field. + + ```graphql + { + project(fullPath: "<fullpath-to-your-project>") { + name + job(id: "gid://gitlab/Ci::Bridge/<job-id-currently-using-the-resource>") { + name + status + pipeline { + path + } + } + } + } + ``` + + If the status is not `running` or `pending`, open a new issue. |