Create or allocate a project

Allocate tool resources to platform projects for use in DevOps-related functions. Tool resources can be divided into different dimensions, such as project resources and repository resources, existing resources and resources to be created.

Allocation Method

Due to differences in tool types, the allocation of tool resources varies.

Note: “Project” is used differently in different tools. In Harbor, a project contains multiple artifact repositories. Meanwhile in HCS OBS, a project is a bucket or parallel file system that can contain multiple folders.

Create a new project

Add a tool-side project for the integrated tools in the platform. The tools that support this feature include: Zentao, Nexus, JFrog Artifactory.

Cautions

When creating a new project for Nexus, you need to know the following information first.

• The Nexus repository types that can be created are Proxy and Hosted. If you need to create a Group repository, please do it in Nexus. If you want to use the Group repository as a publishing repository for build tasks, make sure that the repository group does not contain Proxy repositories.

  Repository Type	Description
  Proxy	Proxy repository, used to connect to remote repositories and cache files from remote repositories. Can be used as a dependency repository.
  Hosted	Hosted repository, provides functionality similar to a local private repository. Can be used as a dependency repository and publishing repository.

• For raw repositories, in order to avoid Nexus’s overly strict file validation rules causing you to fail to upload files to the repository, the platform has by default turned off the Strict Content Type Validation configuration for newly created raw repositories.

Procedure

1. In the left navigation bar, click DevOps Toolchain > Integrations.

2. Click on your tool card.

3. In the upper right corner of the project list, click Create Project.

4. Fill in the project information.

5. Click New.

What’s next

Allocate the newly created tool-side project to the platform project for use.

Auto-allocation

Specify an automatic allocation strategy. After the project resources are imported to the platform, the resources will be automatically allocated to the platform project for use.

Prerequisite

If the tool is deployed and integrated in the platform, make sure you’ve already add a Secret .

Procedure

1. In the left navigation bar, click DevOps Toolchain > Integrations.

2. Click on your tool card.

3. Click Auto allocation strategy in the upper right corner of the page.

   • Automatic assignment of projects with the same name: A project with the same name as the platform project will be automatically created in the selected tool, and the resources in the tool project will be automatically allocated to the platform project with the same name. If a project with the same name already exists in the selected tool, it will not be created again. There may be a short delay when there are too many projects.

   • Automatic assignment of public projects: The project resources in the selected tool will be allocated as public resources to all projects in the platform.

   The allocation strategies supported by the tools in the platform are as follows:

   Tool Type	Automatic Allocation of Projects with the Same Name	Automatic Allocation of Public Projects
   Docker Registry	x	✓
   Harbor	✓	✓
   HCS OBS	✓	✓
   HCS SWR	x	x
   JFrog Artifactory	x	✓
   Nexus	x	✓
   Jenkins	x	✓
   SonarQube	x	✓
   GitLab	✓	✓
   Bitbucket Data Center	✓	✓
   Bitbucket Cloud	x	✓
   TestLink	✓	✓
   JIRA	x	✓
   Zentao	x	✓

4. Click Allocate.

   Any new platform projects added later will also be automatically allocated to this tool project.

Manually allocation

After allocating resources to the platform for the project, manually allocate the resource to the platform project for use.

Note: For a GitLab shared project , if the account on the integration Secret has read or write permissions to only some of the repositories, you will only be able to view the project on the platform, as you will not have sufficient permissions to allocate it.

Procedure

1. In the left navigation bar, click DevOps Toolchain > Integrations.

2. Click on your tool card.

3. Click > Allocate Platform Project.

4. Select the platform project that you want to use this tool project for.

   Tip: When using the Deploy and Integrate toolchain to Allocate Platform Project, you need to Add secret first.

5. Click Allocate.

Remove allocation

The platform supports removing platform projects from the list of allocated projects for a tool.

Note: For a GitLab shared project , if the account on the integration Secret has read or write permissions to only some of the repositories, you will only be able to view the project on the platform, as you will not have sufficient permissions to remove it’s allocation.

Procedure

1. In the left navigation bar, click DevOps Toolchain > Integrations.

2. Click on your tool card.

3. Click > Remove Platform Project.

4. Select the platform project that you no longer want to use this tool project for.

5. Click on Remove and confirm.

   Note: Platform projects that are allocated to the project dimension as a whole cannot be removed from the repository list. Please remove them under the project list.