Skip to content

[RHDEVDOC-7540] Remove Repository CR status field documentation #112326

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ochromy wants to merge 1 commit into
base: pipelines-docs-main
Choose a base branch
from
+0 −17
Open

[RHDEVDOC-7540] Remove Repository CR status field documentation #112326

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 0 additions & 17 deletions modules/op-monitoring-pipeline-run-status-using-pipelines-as-code.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,22 +54,5 @@ If {pac} matches a namespace to a `Repository` custom resource definition (CRD),

These error scenarios do not halt the execution of valid pipeline runs. The system continues to process validated and matched pipeline runs, preventing a single validation problem from disrupting the entire workflow.

*Status associated with Repository CRD*
{pac} stores the last 5 status messages for a pipeline run inside the `Repository` custom resource.

[source,terminal]
----
$ oc get repo -n <pipelines_as_code_ci>
----

.Example output
[source,terminal]
----
NAME URL NAMESPACE SUCCEEDED REASON STARTTIME COMPLETIONTIME
pipelines-as-code-ci https://github.com/openshift-pipelines/pipelines-as-code pipelines-as-code-ci True Succeeded 59m 56m
----

Using the `tkn pac describe` command, you can extract the status of the runs associated with your repository and its metadata.

*Notifications*
{pac} does not manage notifications. If you need to have notifications, use the `finally` feature of pipelines.