Skip to content

Commit

Permalink
Update set-up-multiple-configuration-files-for-a-project.adoc (#9164)
Browse files Browse the repository at this point in the history
* Update set-up-multiple-configuration-files-for-a-project.adoc

* Add temo troubleshooting section

* Update jekyll/_cci2/triggers-overview.adoc

Co-authored-by: Rosie Yohannan <[email protected]>

* Update jekyll/_cci2/triggers-overview.adoc

Co-authored-by: Rosie Yohannan <[email protected]>

* fix formatting

---------

Co-authored-by: sebastian-lerner <[email protected]>
Co-authored-by: Rosie Yohannan <[email protected]>
3 people authored Jan 9, 2025

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
1 parent 6bdc7d1 commit be80751
Showing 1 changed file with 5 additions and 1 deletion.
6 changes: 5 additions & 1 deletion jekyll/_cci2/triggers-overview.adoc
Original file line number Diff line number Diff line change
@@ -48,6 +48,10 @@ TIP: If your code is integrated via **GitHub OAuth or Bitbucket Cloud**, you can

. Select **Run Pipeline** and you will see your new pipeline running in the web app.

=== Troubleshooting: "No suitable user credential could be found for user"

If you are seeing "No suitable user credential could be found for user" when triggering a pipeline from the CircleCI web app, navigate to menu:Project Settings[Pipelines > Add Pipeline > Authorize] and then attempt to run the pipeline again by selecting btn:[Trigger Pipeline].


[#run-a-pipeline-using-the-api]
== Trigger a pipeline using the API
@@ -109,7 +113,7 @@ curl -X POST https://circleci.com/api/v2/project/<project-slug>/pipeline/run \

. To trigger a pipeline from the command line using `curl`, copy and paste this sample request and replace the details in `< >` with your details, VCS can be `gh` or `bb`:
+
NOTE: If you are using CircleCI cloud, <your-circleci-hostname> should be `circleci.com`.
NOTE: If you are using CircleCI cloud, `<your-circleci-hostname>` should be `circleci.com`.
+
[source,shell]
----

0 comments on commit be80751

Please sign in to comment.