This is the multi-page printable view of this section. Click here to print.
Creating a Project
1 - Creating a Project (Helm Chart Deployment)
The user must be enrolled in a project group and tenant to create a project.
For information on how to join a project group and tenant, see Creating a Project Group.
Users can create a project to deploy an application to a specific Kubernetes cluster using App Template, Helm Chart, and Tool Management.
Getting Started with Project Creation
To start creating a project, follow these steps.
- Main page, click the Create Project button. This will take you to the Create Project page.
Entering Basic Information
Enter the project’s basic information. The project name and project ID must be unique and cannot be duplicated.
To enter basic information, follow these steps:
- Project Creation page, select Project Configuration Method item’s App. Template Utilization.
- Select Kubernetes for the Deployment Target item.
- Enter additional content and click the Start button.
Item Description Project Name Enter the project name. Project ID Enter the project ID. Project Configuration Method Select the project configuration method - App. Template Utilization: Select a pre-provided App. template.
- Direct Configuration: Configure directly without an App. template.
Deployment Target Select the deployment target - Kubernetes: Deploy the application to a Kubernetes cluster.
- Kubernetes(ArgoCD): Deploy the application to a Kubernetes cluster using ArgoCD.
- VM(Artifact): Deploy the application to a VM server.
- VM(Docker): Deploy the application to a VM server as a Docker image.
- N/A: Select if the build result is not deployed.
K8S Cluster Select the target cluster to deploy DevOps ConsoleK8S cluster’s cluster, only clusters with user access rights can be selected.
Namespace Select the target namespace to deploy - K8S cluster’s retrieved cluster, only namespaces with user access rights can be selected.
Table. Project Creation Basic Information Input Items
Selecting App Template
Users can select an application template to configure their project.
If you create a project based on an application template with sample source code, you can verify the application to be deployed.
On the other hand, using a template marked as Environment Only configures only the build/deployment environment without sample source code.
If you are using an already configured source code repository to configure your project, select a template marked as Environment Only.
To start choosing an application template, follow these steps:
- Application Template screen, enter the template name to select the desired application template card and click it.
- When the Next button is activated, click the Next button.
| Item | Description |
|---|---|
| Filter | You can easily find application templates through predefined filters. |
| Search | You can easily find application templates through search. |
Setting Code Repository
The user can set up a repository to manage the source code through the code repository setting step.
Creating a New Repository and Using an Existing Repository activation conditions vary depending on the Application Template and Tool.
| Repository Type | App. template with source code + DevOps Console registered tool / DevOps Code | App. template with source code + DevOps Console unregistered tool | App. template without source code (Environment Only) + DevOps Console registered tool / DevOps Code | App. template without source code (Environment Only) + DevOps Console unregistered tool |
|---|---|---|---|---|
| New Repository Creation | ○ | X | ○ | X |
| Existing Repository Use | X | X | ○ | ○ |
To modify or delete saved authentication information, please refer to Managing Authentication Information.
To set up a code repository, follow these steps:
- In the Code Repository section, select the Code Repository type.
- Select Create a New Repository or Use an Existing Repository and enter the information.
- Enter the Authentication Information and click the Connection Test button.
- If the Next button is activated, click the Next button.
| Item | Description |
|---|---|
| Repository Type | Select the code repository to use
|
| New/Existing Usage | Select whether to Create a New Repository or Use an Existing Repository.
|
| Repository Information | Enter repository information
|
| Authentication Information | Enter authentication information
|
| (Unregistered Tool) Repository Information | Enter repository information
|
Setting Code Quality
The user can configure a repository for quality management.
To set up code quality, follow the procedure below.
- Code Quality item, select the Repository Type.
- Enter Basic Information and Authentication Information, then click the Connection Test button.
- When the Next button is activated, click the Next button.
| Item | Description |
|---|---|
| Repository Type | Select the repository to use
|
| New/Existing/Not Used | Select the repository creation method
|
| Base URL | Select the SonarQube URL. |
| Quality Project Name | Enter the name of the SonarQube project. |
| Quality Project Key | Enter the key of the SonarQube project. |
| Authentication Information | Enter authentication information
|
Setting Image Repository
The user can set up the repository to store the built container image through the image repository setting step.
To modify or delete saved authentication information, please refer to Managing Authentication Information.
To set up an image repository, follow these steps:
- Image Repository section, select the Repository Type.
- Select Create New Repository/Use Existing Repository and enter the information.
- Enter the Authentication Information and click the Connection Test button.
- When the Next button is activated, click the Next button.
| Item | Description |
|---|---|
| Repository Type | Select the type of repository to use
|
| Repository Information | Select the repository creation method.
|
| Authentication Information | Enter the authentication information. |
Setting Release Target Environment
The user can deploy through direct configuration using Helm charts.
When selecting Helm release name and Helm chart, the Helm chart installation items and the default Values.yaml items included in the chart are displayed.
Available Helm charts are linked to App templates. You can modify or delete them through Managing Supported Helm Charts.
To set up the deployment target environment, follow these steps:
- Select direct configuration using Helm charts in the deployment target section.
- Enter the Helm release name.
- Click the Search button to select the Helm chart to use.
- Modify the Values.yaml and click the Validation Check button.
- Click the Next button when it is activated.
| Item | Description |
|---|---|
| Deployment Target | Select the deployment target. |
| Helm Release Name | Enter the name of the Helm release to be created.
|
| Helm Chart | Select the Helm chart.
|
| K8S Information | Displays the information of the Kubernetes cluster required for the Value.yaml configuration. |
| Values.yaml | Modify the Values.yaml content.
|
Setting Build Pipeline
Users can configure pipelines for building and deploying applications.
You can check each stage of the pipeline to be configured and change the build job name.
To set up a build pipeline, follow these steps:
- Build Pipeline screen branches according to IDP connection.
- For IDP-connected Jenkins, click the User Check button to verify user registration.
- For non-IDP-connected Jenkins, enter authentication information and click the Connection Test button.
- When the Next button is activated, click the Next button.
Item | Description |
|---|---|
| Build/Deploy Pipeline | Displays build/deploy pipeline information.
|
| Classification | Select development/operation classification.
|
| URL | Select Jenkins to configure the pipeline and enter the job name.
|
| Build Agent | Select the agent to be used for pipeline build.
|
| Build Environment OS | Displays the OS information of the environment where the build agent runs. |
| User Information | IDP-connected Jenkins
|
| Environment Variable Setting | Set environment variables to be registered in the Jenkins pipeline. |
| Image Tag Pattern | Select the method for assigning tags to container images. |
| Deploy Strategy | Select the deployment method for container images. |
| Deployment Result Recipient | Select the user to receive the result after the build pipeline is completed. |
Setting User Definition
Users can specify and modify the path of the Dockerfile file to be used for building.
Additionally, you can check and modify the final script generated based on the information set up in Configuring the Build Pipeline.
To configure Dockerfile and pipeline scripts, follow these steps:
- Customize settings page, enter information, and click the Connection Test button.
- When the Next button is activated, click the Next button.
| Item | Description |
|---|---|
| Dockerfile Settings | Choose whether to Create a new Dockerfile or Use an existing Dockerfile.
|
| Dockerfile Path | Specify the path of the Dockerfile file in the source code. |
| Branch Name | The branch name is automatically registered when setting up Configuring the Code Repository. |
| Dockerfile | Check and modify the contents of the Dockerfile. |
| Pipeline Script | Check and modify the pipeline script. |
Completing Project Creation
The user can finally check the project and tool information to be created and start creating the project.
To complete the project creation, follow the procedure below.
- Summary Information screen, check the information and click the Complete button.
- The Project Creation popup window opens and the project creation proceeds.
- After the project creation is complete, click the Confirm button to move to the Project page.
2 - Creating a Project (Workload Deployment)
For information on how to join a project group and tenant, see Creating a Project Group.
Users can create a project that deploys to a specific Kubernetes cluster using App Templates, Tool Management, and Workloads.
Starting Project Creation
To start creating a project, follow these steps:
- Main page, click the Create Project button. This will take you to the Create Project page.
Entering Basic Information
Enter the project’s basic information. The project name and project ID must be unique and cannot be duplicated.
To enter basic information, follow these steps:
- Project Creation page, select Project Configuration Method item’s App. Template Utilization.
- Select Kubernetes for the Deployment Target item.
- Enter additional content and click the Start button.
Item Description Project Name Enter the project name. Project ID Enter the project ID. Project Configuration Method Select the project configuration method - App. Template Utilization: Select a pre-provided App. template.
- Direct Configuration: Configure directly without an App. template.
Deployment Target Select the deployment target - Kubernetes: Deploy the application to a Kubernetes cluster.
- Kubernetes(ArgoCD): Deploy the application to a Kubernetes cluster using ArgoCD.
- VM(Artifact): Deploy the application to a VM server.
- VM(Docker): Deploy the application to a VM server as a Docker image.
- N/A: Select if the build result is not deployed.
K8S Cluster Select the target cluster to deploy DevOps ConsoleK8S cluster’s cluster, only clusters with user access rights can be selected.
Namespace Select the target namespace to deploy - K8S cluster’s retrieved cluster, only namespaces with user access rights can be selected.
Table. Project Creation Basic Information Input Items
Selecting an Application Template
Users can select an application template to configure their project.
If you create a project based on an application template with sample source code, you can verify the application to be deployed.
On the other hand, using a template marked as Environment Only configures only the build/deployment environment without sample source code.
If you are using an already configured source code repository to configure your project, select a template marked as Environment Only.
To start choosing an application template, follow these steps:
- Application Template screen, enter the template name to select the desired application template card and click it.
- When the Next button is activated, click the Next button.
| Item | Description |
|---|---|
| Filter | You can easily find application templates through predefined filters. |
| Search | You can easily find application templates through search. |
Setting Up a Code Repository
The user can set up a repository to manage the source code through the code repository setting step.
Creating a New Repository and Using an Existing Repository activation conditions vary depending on the Application Template and Tool.
| Repository Type | App. template with source code + DevOps Console registered tool / DevOps Code | App. template with source code + DevOps Console unregistered tool | App. template without source code (Environment Only) + DevOps Console registered tool / DevOps Code | App. template without source code (Environment Only) + DevOps Console unregistered tool |
|---|---|---|---|---|
| New Repository Creation | ○ | X | ○ | X |
| Existing Repository Use | X | X | ○ | ○ |
To modify or delete saved authentication information, please refer to Managing Authentication Information.
To set up a code repository, follow these steps:
- In the Code Repository section, select the Code Repository type.
- Select Create a New Repository or Use an Existing Repository and enter the information.
- Enter the Authentication Information and click the Connection Test button.
- If the Next button is activated, click the Next button.
| Item | Description |
|---|---|
| Repository Type | Select the code repository to use
|
| New/Existing Usage | Select whether to Create a New Repository or Use an Existing Repository.
|
| Repository Information | Enter repository information
|
| Authentication Information | Enter authentication information
|
| (Unregistered Tool) Repository Information | Enter repository information
|
Setting Up Code Quality
The user can configure a repository for quality management.
To set up code quality, follow the procedure below.
- Code Quality item, select the Repository Type.
- Enter Basic Information and Authentication Information, then click the Connection Test button.
- When the Next button is activated, click the Next button.
| Item | Description |
|---|---|
| Repository Type | Select the repository to use
|
| New/Existing/Not Used | Select the repository creation method
|
| Base URL | Select the SonarQube URL. |
| Quality Project Name | Enter the name of the SonarQube project. |
| Quality Project Key | Enter the key of the SonarQube project. |
| Authentication Information | Enter authentication information
|
Setting Up an Image Repository
The user can set up the repository to store the built container image through the image repository setting step.
To modify or delete saved authentication information, please refer to Managing Authentication Information.
To set up an image repository, follow these steps:
- Image Repository section, select the Repository Type.
- Select Create New Repository/Use Existing Repository and enter the information.
- Enter the Authentication Information and click the Connection Test button.
- When the Next button is activated, click the Next button.
| Item | Description |
|---|---|
| Repository Type | Select the type of repository to use
|
| Repository Information | Select the repository creation method.
|
| Authentication Information | Enter the authentication information. |
Setting Up the Deployment Environment
Users can deploy by selecting the Deployment Target Workload.
To set up the deployment environment, follow these steps:
- In the Deployment Target section, select Select Deployment Target Workload. The Deployment Target Workload area will appear.
- In the Deployment Target Workload area, select the target workload and target container to deploy.
- When the Next button is activated, click the Next button.
| Item | Description |
|---|---|
| Deployment Target | Select the deployment target
|
| Inquiry Target | Select the inquiry target. |
| Workload | Select the workload
|
| Target Container | Select the target container to use from the selected workload. |
Setting Up the Build Pipeline
Users can configure pipelines for building and deploying applications.
You can check each stage of the pipeline to be configured and change the build job name.
To set up a build pipeline, follow these steps:
- Build Pipeline screen branches according to IDP connection.
- For IDP-connected Jenkins, click the User Check button to verify user registration.
- For non-IDP-connected Jenkins, enter authentication information and click the Connection Test button.
- When the Next button is activated, click the Next button.
Item | Description |
|---|---|
| Build/Deploy Pipeline | Displays build/deploy pipeline information.
|
| Classification | Select development/operation classification.
|
| URL | Select Jenkins to configure the pipeline and enter the job name.
|
| Build Agent | Select the agent to be used for pipeline build.
|
| Build Environment OS | Displays the OS information of the environment where the build agent runs. |
| User Information | IDP-connected Jenkins
|
| Environment Variable Setting | Set environment variables to be registered in the Jenkins pipeline. |
| Image Tag Pattern | Select the method for assigning tags to container images. |
| Deploy Strategy | Select the deployment method for container images. |
| Deployment Result Recipient | Select the user to receive the result after the build pipeline is completed. |
Setting Up Custom Settings
Users can specify and modify the path of the Dockerfile file to be used for building.
Additionally, you can check and modify the final script generated based on the information set up in Configuring the Build Pipeline.
To configure Dockerfile and pipeline scripts, follow these steps:
- Customize settings page, enter information, and click the Connection Test button.
- When the Next button is activated, click the Next button.
| Item | Description |
|---|---|
| Dockerfile Settings | Choose whether to Create a new Dockerfile or Use an existing Dockerfile.
|
| Dockerfile Path | Specify the path of the Dockerfile file in the source code. |
| Branch Name | The branch name is automatically registered when setting up Configuring the Code Repository. |
| Dockerfile | Check and modify the contents of the Dockerfile. |
| Pipeline Script | Check and modify the pipeline script. |
Completing Project Creation
The user can finally check the project and tool information to be created and start creating the project.
To complete the project creation, follow the procedure below.
- Summary Information screen, check the information and click the Complete button.
- The Project Creation popup window opens and the project creation proceeds.
- After the project creation is complete, click the Confirm button to move to the Project page.
3 - Creating an ArgoCD Deployment Project
- The user must be a member of a project group and tenant to create a project.
- For information on how to join a project group and tenant, see Creating a Project Group.
- ArgoCD deployment requires ArgoCD and a Git repository for GitOps deployment to be set up in advance.
- In the DevOps Console, the existing ArgoCD and its associated Git information are used for deployment.
Users can create a project using App Template, Tool Management, and ArgoCD.
Starting Project Creation
To start creating a project, follow these steps.
- Click the Create Project button on the Main page. This will take you to the Create Project page.
Entering Basic Information
Enter the project’s basic information. The project name and project ID must be unique and cannot be duplicated.
To enter the basic information, follow these steps.
- Enter the project name and project ID.
- Select App Template as the Project Configuration Method.
- Select Kubernetes (ArgoCD) as the Deployment Target.
- Choose the ArgoCD App Creation Method.
- Create a new App: Create a new ArgoCD application while creating the project.
- Use an existing App: Use an existing ArgoCD application to create the project.
- Click the Start button after completing each input.
Selecting an App Template
Users can select an application template to configure their project.
If you create a project based on an application template with sample source code, you can verify the application to be deployed.
On the other hand, using a template marked as Environment Only configures only the build/deployment environment without sample source code.
If you are using an already configured source code repository to configure your project, select a template marked as Environment Only.
To start choosing an application template, follow these steps:
- Application Template screen, enter the template name to select the desired application template card and click it.
- When the Next button is activated, click the Next button.
| Item | Description |
|---|---|
| Filter | You can easily find application templates through predefined filters. |
| Search | You can easily find application templates through search. |
Setting up a Code Repository
The user can set up a repository to manage the source code through the code repository setting step.
Creating a New Repository and Using an Existing Repository activation conditions vary depending on the Application Template and Tool.
| Repository Type | App. template with source code + DevOps Console registered tool / DevOps Code | App. template with source code + DevOps Console unregistered tool | App. template without source code (Environment Only) + DevOps Console registered tool / DevOps Code | App. template without source code (Environment Only) + DevOps Console unregistered tool |
|---|---|---|---|---|
| New Repository Creation | ○ | X | ○ | X |
| Existing Repository Use | X | X | ○ | ○ |
To modify or delete saved authentication information, please refer to Managing Authentication Information.
To set up a code repository, follow these steps:
- In the Code Repository section, select the Code Repository type.
- Select Create a New Repository or Use an Existing Repository and enter the information.
- Enter the Authentication Information and click the Connection Test button.
- If the Next button is activated, click the Next button.
| Item | Description |
|---|---|
| Repository Type | Select the code repository to use
|
| New/Existing Usage | Select whether to Create a New Repository or Use an Existing Repository.
|
| Repository Information | Enter repository information
|
| Authentication Information | Enter authentication information
|
| (Unregistered Tool) Repository Information | Enter repository information
|
Setting up Code Quality
The user can configure a repository for quality management.
To set up code quality, follow the procedure below.
- Code Quality item, select the Repository Type.
- Enter Basic Information and Authentication Information, then click the Connection Test button.
- When the Next button is activated, click the Next button.
| Item | Description |
|---|---|
| Repository Type | Select the repository to use
|
| New/Existing/Not Used | Select the repository creation method
|
| Base URL | Select the SonarQube URL. |
| Quality Project Name | Enter the name of the SonarQube project. |
| Quality Project Key | Enter the key of the SonarQube project. |
| Authentication Information | Enter authentication information
|
Setting up an Image Repository
The user can set up the repository to store the built container image through the image repository setting step.
To modify or delete saved authentication information, please refer to Managing Authentication Information.
To set up an image repository, follow these steps:
- Image Repository section, select the Repository Type.
- Select Create New Repository/Use Existing Repository and enter the information.
- Enter the Authentication Information and click the Connection Test button.
- When the Next button is activated, click the Next button.
| Item | Description |
|---|---|
| Repository Type | Select the type of repository to use
|
| Repository Information | Select the repository creation method.
|
| Authentication Information | Enter the authentication information. |
Setting up the Deployment Environment
To set up the deployment environment, you need to have ArgoCD and a Git repository for GitOps deployment ready.
The input values differ depending on the ArgoCD App Creation Method chosen.
- Create a new App
- Use an existing App
Creating a New App
To set up the deployment environment by creating a new ArgoCD application, follow these steps.
- On the Deployment Environment screen, enter the ArgoCD URL and click the Confirm button.
- The authentication information input screen appears.
- Enter the authentication information and click the Connection Test button.
- The input screen for the new ArgoCD application appears.
- Enter the ArgoCD application name and ArgoCD project name.
- Select the repository type.
- Select the Helm chart.
- The Helm chart and Helm chart Git repository information are displayed.
- Modify the Values.yaml and click the Validation Check button.
- Enter the Git repository information and authentication information, then click the Connection Test button.
- Click the Next button when it becomes active.
| Item | Description |
|---|---|
| URL input method | Select the URL input method.
|
| ArgoCD URL | Enter the ArgoCD URL and click the Confirm button. The authentication information section appears. |
| Authentication information | Enter the authentication information and click the Connection Test button. The application basic information section opens. |
| Application name | Enter the name of the ArgoCD application to be created. |
| Project name | Enter the name of the ArgoCD project. |
| Repository type | Select the repository type.
|
| Helm chart | Select the Helm chart. |
| Helm chart Git repository | Enter the information of the Git repository to be used for GitOps. |
Using an Existing App
To set up the deployment environment using an existing ArgoCD application, follow these steps.
- On the Deployment Environment screen, enter the ArgoCD URL and click the Confirm button.
- The input screen for the existing ArgoCD application name and authentication information appears.
- Enter the existing application name and authentication information, then click the Connection Test button.
- A pop-up window for URL Check opens to distinguish the Git repository linked to the ArgoCD application.
- Modify the Base URL in the URL Check pop-up window and click the Confirm button.
- The information of the Git repository linked to the ArgoCD application is displayed.
- Enter the authentication information of the Git repository and click the Connection Test button.
- In the Manifest Root path section, enter the yaml file name and key value to be modified.
- Click the Next button when it becomes active.
| Item | Description |
|---|---|
| URL input method | Select the URL input method
|
| ArgoCD URL | Enter the ArgoCD URL and click the Confirm button. The existing application name and authentication information section appears. |
| Application name / Authentication information | Enter the existing application name and authentication information, then click the Connection Test button. The Git repository and ArgoCD information section appears. |
| URL Check | Distinguish the Base URL and Path from the entire URL. |
| Git repository authentication information | Enter the authentication information of the Git repository used by the selected existing application. |
| Image Repo Key | Enter the path and key value of the yaml file where the image repository information is recorded. If the key values for the repository and tag are the same, enter the same value. |
| Image Tag Key | Enter the path and key value of the yaml file where the image tag information is recorded. If the key values for the repository and tag are the same, enter the same value. |
| Image Secret Key | Enter the path and key value of the yaml file where the image secret information is recorded. |
| Deploy Strategy Key | Enter the path and key value of the yaml file where the deployment strategy information is recorded (optional). |
Setting up a Build Pipeline
Users can configure pipelines for building and deploying applications.
You can check each stage of the pipeline to be configured and change the build job name.
To set up a build pipeline, follow these steps:
- Build Pipeline screen branches according to IDP connection.
- For IDP-connected Jenkins, click the User Check button to verify user registration.
- For non-IDP-connected Jenkins, enter authentication information and click the Connection Test button.
- When the Next button is activated, click the Next button.
Item | Description |
|---|---|
| Build/Deploy Pipeline | Displays build/deploy pipeline information.
|
| Classification | Select development/operation classification.
|
| URL | Select Jenkins to configure the pipeline and enter the job name.
|
| Build Agent | Select the agent to be used for pipeline build.
|
| Build Environment OS | Displays the OS information of the environment where the build agent runs. |
| User Information | IDP-connected Jenkins
|
| Environment Variable Setting | Set environment variables to be registered in the Jenkins pipeline. |
| Image Tag Pattern | Select the method for assigning tags to container images. |
| Deploy Strategy | Select the deployment method for container images. |
| Deployment Result Recipient | Select the user to receive the result after the build pipeline is completed. |
Setting up User Definitions
Users can specify and modify the path of the Dockerfile file to be used for building.
Additionally, you can check and modify the final script generated based on the information set up in Configuring the Build Pipeline.
To configure Dockerfile and pipeline scripts, follow these steps:
- Customize settings page, enter information, and click the Connection Test button.
- When the Next button is activated, click the Next button.
| Item | Description |
|---|---|
| Dockerfile Settings | Choose whether to Create a new Dockerfile or Use an existing Dockerfile.
|
| Dockerfile Path | Specify the path of the Dockerfile file in the source code. |
| Branch Name | The branch name is automatically registered when setting up Configuring the Code Repository. |
| Dockerfile | Check and modify the contents of the Dockerfile. |
| Pipeline Script | Check and modify the pipeline script. |
Completing Project Creation
The user can finally check the project and tool information to be created and start creating the project.
To complete the project creation, follow the procedure below.
- Summary Information screen, check the information and click the Complete button.
- The Project Creation popup window opens and the project creation proceeds.
- After the project creation is complete, click the Confirm button to move to the Project page.
4 - Creating a Project (VM Deployment)
The user must be a member of a project group and tenant to create a project.
For more information on joining a project group and tenant, see Creating a Project Group.
Users can create a project that deploys to a specific VM server using App Template and Tool Management.
Before creating a project for VM deployment, register the VM server information. For more information on registering a VM server, see Getting Started with VM Server Group.
Starting Project Creation
To start creating a project, follow these steps:
- Main page, click the Create Project button. This will take you to the Create Project page.
Entering Basic Information
- On the Create Project page, enter the project name and project ID.
- For the Project Configuration Method, select App Template.
- For the Deployment Target, select VM (Artifact) or VM (Docker).
- VM (Artifact) creates a
war/jarfile and deploys it to the target server. - VM (Docker) builds and deploys a Docker image using the
dockercommand.
- VM (Artifact) creates a
- Select the Deployment Method.
- For differences in deployment methods, see Table. SSH Method vs Agent Method
- After completing each input, click the Start button.
Selecting App Template
Users can select an application template to configure their project.
If you create a project based on an application template with sample source code, you can verify the application to be deployed.
On the other hand, using a template marked as Environment Only configures only the build/deployment environment without sample source code.
If you are using an already configured source code repository to configure your project, select a template marked as Environment Only.
To start choosing an application template, follow these steps:
- Application Template screen, enter the template name to select the desired application template card and click it.
- When the Next button is activated, click the Next button.
| Item | Description |
|---|---|
| Filter | You can easily find application templates through predefined filters. |
| Search | You can easily find application templates through search. |
Setting Up Code Repository
The user can set up a repository to manage the source code through the code repository setting step.
Creating a New Repository and Using an Existing Repository activation conditions vary depending on the Application Template and Tool.
| Repository Type | App. template with source code + DevOps Console registered tool / DevOps Code | App. template with source code + DevOps Console unregistered tool | App. template without source code (Environment Only) + DevOps Console registered tool / DevOps Code | App. template without source code (Environment Only) + DevOps Console unregistered tool |
|---|---|---|---|---|
| New Repository Creation | ○ | X | ○ | X |
| Existing Repository Use | X | X | ○ | ○ |
To modify or delete saved authentication information, please refer to Managing Authentication Information.
To set up a code repository, follow these steps:
- In the Code Repository section, select the Code Repository type.
- Select Create a New Repository or Use an Existing Repository and enter the information.
- Enter the Authentication Information and click the Connection Test button.
- If the Next button is activated, click the Next button.
| Item | Description |
|---|---|
| Repository Type | Select the code repository to use
|
| New/Existing Usage | Select whether to Create a New Repository or Use an Existing Repository.
|
| Repository Information | Enter repository information
|
| Authentication Information | Enter authentication information
|
| (Unregistered Tool) Repository Information | Enter repository information
|
Setting Up Code Quality
The user can configure a repository for quality management.
To set up code quality, follow the procedure below.
- Code Quality item, select the Repository Type.
- Enter Basic Information and Authentication Information, then click the Connection Test button.
- When the Next button is activated, click the Next button.
| Item | Description |
|---|---|
| Repository Type | Select the repository to use
|
| New/Existing/Not Used | Select the repository creation method
|
| Base URL | Select the SonarQube URL. |
| Quality Project Name | Enter the name of the SonarQube project. |
| Quality Project Key | Enter the key of the SonarQube project. |
| Authentication Information | Enter authentication information
|
Setting Up Artifact Repository
Users can configure a repository for artifacts.
If you select Not Created, you can proceed to the next step.
To set up an artifact repository, follow these steps:
- On the Artifact Repository screen, select the repository type.
- Enter the basic information and authentication information, then click the Connection Test button.
- If the Next button is activated, click it.
| Item | Description |
|---|---|
| Repository Type | Select the type of repository to use
|
| New/Existing/Not Used | Select the method of creating a repository
|
| Base URL / Endpoint URL | Select the Nexus URL or Object Storage URL. |
| Repository Type / Bucket Name |
|
| Repository Name / Folder Name |
|
| Authentication Information | Enter the authentication information
|
Setting Up Deployment Target Environment
Deployment Target Setting requires a registered VM Server Group/VM Server.
For registration methods and more information, see VM Server Group.
To set up the deployment target environment, follow these steps:
- On the Deployment Target Environment screen, enter the required information and click the Next button.
| Item | Description |
|---|---|
| Deployment Configuration | Choose whether to write a deployment script directly
|
| Deployment Method | The selected deployment method is displayed.
|
| Artifact Repository | The address of the repository to use for the agent method is displayed.
|
| Manual Deployment | Select the default value for manual deployment
|
| Deployment Order | Choose whether to deploy to multiple target servers in parallel or sequentially. |
| Deployment Target Setting | Set up the deployment target server.
|
| Auto-Restore Setting | Choose whether to set up automatic restoration.
|
| Command Before File Deployment | Enter the command to be executed before file deployment. |
| Files to be Deployed |
|
| Command After File Deployment | Enter the command to be executed after file deployment. |
Setting Up Build Pipeline
Users can configure a pipeline to build and deploy an application.
You can check each stage of the pipeline to be configured and change the build job name.
To set up a build pipeline, follow these steps:
- On the build pipeline setup stage, enter the Authentication Information and click the Connection Test button.
- If the Next button is activated, click it.
| Item | Description |
|---|---|
| Build/Deployment Pipeline | Displays build/deployment pipeline information.
|
| Classification | Select the development/operation classification.
|
| URL | Select the Jenkins to configure the pipeline and enter the job name.
|
| Build Agent | Select the agent to use for pipeline build.
|
| Build Environment OS | Displays the OS information of the environment where the build agent is executed. |
| Authentication Information | Enter the authentication information for Jenkins. |
| Environment Variable Setting | Set the environment variables to be registered in the Jenkins pipeline. |
| Deployment Result Recipient | Select the user to receive the result of the build pipeline completion. |
Setting Up User-Defined Configuration
If you selected Direct Deployment Script Writing in the deployment target and deployment setting stage, modify the pipeline content in this stage to complete the deployment setting.
To set up a user-defined configuration, follow these steps:
- On the User-Defined stage, review and modify the content, then click the Next button.
Completing Project Creation
The user can finally check the project and tool information to be created and start creating the project.
To complete the project creation, follow the procedure below.
- Summary Information screen, check the information and click the Complete button.
- The Project Creation popup window opens and the project creation proceeds.
- After the project creation is complete, click the Confirm button to move to the Project page.
5 - Creating an Empty Project
- The user must be a member of a project group and tenant to create a project.
- For information on how to join a project group and tenant, see Creating a Project Group.
Users can create an empty (empty) project with no settings.
After creating an empty project, to configure the build/deployment, users must manually perform tasks such as Adding a Code Repository, Adding an Image Repository, Installing Helm, Adding a Build Pipeline.
Starting Project Creation
To start creating an empty project, follow these steps.
- Click the Create Project button on the Main page. This will take you to the Create Project page.
Entering Basic Information
Enter the project’s basic information. The project name and project ID must be unique and cannot be duplicated.
To enter basic information, follow these steps.
- On the Create Project page, select Direct Configuration from the Project Configuration Method.
- Enter the Project Name and Project ID, then click the Start button. The Summary Information screen will appear.
Completing Project Creation
The user can finally check the project and tool information to be created and start creating the project.
To complete the project creation, follow the procedure below.
- Summary Information screen, check the information and click the Complete button.
- The Project Creation popup window opens and the project creation proceeds.
- After the project creation is complete, click the Confirm button to move to the Project page.