Authorized user email addresses

To retrieve the list of email addresses, complete the following steps:

1. Open the resource list.
2. Select Developer tools.
3. Click the Continuous Delivery service instance of interest.
4. Select Manage > Authorized users.
5. Select and copy the contents of the table of email addresses to the clipboard, and paste to a plain text file.

For more information about managing authorized users, see Plan limitations and usage.

Toolchain configurations

You can retrieve a list of toolchains and their configurations by using the Toolchain API, specifically the methods to Get a list of toolchains or Get a toolchain. To retrieve toolchain configuration data, complete the following steps:

1. GET https://resource-controller.cloud.ibm.com/v2/resource_groups to retrieve a list of resource groups in the account.
2. For each resource group, GET https://api.$REGION.devops.cloud.ibm.com/toolchain/v2/toolchains?resource_group_id=$RG_ID to retrieve the list of toolchains in the resource group.

You can also retrieve a subset of Toolchain resource metadata by using the Global Search API or the Resource Controller API.

Tool integration configurations

You can retrieve tool integration configuration data by using the Toolchain API, specifically the methods to Get a list of tools bound to a toolchain and to Get a tool. To retrieve tool integration configuration data, complete the following steps:

1. For a specific toolchain, use GET https://api.$REGION.devops.cloud.ibm.com/toolchain/v2/toolchains/$TOOLCHAIN_ID/tools to retrieve configuration details for all tool integrations in the toolchain.

You cannot retrieve secret properties from Continuous Delivery. Some of the properties of a tool integration configuration are secrets, such as access tokens, API keys, and passwords. It's a best practice to configure these properties by reference to a secrets store, such as Secrets Manager. In this case, the API returns strings that reference the locations of the properties in their secrets stores. If secret property values are stored directly in a tool integration configuration, the API doesn't return the secret values, only a hash of the value for information security.

Tekton pipelines

You can retrieve a list of Tekton pipelines that are integrated into a toolchain by using the Toolchain API. To retrieve the list of Tekton pipelines, complete the following steps:

1. For a specific toolchain, use GET https://api.$REGION.devops.cloud.ibm.com/toolchain/v2/toolchains/$TOOLCHAIN_ID/tools to obtain a list of all tool integrations in the toolchain.
2. Use a tool such as jq to filter the list to only pipeline tool integrations, and to derive the corresponding pipeline IDs.
   • Use the following command to produce a list of IDs for all Tekton and Classic pipelines in a toolchain: curl -s -X GET -H "Authorization: Bearer $TOKEN" -H "Accept: application/json" https://api.$REGION.devops.cloud.ibm.com/toolchain/v2/toolchains/$TOOLCHAIN_ID/tools | jq -r '.tools[] | select(.tool_type_id == "pipeline").id'
   • Use the following command to produce a list of IDs for all Tekton pipelines in a toolchain: curl -s -X GET -H "Authorization: Bearer $TOKEN" -H "Accept: application/json" https://api.$REGION.devops.cloud.ibm.com/toolchain/v2/toolchains/$TOOLCHAIN_ID/tools | jq -r '.tools[] | select(.tool_type_id == "pipeline" and .parameters.type == "tekton").id'
   • Use the following command to produce a list of IDs of all Classic pipelines in a toolchain: curl -s -X GET -H "Authorization: Bearer $TOKEN" -H "Accept: application/json" https://api.$REGION.devops.cloud.ibm.com/toolchain/v2/toolchains/$TOOLCHAIN_ID/tools | jq -r '.tools[] | select(.tool_type_id == "pipeline" and .parameters.type == "classic").id'

Tekton pipeline configurations

You can retrieve the configuration of a Tekton pipeline, including its definitions, properties, triggers, and trigger properties, by using the Tekton Pipeline API, specifically the method to Get Tekton pipeline data.

To work with Classic pipelines, see Classic pipeline configurations.

To retrieve configuration data about a Tekton pipeline, complete the following step:

1. For a specific Tekton pipeline, use GET https://api.$REGION.devops.cloud.ibm.com/pipeline/v2/tekton_pipelines/$TEKTON_PIPELINE_ID to retrieve the configuration of the pipeline.

Responses from this method do not include pipeline runs. To retrieve data about pipeline runs, see Tekton pipeline runs.

Tekton pipeline runs

Pipeline run data is the result of running, not configuring, pipelines. It is not considered essential to implementing pipeline workloads with different service providers or on-premises software. Therefore, this section is included as a convenience, not as a requisite of data portability.

You can retrieve metadata about pipeline runs by using the Tekton pipeline API method to List pipeline run records.

1. For a specific Tekton pipeline, use GET https://api.$REGION.devops.cloud.ibm.com/pipeline/v2/tekton_pipelines/$TEKTON_PIPELINE_ID/pipeline_runs to retrieve a list of pipeline runs.

The response includes detailed information about pipeline runs, except for pipeline logs. To retrieve pipeline logs, see Tekton pipeline logs.

Tekton pipeline logs

Pipeline run logs result from running, not configuring, pipelines. They are not considered essential to implementing pipeline workloads with different service providers or on-premises software. Therefore, this section is included as a convenience, not as a requisite of data portability.

You can retrieve pipeline logs by using Tekton pipeline API methods to Get a list of pipeline run log objects and to Get the log content of a pipeline run step.

To retrieve logs, complete the following steps:

1. For a specific Tekton pipeline, use GET https://api.$REGION.devops.cloud.ibm.com/pipeline/v2/tekton_pipelines/$TEKTON_PIPELINE_ID/pipeline_runs/$RUN_ID/logs to retrieve a list of pipeline run log descriptors, including log descriptor IDs.
2. For a specific log descriptor, use GET https://api.$REGION.devops.cloud.ibm.com/pipeline/v2/tekton_pipelines/$TEKTON_PIPELINE_ID/pipeline_runs/$RUN_ID/logs/$LOG_ID to return the log contents.

Classic pipeline configurations

You can retrieve the configuration of a Classic pipeline by using the ibmcloud dev pipeline-get CLI. This CLI is for Classic pipelines only. To work with Tekton pipelines, see Tekton pipeline configurations.

To retrieve the configuration of a Classic pipeline, complete the following steps:

1. For a specific Classic pipeline, run ibmcloud dev pipeline-get $CLASSIC_PIPELINE_ID --output JSON.

Classic pipeline runs

Pipeline run data is the result of running, not configuring, pipelines. It is not considered essential to implementing pipeline workloads with different service providers or on-premises software. Therefore, this section is included as a convenience, not as a requisite of data portability.

To produce Classic pipeline run data, trigger a run. You can trigger a run by using the ibmcloud dev pipeline-run CLI. This CLI is for Classic pipelines only. To work with Tekton pipeline runs, see Tekton pipeline runs. To trigger a run and retrieve information about the run, complete the following step:

1. For a specific Classic pipeline, run ibmcloud dev pipeline-run $CLASSIC_PIPELINE_ID --output JSON.

Classic pipeline logs

Pipeline run data is the result of executing, not configuring, pipelines. It is not considered essential to implementing pipeline workloads with different service providers or on-premises software. Therefore, this section is included as a convenience, not as a requisite of data portability.

You can retrieve Classic pipeline logs by using the ibmcloud dev pipeline-log CLI. This CLI is for Classic pipelines only. To work with Tekton pipeline logs, see Tekton pipeline logs. To retrieve logs, run the following command:

1. For a specific Classic pipeline, run ibmcloud dev pipeline-log $CLASSIC_PIPELINE_ID.

GitLab projects

If you want to migrate a Git Repos and Issue Tracking project to another instance of GitLab, use the “Export Project” feature. To export a project archive, complete the following steps:

1. Go to the Git Repos and Issue Tracking home page for the project of interest.
2. Select Settings > General > Advanced > Export Project.
3. The export process runs in the background. After the process completes, a Download Export button appears on the Export Project section of the page. You are also sent an email with a link to download the archive.

For more information about the "Export Project" feature, see Migrate projects and groups by using file exports in the GitLab Docs.

If you want to harvest data from Git Repos and Issue Tracking for use in another system, the "Export Project" feature might not be appropriate. Review the following sections for alternative methods for exporting GitLab data.

GitLab project repositories

You can obtain a copy of a project's file repository, complete with its commit history, by cloning the project repository to a local file system. To clone a Git Repos and Issue Tracking project, see Setting up local clients to work with Git source control.

Current GitLab project repository files

You can obtain an archive that contains the current files in any branch of a project. An archive that you export this way does not include the commit history. To export an archive, complete the following steps:

1. Go to the Git Repos and Issue Tracking home page for the project of interest.
2. Select the branch of the repository that you want to export.
3. Click the Code.
4. Choose an export format, such as zip, tar, tar.gz, or tar.bz2.

For more information, see Download repository source code in the GitLab Docs.

GitLab merge requests

To export the data of a project's merge requests, complete the following steps:

1. From the Git Repos and Issue Tracking home page for the project, select Code > Merge requests.
2. Query for all merge requests of interest.
3. Select Actions > Export as CSV.

For more information, see Export merge requests to CSV in the GitLab Docs.

GitLab issues

To export the data of a project's issues, complete the following steps:

1. From the Git Repos and Issue Tracking home page for the project, select Plan > Issues.
2. Query for all applicable issues.
3. Select Actions > Export as CSV.

For more information, see Export issues to CSV.

GitLab snippets

You can retrieve snippets from a Git Repos and Issue Tracking project. To retrieve snippets, complete the following steps:

1. Use the GitLab GET /snippets/all API to list all snippets to which you have access. This includes personal and project snippets. For more information, see List all snippets in the GitLab API Docs.
2. Use the GitLab GET /snippets/:id/raw API to retrieve the raw content of each snippet of interest. For more information, see Single snippet contents in the GitLab API Docs.

You cannot retrieve private snippets that belong to another user. If you need to obtain private snippets of another user, contact the user and request access to their snippets, or that they export their snippets.

For more information, see Snippets in the GitLab Docs.

GitLab project members

You can obtain a list of member users of a Git Repos and Issue Tracking project. To list member users and their basic metadata, use the following command:

1. Use the GitLab GET /projects/:id/members API to list members of the project.

You can't retrieve detailed information about users other than yourself. If you need to obtain detailed user metadata for members of your project, contact the users on the members list and request that they export their details.

For more information, see List all members of a group or project in the GitLab API Docs.

GitLab Wikis

You can obtain a copy of a project wiki by cloning the wiki repository to a local file system. To clone a Git Repos and Issue Tracking wiki, complete the following steps:

1. From the Git Repos and Issue Tracking home page for the project, select Plan > Wiki.
2. Select Actions > Clone repository.

For more information, see Create or edit wiki pages locally.

DevOps Insights policies and rules

A DevOps Insights policy is defined by the rules within it. These are managed by using the DevOps Insights GUI. To retrieve the details of policy rules, complete the following steps:

1. Select a toolchain from the Overview page.
2. Type "DevOps Insights" into the search field.
3. If there is a DevOps Insights tool integration in the toolchain, select it.
4. Select Policies in the DevOps Insights dashboard.
5. For each policy of interest, select Manage policies > Actions > Edit Rules.
6. For each rule of interest, select Manage rules > Actions > Edit.
7. Copy the data in the resulting dialog to the clipboard, and paste to a plain text file.