Skip to content

Commit 4c0d196

Browse files
update troubleshooting docs (circleci#8913)
* Update pipelines.adoc * move troubleshooting to snippet and add whole snippet to pipelines page --------- Co-authored-by: Rosie Yohannan <[email protected]>
1 parent 951e378 commit 4c0d196

File tree

2 files changed

+24
-2
lines changed

2 files changed

+24
-2
lines changed

jekyll/_cci2/pipelines.adoc

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -170,6 +170,11 @@ image::/docs/assets/img/docs/vs_code_extension_job-details.png[Screenshot showin
170170

171171
The CircleCI VS Code extension is available to download on the link:https://marketplace.visualstudio.com/items?itemName=circleci.circleci[VS Code marketplace.]
172172

173+
[#troubleshooting]
174+
== Troubleshooting
175+
176+
include::../_includes/snippets/troubleshoot/pipelines-troubleshoot-snip.adoc[]
177+
173178
[#next-steps]
174179
== Next steps
175180

jekyll/_includes/snippets/troubleshoot/pipelines-troubleshoot-snip.adoc

Lines changed: 19 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,18 @@
1+
=== Config could not be located error
2+
3+
If you see the following error message, check the steps below to remediate the issue.
4+
5+
[,shell]
6+
----
7+
config file .circleci/sample-filename.yml could not be located on branch sample-branch-name in repository sample-repo-name
8+
----
9+
10+
* Ensure that there is a CircleCI configuration file in the repository on the branch that uses the filename specified in the error message. If there is not one present, add a CircleCI configuration file.
11+
12+
* If there is a config file present:
13+
.. Navigate to menu:Project Settings[Pipelines] in the CircleCI web app for the project where you are seeing this error message.
14+
.. Select the pencil icon for each pipeline listed and ensure that the "Config File Path" field matches the filepath of the config file that is in your repository. If you changed the name of the config file in your repository, the reference to that filepath must also be changed in the menu:Project Settings[Pipelines] section for any pipeline that uses that configuration file.
15+
116
[#why-is-my-scheduled-pipeline-not-running]
217
=== Why is my scheduled pipeline not running?
318

@@ -22,9 +37,9 @@ After checking your `.circleci/config.yml` for formatting errors, search for you
2237
A job might end up being queued because of a concurrency limit being imposed due your organization's plan. If your jobs are queuing often, you can consider link:https://circleci.com/pricing/[upgrading your plan].
2338

2439
[#why-are-my-jobs-queuing-performance-plan]
25-
=== Why are my jobs queuing even though I am on the Performance plan?
40+
=== Why are my jobs queuing even though I am on the Performance Plan?
2641

27-
In order to keep the system stable for all CircleCI customers, we implement different soft concurrency limits on each of the xref:configuration-reference#resourceclass[Resource classes]. If you are experiencing queuing on your jobs, it is possible you are hitting these limits. Please link:https://support.circleci.com/hc/en-us/requests/new[contact CircleCI support] to request raises on these limits.
42+
In order to keep the system stable for all CircleCI customers, we implement different soft concurrency limits on each of the xref:configuration-reference#resourceclass[Resource classes]. If you are experiencing queuing on your jobs, it is possible you are hitting these limits. link:https://support.circleci.com/hc/en-us/requests/new[Contact CircleCI support] to request raises on these limits.
2843

2944
[#find-project-projects-dashboard]
3045
=== Why can I not find my project on the Projects dashboard?
@@ -36,13 +51,15 @@ If you are not seeing a project you would like to build, and it is not currently
3651

3752
CircleCI currently supports pulling (and pushing with Docker Engine) Docker images from link:https://hub.docker.com/[Docker Hub]. For link:https://hub.docker.com/explore/[official images], you can pull by simply specifying the name of the image and a tag:
3853

54+
[,yml]
3955
----
4056
golang:1.7.1-jessie
4157
redis:3.0.7-jessie
4258
----
4359

4460
For public images on Docker Hub, you can pull the image by prefixing the account or team username:
4561

62+
[,yml]
4663
----
4764
my-user/couchdb:1.6.1
4865
----

0 commit comments

Comments
 (0)