企业🤖AI智能体构建引擎,智能编排和调试,一键部署,支持私有化部署方案 广告
# Troubleshooting CI/CD > 原文:[https://docs.gitlab.com/ee/ci/troubleshooting.html](https://docs.gitlab.com/ee/ci/troubleshooting.html) * [Merge request pipeline widget](#merge-request-pipeline-widget) * [“Checking pipeline status”](#checking-pipeline-status) * [Merge request ability to merge widget](#merge-request-ability-to-merge-widget) * [“A CI/CD pipeline must run and be successful before merge”](#a-cicd-pipeline-must-run-and-be-successful-before-merge) # Troubleshooting CI/CD[](#troubleshooting-cicd "Permalink") ## Merge request pipeline widget[](#merge-request-pipeline-widget "Permalink") 合并请求管道小部件在"合并请求"中显示有关管道状态的信息. [在合并小部件](#merge-request-ability-to-merge-widget)的[合并请求功能](#merge-request-ability-to-merge-widget)上方显示. 根据管道的状态,可以显示几条消息. ### “Checking pipeline status”[](#checking-pipeline-status "Permalink") This message is shown when the merge request has no pipeline associated with the latest commit yet and [Pipelines must succeed](../user/project/merge_requests/merge_when_pipeline_succeeds.html#only-allow-merge-requests-to-be-merged-if-the-pipeline-succeeds) is turned on. This might be because: * GitLab 尚未完成创建管道. * 您正在使用外部 CI 服务,但 GitLab 尚未收到该服务的回音. * 您没有在项目中使用 CI / CD 管道. 创建管道后,该消息将更新为管道状态. 注意:当前,如果您删除合并请求的最新管道,则将显示此消息,而不是有意义的错误消息. 这是一个已知问题,应尽快解决. ## Merge request ability to merge widget[](#merge-request-ability-to-merge-widget "Permalink") 合并请求状态窗口小部件显示" **合并"**按钮以及合并请求是否准备就绪. 如果合并请求无法合并,则会显示原因. 如果管道仍在运行,则将" **合并"**按钮替换为" **管道成功后合并"**按钮. 如果[**合并火车**](merge_request_pipelines/pipelines_for_merged_results/merge_trains/index.html)被启用,按钮要么**加入到合并列车**或**添加到合并火车时管道成功** . ### “A CI/CD pipeline must run and be successful before merge”[](#a-cicd-pipeline-must-run-and-be-successful-before-merge "Permalink") 如果在项目中启用了" [管道必须成功"](../user/project/merge_requests/merge_when_pipeline_succeeds.html#only-allow-merge-requests-to-be-merged-if-the-pipeline-succeeds)设置,并且管道尚未成功运行,则会显示此消息. 如果尚未创建管道,或者正在等待外部 CI 服务,则这也适用. 如果您的项目不使用管道,则应禁用**管道必须成功**才能接受合并请求.