This article explains how to find the first real error when a pipeline shows failed, instead of running it again and again. After reading it, you can follow run detail, the failed job, and the log of the failed step, compare the exit code and Failure diagnosis , and tell apart an image pull, a checkout, a missing command, and a timeout. In the YAML, a task is a job: one group of steps that run in order. A runner is the program on a build machine that actually runs those steps.
Pipelines are available on Team and Enterprise. Community has no CI/CD menu, and the steps in this article do not apply there.
The screenshots use the pipeline mcp-sample-fail on the example repository xlliu/test-cicd-example , and its run #3 . This run was started by hand, on the runner priv-1 , at commit 98d2f2a . The failed job is named fail , and the step is named Fail on purpose . The step name shows this is a step that fails on purpose, so the log only has the checkout record and has no compile error.
1.…