Managing personal data for Continuous Delivery

Personal accounts

Typically, each user has their own account that is their personal account. You can easily identify your personal account because it usually contains your name, for example, John Smith's Account.

You have full rights over all objects that are created in your personal account. You can invite other users to join your account, assign them rights over objects that you create, and assign them rights to create objects in your account. Because of these rights, the personal data of other users might be in your account, and your personal data might be in other user's accounts.

If you have permission to create an object in an account, you also have the right to modify and delete it, regardless of which account the object is stored in. When two users collaborate, they often share a personal account.

Corporate accounts

A corporate account is set up by your company. Typically, you are added automatically to the account, rather than being invited. Although corporate accounts provide users with a place to work, communicate, and share resources and charging, this set up is just a convention. A corporate account is really no different than a personal account. Objects that are created in a corporate account are associated with the account and users can be invited to the account.

Teams of people who work for a corporation often collaborate by using a corporate account.

Corporate individual accounts

When you work for a corporation, the work in your account might be legally owned by the corporation. Many users who work for a corporation have a corporate individual account. If you log in to your account by using credentials that contain your corporation's name and also have what appears to be a personal account, the work within your personal account might belong to the corporation.

A corporate individual account is no different from any other account. You can invite users to a corporate individual account and objects that are created in a corporate individual account are owned by the account.

If you work for a corporation that owns your work, a personal account that usually contains your name is considered a corporate individual account.

Personal account

If you own a personal account, you can make changes and delete your data. If you share your account with another user, you own the data, but you might want to contact them about the shared work.

If you can't log in to your IBM Cloud account, contact IBM Support.

Corporate individual account

If you own a corporate individual account, you must coordinate any changes with both your corporation and other members of your team. Delete your personal data regardless of whether it is stored in a corporate account or a corporate individual account. Make sure that you don't delete work that you shared with other users.

Before you start to manage your personal data for the Continuous Delivery components, make sure that you are working in your IBM Cloud account. To view the IBM Cloud account that you are currently working in, on the menu bar, click your profile avatar.

If you can't log in to your IBM Cloud account, contact your corporation, and work with them to delete your personal data.

If you want to delete all of your personal data from Continuous Delivery, the order in which you delete that data is important. First, delete your Git Repos and Issue Tracking data, and then delete your Git Repos and Issue Tracking account. Finally, delete your delivery pipelines, tool integrations, and toolchains.

Personal and shared projects

You can invite other users to collaborate in projects. Git projects that you create inside your account are called personal projects. You can also create Git groups in which projects can be owned by multiple Git owners. You can create new projects for the group or transfer ownership of personal projects to the group. A Git group is often used to represent an IBM Cloud corporate account to indicate ownership of projects by the corporation.

Exporting a Git Repos and Issue Tracking project

Before you delete a Git Repos and Issue Tracking project, you can export the project to archive it.

1. Click the Settings icon in the navigation sidebar.
2. Click General.
3. Click Expand to expand the Export project section.
4. Click Export project.

After the project is archived, you can import it into another GitLab instance.

Deleting your Git Repos and Issue Tracking account

You can delete your Git Repos and Issue Tracking account and most of the things that are owned by that account.

1. On the Git Repos and Issue Tracking User Settings dashboard, on the Account page, in the Delete account section, click Delete account.
2. All Git projects, including repositories and issues are deleted. You are also removed from any Git Repos and Issue Tracking groups that you belong to.

After your account is deleted, some content will remain. This content is assigned to a system-wide Ghost User. For example, comments that you added to an issue remain, but they are attributed to the Ghost User. To delete all of the content that you authored, contact IBM Support

Git Repos and Issue Tracking uses a single sign-on mechanism that automatically creates a corresponding Git account for your IBM Cloud account the first time that you access the tool integration. After you delete your account, do not access Git Repos and Issue Tracking. If you access Git Repos and Issue Tracking again, a new account is automatically created that you must delete.

Modifying a Classic pipeline stage

To modify a pipeline stage:

1. On the Pipeline page, click the Settings icon.

2. Click Configure Stage.

3. On the ENVIRONMENT PROPERTIES tab, edit or delete properties.

4. Modify a job script within the pipeline stage. Select the job and change the values that are part of the Build, Deploy, or Test Configuration.

   

5. Delete a job from the pipeline stage. On the JOBS tab, select the job that you want to delete and click Remove.

Exporting a Classic pipeline stage

To export the definition for an entire pipeline, append /yaml to the pipeline URL:

https://cloud.ibm.com/devops/pipelines/<pipeline id>/yaml?env_id=<region id>

Where <pipeline id> and <region id> are the values that are displayed in the pipeline page URL.

The resulting yaml file includes definitions of all of the pipeline stages.

To export artifacts and logs for a pipeline stage:

1. On the Pipeline page, click View logs and history.
2. Click the build number that you want to export artifacts and logs for.
3. Click DOWNLOAD > Artifacts to export the artifacts for the selected build.
4. Click DOWNLOAD > Logs to export the logs for the selected build.

Deleting a Classic pipeline stage

To delete a pipeline stage:

1. On the Pipeline page, click the Settings icon.
2. Click Delete Stage.

Modifying a Tekton Pipeline

To modify a Tekton Pipeline definition:

1. On the Pipeline Overview page, click Settings, and then click Definitions.
2. Click Add to add a Git repo that was already added to the toolchain.
3. Click the menu to access the options and click Edit or Remove to edit or remove an existing Git repo definition.

To modify the worker to use to run the Tekton Pipeline:

1. On the Pipeline Overview page, click Settings, and then click Worker.
2. Select any worker that was added to the toolchain or the public managed workers.

To modify the environment properties used by the tekton pipeline:

1. On the Pipeline Overview page, click Settings, and then click Environment properties.
2. Edit, add, or remove properties from the page.

For more information about modifying Tekton Pipelines, see Working with Tekton pipelines.

Deleting a Tekton Pipeline

To delete a Tekton Pipeline:

1. From your toolchain's Overview page, on the Delivery pipelines card, go to your Tekton pipeline instance.
2. Click the menu on your Tekton pipeline to access the configuration options and click Delete.

For more information about deleting Tekton pipelines, see the following topics:

• Deleting a Delivery Pipeline with the API
• Deleting a Delivery Pipeline with Terraform

Modifying and deleting tool integrations

When you create a tool integration, you must provide user credentials and other account information that pertains to the integration. If you used your own personal credentials and account information, replace this information with different values, or delete the tool integration.

For more information about modifying tool integrations, see the following documentation:

• Updating a tool integration by using the console
• Updating a tool integration with the API
• Updating a tool integration with Terraform

For more information about deleting tool integrations, see the following documentation:

• Deleting a tool integration by using the console
• Deleting a tool integration with the API
• Deleting a tool integration with Terraform

Deleting toolchains

When you delete a toolchain, the deletion cannot be undone. Deleting a toolchain removes all of its tool integrations, including pipelines, which might delete resources that are managed by those tool integrations.

For more information about deleting toolchains, see the following documentation:

• Deleting a toolchain by using the console
• Deleting a toolchain from the CLI (Beta)
• Deleting a toolchain from the API
• Deleting a toolchain from Terraform

Deleting all toolchains

When you work by using the console, you cannot delete all of the toolchains within a resource group at the same time. You must delete each toolchain, one at a time.

By using the API, CLI, or Terraform, you can more readily delete multiple toolchains. For example, you can write a program or a script that iterates over a set of toolchains and deletes them by repeatedly calling the API or by running the ibmcloud dev toolchain-delete command. If you defined multiple toolchains in Terraform, you can delete the ibm_cd_toolchain resource blocks and run terraform apply, or you can use the terraform destroy command to delete the toolchain resources.

Toolchains are scoped by IBM Cloud region and resource group. Make sure that you target each region and resource group in an account to delete every toolchain that you created in that account.