support-reviewed:2023-04-18 LG

This article describes how to enable debug mode when using the Codefresh CLI for pipeline management.

Enabling the`debug` mode provides detailed output helping you to understand the reasons for potential issues.

When you're running commands using Codefresh CLI you may face some issues related to:

Debig mode is useful when facing issues related to:

* Authentication

* Network access, such as connectivity to the Codefresh platform

* Delays or errors during command execution, as when running a pipeline locally

* Authentication problems

* Network-related issues (e.g.: trying to reach Codefresh platform)

* Delays or errors executing a command (e.g.: running a pipeline locally)

Make sure you have the[latest version of the CLI](https://codefresh-io.github.io/cli/installation/){:target="\_blank"}.

1. Enable the`debug` mode for the Codefresh CLI: to do so, you need to initialize the`DEBUG` environment variable as follows:

1. Initialize the`DEBUG` environment variable:

DEBUG=codefresh*

```

2. Run the Codefresh CLIcommand you would like to debug. For example:

1. Run the Codefresh CLIcommand you want to debug.

For example:

(or any other Codefresh CLI command)

3. You will get an output similar to this:

1. Analyze the output to identify issues.

Below is an example of CLIcommand outputin debug mode.


>**_Note:_**

>If after reviewing the output provided by the debug mode you're still unable to fix the issue, please include that output in a ticket. That way the Support Team will be able to help you.

{{site.data.callout.callout_tip}}

**TIP**

If after analyzing the debug output you're unable to resolve the issue, please submit a ticket to Codefresh Support, including the output details.

* [Codefresh CLI Installation and upgrade process](https://codefresh-io.github.io/cli/installation/) (it's important to keep your Codefresh CLI up to date)

support-reviewed:2023-04-18 LG

You need to option to stop status update to github from a pipeline

To disable status updates to Github, please follow these steps (it's currently supported only via CLI):

Disabling status updates to GitHub is currently supported only via CLI for Codefresh pipelines.

2. Authenticate the CLI to your Codefresh account:<https://codefresh-io.github.io/cli/authentication/>

* Install the CLI](https://codefresh-io.github.io/cli/installation/){:target="\_blank"}

*[Authenticate the CLI to your Codefresh account](https://codefresh-io.github.io/cli/authentication/){:target="\_blank"}

4. Add the options section under`spec`, set`enableNotifications: false` and save the changes. The updated YAML should look like this:

1. Export the full pipeline spec as a YAML file:

`codefresh get pipeline <project_name/pipeline_name> -o yaml > pipeline_name_spec.yaml` to

1. Below`spec`, add`options` and then add`enableNotifications: false`, as in the example below.

version:'1.0'

options:

enableNotifications:false

title:"How To:Ensure Clean Up CommandsAlwaysRun If a Pipeline Is Manually Stopped"

title:"How To: Alwaysrun clean-up commands after pipeline execution"

description:

group:kb

sub-group:articles

support-reviewed:2023-05-04 LG

Sometimes you might want to run code at the end of every pipeline (eg to clean up resources) regardless of success, failure, or the pipeline is manually stopped.

When working with a sequential (default) pipeline, you will find that manually stopping a pipeline halts the entire pipeline - including any pipeline hooks set to run on_success or on_failure[1]. However, if you switch the entire pipeline work in parallel[2], you can use the below step as a template to ensure that your clean up code will always run:

The parallel step always runs at the end of the pipeline, regardless of its build status, or if the pipeline was manually terminated.

In a sequential pipeline, which is the default execution mode for pipelines, manually terminating the pipeline, also terminates the execution of subsequent steps, including any pipeline hooks set to run on success or failure.

You can circumvent this behavior by inserting a parallel step within the pipeline.

* Add the step below as a template to ensure code clean-up will always run:

cleaner_always_executed:

buildSuccess:workflow.result == 'success'

title:"How To: FindPipelines Using a SpecificGitIntegration"

title:"How To: Findpipelines using specificGitintegration"

description:

group:kb

sub-group:articles

support-reviewed:2023-04-18 LG

You have an old git context and are unabletodelete theintegration. Or you wanttomigrate to a new GitIntegration.

This article describes howtouse theCodefresh CLItofind pipelines with legacy Gitcontexts.

You need JQuery installed for the command below.

Run the following CLI command to get the names of pipelines that reference the Git Integration for a Trigger, using to get YAML from Repository, or specified in a git-clone step while using an Inline YAML. You will need to have JQ installed for this to work.

Get the names of pipelines that reference the Git integration for a trigger.

The command below supports pipelines with source YAMLs from Git repositories, or those that reference the Git integration in a`git-clone` step with inline YAML.

* Run:

codefresh get pip --limit 100 -o json|\

jq --arg v"GIT_INTEGRATION" -r'.[] | select(contains({"spec":{"triggers":[{"type":"git", "context":$v}]}}) or contains({"spec":{"specTemplate":{"context":$v}}}) or contains({"spec":{"steps":$v}})) | .metadata.name'

[Creating a pipeline]({{site.baseurl}}/docs/pipelines/pipelines/#creating-a-pipeline)