DevOps Tools

• 1: DevOps Service
• 1.1: Overview
• 1.2: How-to guides
• 1.3: API Reference
• 1.4: CLI Reference
• 1.5: Release Note
• 2: DevOps Console
• 2.1: Overview
• 2.1.1: DevOps Console Introduction
• 2.1.2: Roles
• 2.1.3: Screen Configuration
• 2.2: Getting Started
• 2.2.1: Getting Started with DevOps Console
• 2.2.1.1: Registration Information
• 2.2.2: Tutorial (From Project Creation to Build/Deploy)
• 2.2.2.1: Add Build/Deploy (Helm Chart Deployment)
• 2.2.2.2: Add Build/Deploy (Workload Deployment)
• 2.2.2.3: Add Build/Deploy (VM Deployment)
• 2.2.2.4: Check Deployment Target Namespace Permissions (Before Project Creation)
• 2.3: Project
• 2.3.1: Project Overview
• 2.3.2: Create Project
• 2.3.2.1: Create Project (Helm Chart Deployment)
• 2.3.2.2: Create Project (Workload Deployment)
• 2.3.2.3: Create Project (ArgoCD Deployment)
• 2.3.2.4: Create Project (VM Deployment)
• 2.3.2.5: Create Project (Empty)
• 2.3.3: Start Project
• 2.3.4: Project Dashboard
• 2.3.5: Project Members
• 2.4: Build/Deploy
• 2.4.1: Build Pipeline
• 2.4.1.1: Stage
• 2.4.1.2: Multibranch Pipeline
• 2.4.2: Kubernetes Deployment
• 2.4.2.1: Helm Release
• 2.4.2.2: Workload
• 2.4.2.3: Blue/Green Deployment
• 2.4.2.4: Canary Deployment
• 2.4.2.5: Istio
• 2.4.2.6: ArgoCD
• 2.4.3: VM Deployment
• 2.4.4: Helm Install
• 2.4.5: Ingress/Service Management
• 2.4.6: Kubernetes Secret Management
• 2.4.7: Environment Variable Management
• 2.5: Project Group
• 2.5.1: Project Group Overview
• 2.5.2: Create Project Group
• 2.5.3: Project Group Dashboard
• 2.6: Tenant
• 2.6.1: Tenant Management
• 2.6.2: Tenant Dashboard
• 2.6.3: Tenant Notice
• 2.7: Repository
• 2.7.1: Code Repository
• 2.7.2: Artifact Repository
• 2.7.3: Image Repository
• 2.7.4: Chart Repository
• 2.7.5: Helm Chart
• 2.7.5.1: Creating Helm Charts with Form Input Support
• 2.8: Quality
• 2.8.1: Code Quality
• 2.9: Tools & Templates
• 2.9.1: Tool Management
• 2.9.2: App Template
• 2.9.3: Register User-installed Jenkins Tool
• 2.10: Deployment Target
• 2.10.1: K8S Cluster
• 2.10.1.1: Verify Cluster Admin Token
• 2.10.2: VM Server Group
• 2.10.3: Request Permission
• 2.11: Release Management
• 2.11.1: Release Management
• 2.11.2: Workflow Management
• 2.11.3: Approval Template Settings
• 2.11.4: Task
• 2.11.5: JIRA Project
• 2.12: Release Note

1 - DevOps Service

1.1 - Overview

Service Overview

DevOps Service is a service that provides standardized development tools, code‑framework‑based development templates, and integrated management functions for application and system development, deployment, and operation through the DevOps Console. This enables fast and reliable software development, deployment, and operation, and allows convenient integrated management of Samsung Cloud Platform resources and CI/CD tools within the DevOps Workflow.

Features

• Convenient Code Management and Deployment: Users can conveniently manage everything from source code management to build and deployment via a web-based console. It also supports integration with various tools to analyze source code and improve quality.
• Flexible Deployment Options: Minimize user service downtime and provide deployment environment configurations for k8s clusters or Virtual Machines, allowing users to configure deployments that fit their services and offering flexible deployment methods.
• Repository for Deployment Management: Provides a repository that can manage source code, libraries, application artifacts, container images, and other assets for the deployment management of user services.

Service Architecture Diagram

Provided features

DevOps Service integrates standard development tools to easily set up the development environment and provides convenience for build/deployment, offering the following features.

• Continuous Integration and Deployment (CI/CD Continuous Integration/Continuous Deployment): Users can access tools responsible for source code repositories, artifact repositories, code analysis, image registries, and build/deployment with a single login.
• Application template-based project configuration: Users can easily set up a project using a wizard approach with a template that reflects development standards.
• Major Development Languages and Frameworks Provided: Users can select the development languages (Java, C#, Python, Ruby, etc.) and frameworks (SpringBoot, Vue.js, .Net, etc.) required for application development to configure a project for building/deployment.
• Automated Build/Deployment Pipeline Configuration: Users can automatically generate pipeline scripts using the build/deployment pipeline template included in the application template, or configure each stage of the pipeline through a GUI-based interface.
• Support for Various Deployment Strategies and Rollback: Users can use deployment strategies (RollingUpdate, Blue-Green) to minimize downtime of running applications, and can roll back to the desired version with a single click. If a user wants to use a Virtual Server as the deployment environment, they can deploy to the Virtual Server as a packaged file or a Docker image.
• Custom Release Process Support: Users can define and repeatedly execute various release processes, taking into account the type of application changes.

Components

Users can easily use the DevOps Service through the Samsung Cloud Platform DevOps Console.

DevOps Console

DevOps Console provides integrated support for the tools required for application development and build/deployment, allowing easy management of project configuration and build/deployment.

• Dev.Starter: An application template that provides integrated templates required for build and deployment, as well as sample code reflecting development standards.
• Source Code Repository (Source Code Repository): Supports integration with source code configuration management tools. Can be linked with Git Repository.
• Artifact Repository (Artifact Repository): Supports integration with an artifact repository for storing libraries needed for application builds and application artifacts.
• Code Quality (Code Review): Supports integration with code quality tools that can measure and manage source code quality through static code analysis.
• Helm Chart Repository (Helm Chart Repository): In Kubernetes, Helm charts are used to install and upgrade software easily. To install software, users must create Helm charts themselves. ChartMuseum is provided as the default repository for managing Helm charts. Integration with other chart repository tools is also supported.
• Image Registry: Supports integration with an image registry for storing container images.
• VM server group: a collection of Virtual Servers that serve as the deployment target for an application. Users can register Virtual Servers in the DevOps Console and designate them as deployment targets.
• Kubernetes Cluster: The cluster that serves as the deployment target for applications. Users can register a Kubernetes Cluster in the DevOps Console and designate it as a deployment target.

Provision status by region

The DevOps Service is available in the environments below.

Preliminary Service

The DevOps Service has no prerequisite services.

1.2 - How-to guides

The user can create the service by entering the required information for the DevOps Service and selecting detailed options through the Samsung Cloud Platform Console. Additionally, by using the DevOps Service’s standardized development tools, code, framework-based development templates, and integrated management features, the user can efficiently carry out development projects.

Create DevOps Service

You can create and use a DevOps Service in the Samsung Cloud Platform Console.

To create a DevOps Service, follow these steps.

1. From the All Services > DevOps Tools > DevOps Service menu, click the Create Service button. You will be taken to the Service Home page of the DevOps Service.
2. On the Service Home page, click the DevOps Service Create button. You will be taken to the DevOps Service Create page.
3. On the DevOps Service Creation page, enter the information required to create the service.
   • Enter the required information in the Service Information Input area.

     Category	Required status	Detailed description
     Tenant name	Required	Tenant name of the DevOps Service created by the user Name displayed logically when accessing the DevOps Console Start with a lowercase English letter and use lowercase English letters, numbers, and special characters (-) to enter 3 to 30 characters
     Tenant code	Required	ID used internally by the system It is an ID value used internally, similar to a project ID, generated from the value entered by the user It must start with a lowercase English letter and be entered using lowercase English letters, numbers, and special characters (-) with a length of 3 to 30 characters

     Table. DevOps Service required information input items
   • In the Add Tenant Member area, select the tenant user who will use the service.

     Category	Required status	Detailed description
     user	Required	Select members from the user list Service applicants are included as default members of the Tenant You must select at least one user to create the service

     Table. DevOps Service Tenant member addition items
   • Enter or select the required information in the Additional Information Input area.

     Category	Required	Detailed description
     tag	Selection	Add Tag Up to 50 can be added per resource After clicking the Add Tag button, enter or select Key, Value values

     Table. DevOps Service Additional Information Input Fields
4. Verify the detailed information and estimated charges generated in the summary panel, and click the Create button.
   • Once creation is complete, check the created resource on the Resource List page.

Using DevOps Service

The DevOps Service can configure an actual DevOps environment in a separate console called DevOps Console.

To use the DevOps Service, follow these steps.

1. Click the All Services > DevOps Tools > DevOps Service menu. Go to the Service Honme page of DevOps Service.
2. From the Service Home page, click the DevOps Service menu. You will be taken to the DevOps Service list page.
3. DevOps Service List page, click the resource you want to view detailed information for. You will be taken to the DevOps Service Details page.
4. On the DevOps Service Details page, click the DevOps Console button. You will be taken to the Samsung Cloud Platform DevOps Console page.

Check DevOps Service details

DevOps Service service allows you to view and edit the full list of resources and detailed information. The DevOps Service Details page consists of Details, Tags, Activity Log tabs.

To view the detailed information of the DevOps Service, follow the steps below.

1. Click the All Services > DevOps Tools > DevOps Service menu. Navigate to the Service Honme page of DevOps Service.
2. On the Service Home page, click the DevOps Service menu. You will be taken to the DevOps Service list page.
3. On the DevOps Service List page, click the resource you want to view detailed information for. You will be taken to the DevOps Service Details page.
   • DevOps Service Details page displays status information and consists of Details, Tags, Activity History tabs.

     Category	Detailed description
     Status indicator	Display the status of the DevOps Service Active: Available state Creating: Creating state Error: Operational error state
     DevOps Console	Navigate to the DevOps Console to control the service.
     Service termination	Service cancellation button

     Table. DevOps Service status information and additional features

Detailed information

You can view detailed information of the selected resource on the DevOps Service List page.

tag

DevOps Service List page lets you view the tag information of the selected resource, and you can add, modify, or delete it.

Work History

On the DevOps Service List page, you can view the operation history of the selected resource.

Cancel DevOps Service

To cancel the DevOps Service, follow the steps below.

1. Click the All Services > DevOps Tools > DevOps Service menu. You will be taken to the Service Home page of the DevOps service.
2. On the Service Home page, click the DevOps Service menu. You will be taken to the DevOps List page.
3. On the DevOps Service List page, click the resource to cancel. You will be taken to the DevOps Service Detail page.
4. On the DevOps Service Details page, click the Cancel Service button.
5. When termination is complete, verify on the DevOps Service List page whether the resource has been terminated.

1.3 - API Reference

1.4 - CLI Reference

1.5 - Release Note

2 - DevOps Console

2.1 - Overview

2.1.1 - DevOps Console Introduction

Service Overview

DevOps Console integrates standard development tools, making it easy to configure development environments and providing convenience for building and deploying, with the following features.

Key tool integration and unified authentication for Continuous Integration and Deployment (CI/CD Continuous Integration/Continuous Deployment)

Users can access tools responsible for source code repositories, artifact repositories, code analysis, image repositories, and build/deployment with a single login.

Project configuration based on application template

Users can easily configure a project using a wizard-style approach with templates that incorporate development standards.

Major development languages and frameworks provided

Users can select the development languages (Java, C#, Python, Ruby, etc.) and frameworks (SpringBoot, Vue.js, .Net, etc.) required for application development to configure a project for building and deployment.

Automatic Build/Deployment Pipeline Configuration

Users can automatically generate pipeline scripts using the build/deployment pipeline templates included in the application template, or configure each pipeline stage through a GUI-based approach.

Support for multiple deployment methods and rollback

Users can employ deployment strategies (RollingUpdate, Blue-Green) to minimize downtime of running applications, and can roll back to a desired version with a single click. If users wish to use a VM server as the deployment environment, they can deploy to the VM server in the form of packaged files or Docker images.

Custom Release Process Support

Users can define and repeatedly execute various release processes, taking into account the type of application changes.

Component

Users can easily use the DevOps Service through the DevOps Console.

DevOps Console

It provides integrated support for the tools required for application development and build/deployment, allowing easy management of project configuration and build/deployment.

Dev. Starter

It is an application template that provides not only sample code reflecting development standards but also integrated templates required for build and deployment.

IDP(ID Provider)

It manages users centrally and handles authentication.

Source Code Repository

Supports integration with source code version control tools.

Artifact Repository

Supports integration with an artifact repository for storing libraries required for application builds and application artifacts.

code quality

Supports integration with code quality tools that can measure and manage source code quality through static code analysis.

Helm chart repository

In Kubernetes, Helm charts are used to easily install and upgrade software. Users must create Helm charts themselves to install software. It provides ChartMuseum as the default repository for managing Helm charts. It also supports integration with other chart repository tools.

Image Repository

Supports integration with an image registry for storing container images.

VM Server Group

A group of VM servers that serve as the deployment target for the application. Users can register VMs and designate them as deployment targets in the DevOps Console.

Kubernetes Cluster

The cluster that serves as the deployment target for the application. Users can register a Kubernetes Cluster in the DevOps Console and designate it as a deployment target.

Key concepts and relationships

System administrators (System Admin) or administrators (Admin) must predefine the tools and application templates required when a user creates a project.

tenant

It is a logical unit that independently provides and shares tools and application templates usable in projects. The system administrator registers a tenant for each organization (or client) unit that must guarantee independence and assigns a tenant administrator. The tenant administrator can register tenant tools, application templates, and tenant members that can be used within that tenant.

Project Group

As a unit for managing individual projects, a member belonging to a specific tenant can create a project group. Therefore, a project group belongs to a single tenant and can utilize the tools and templates configured for that tenant.

project

A project is a unit that develops and manages an application or microservice that is deployed and run independently. Consequently, it is common to structure a project around a single source code repository, but it can be flexibly organized according to the characteristics of the application or the development and operations teams.

tool

It is a development tool that supports source code repositories, image registries, build/deployment pipelines, and code quality used in projects. Each project can use the tools assigned to its project group, tenant, or the Kubernetes Cluster that is the deployment target of the application. Typically, when assigned at the cluster level, the tools support build/pipelines and image registries that affect deployment speed. Tools are broadly classified into three types based on their scope of use.

Application Template

This is a template that makes it easy to set up a project. A template that reflects development standards and even provides sample code is called Dev. Starter, while a template that simply supports development environment setup is called Environment Only. Like tools, it is divided into three main types based on the scope of use.

2.1.2 - Roles

Project group roles and permissions

• The project group creator has Owner permission by default.
• Master lacks the project group deletion permission among the Owner’s permissions.
• Developers and Viewers have view‑only permissions.

Project roles and permissions

• They are classified as Owner, Master, Developer, and Viewer.
• Viewer can only view.
• Developers can create or delete development-related functions.
  • Example) build pipeline, Helm chart, deployment
• Owner/Master can view, create, and delete all functions within a project.
• The project role holder inherits the role holder of the project group.
• Even if you are not registered as a project member, you can perform the role in the project if you are a member of the project group.
• When a user’s project role and project group role differ, the project role takes precedence.
  • In other words, you can restrict permissions for a specific project among the members of a project group.
• Example) If you do not want to grant Master permissions to the Master role holder of a project group for a specific project, register them as a project member and assign Developer or Viewer permissions.

• Jenkins system permissions
  • Access permissions are granted based on the project permission hierarchy of DevOps Console.
    • Jenkins system permission table by role within the project reference
  • Permissions are assigned to the Jenkins pipeline based on the project’s role assignments.
  • For tools other than Jenkins, you can set permissions in the tool’s menu.

System roles and permissions

2.1.3 - Screen Configuration

Describes the main menu pages of DevOps Console.

When you first log in, the top menu and all project groups and projects you have permission for are displayed.

Top menu

Through the top menu, you can navigate to the Main screen, Management screen, etc., and edit user information. The top menu is always displayed while using DevOps Console.

Main Page

Displays the status of all project groups and projects for which the user has permissions.

Admin Page

It includes overall management functions of the DevOps Console, such as dashboard, tenant, project, tool, and user.

Project Group Management Page

This is the management page for project groups and releases.

Project page

This is a page about the project.

2.2 - Getting Started

2.2.1 - Getting Started with DevOps Console

Describes how to log in to the DevOps Console and set the display language and user information.

Sign up

To use DevOps Console, you need to create a DevOps Console account that is separate from Samsung Cloud Platform, and you can create the account through sign‑up.

To create an account in DevOps Console, follow the steps below.

1. Click the Sign Up link on the login page. You will be taken to the sign‑up page.
2. Please proceed with Identity verification. When identity verification is complete, click the Next button.

   Item	Required status	Explanation
   Auto Input Prevention	Required	Enter the characters displayed in the image into the input field.

   Table. Authentication Information
3. Please agree to the terms of the Sign-up Information item.

   Item	Required status	Explanation
   Terms of Service	Required	Check if the service terms are agreed
   Privacy Policy	Required	Check consent for collection and use of personal information
   Must be at least 14 years old.	Required	Check whether the user is 14 or older.

   Table. Sign-up Information Input
4. Enter the required information for the Member Information field.

   Item	Whether required	Explanation
   User ID (email)	Required	Email to be used as the subscriber ID
   mobile phone number	Required	Enter mobile phone number Enter the mobile phone number and click the OTP Send button to generate an OTP Enter the OTP number received on the mobile phone and click the Verify button If the OTP is valid, mobile phone number verification is completed
   Password	Required	The password that the subscriber can use must be entered within 8 to 20 characters User ID or name cannot be used as the password Must include at least one uppercase letter (English), one lowercase letter (English), one digit, and one special character (! @ # $ % ^ & *) The same character cannot be used three or more times Sequences of four or more consecutive letters or numbers are not allowed Password change interval: 90 days
   Confirm Password	Required	Confirm the password the subscriber will use
   Name	Required	Subscriber name Can be entered using letters, numbers, and spaces, up to 100 characters
   language	Required	Notification language settings for email, SMS, etc.
   Time zone	Required	Set user’s timezone information

   Table. Member Information Input
5. After entering all the information, click the Complete button, and a verification email will be sent to the entered email address.
   • Click the Email address verification button in the received email to complete registration.

Log in

To log in to DevOps Console, enter your account information on the login page and click the Next button.

After entering the OTP number issued for the selected OTP type on the OTP authentication page, click the Login button.

If you cannot remember your ID or password, click the ID/Password Recovery link, locate your account information first, and then attempt to log in.

After logging in, the DevOps Console main page opens.

Edit User Information

To edit user information, follow these steps.

1. Click the Shortcut icon at the upper right of the Main page.
2. DevOps IDP Click the link. DevOps IDP page opens in a new tab.
3. You can change information such as mobile phone number, password, name, timezone, and language on the user information page.

To modify the information used in DevOps Console, follow these steps.

1. Click the User icon in the top menu of the Main page.
2. Click the Account Information menu. The Account Information popup window opens.
3. After changing the language and time zone information, click the Save button to complete updating your account information.

Changing Console Language

To change the language displayed in DevOps Console, after logging in, click Language Settings located below the DevOps Console page to select the desired language.

Manage authentication keys

You can manage each user’s individual authentication keys through the Authentication Key Management menu after clicking the User icon in the top menu of the Main page.

Add authentication key

To add an authentication key, follow these steps.

1. Click the User icon at the top right of the Main page.
2. Click the Authentication Key Management menu. The Authentication Key Management popup window opens.
3. Click the Create Authentication Key button. The Create Authentication Key popup will appear.
4. After setting the expiration date, click the Save button to complete the creation of the authentication key.

Configure security settings

You can restrict the IPs that are allowed to use this authentication key through security settings.

To add security settings, follow these steps.

1. Click the User icon at the top right of the Main page.
2. Click the Authentication Key Management menu. The Authentication Key Management popup window opens.
3. Click the Security Settings tab, then click the Edit button. The Change Security Settings popup window opens.
4. Set IP access control to use.
5. After entering the allowed IP, click the Save button to complete the security settings.

Delete authentication key

To delete the authentication key, follow these steps.

1. Click the User icon at the top right of the Main page.
2. Click the Authentication Key Management menu. The Authentication Key Management popup window opens.
3. Click the Status Change button.
4. When the Authentication Key Status Change popup opens, process it as Unused and click the Save button.
5. Click the Delete button to complete the authentication key deletion.

Check My Activity History

If you click the User Icon > My Activity History menu in the top menu of the Main page, you can view your DevOps Console activity history.

Configure Access Control IP

You can register IP addresses that are allowed to access the DevOps Console to control access.

Follow these steps to register an access control IP.

1. Click the Main page’s top‑right shortcut icon.
2. DevOps IDP Click the link. DevOps IDP page opens in a new tab.
3. Click the Access Control menu in the left menu.
4. On the Access Control page, click the Edit button below. You will be taken to the Access Control Edit page.
5. Set Access Control IP Settings to Enable.
6. After adding the IP to allow access, click the Save button to complete the access control settings.

Delete Account

To delete your DevOps Console account, follow the steps below.

1. Click the Main page’s top‑right shortcut icon.
2. DevOps IDP Click the link. DevOps IDP page opens in a new tab.
3. On the user information page, click the Delete Account button at the top right. The Delete Account popup will appear.
4. Enter your current password in the input field, then click the Delete Account button to complete the deletion.

2.2.1.1 - Registration Information

Users can view and manage their basic information, authentication information, subscribed tenants, subscribed project groups, and subscribed projects.

Getting Started with Sign-up Information

To start managing your registration information, follow these steps.

1. Main page, click the Admin icon in the upper right. Navigate to the Tenant Dashboard page.
2. Please click the Sign-up Information menu in the left menu. It navigates to the Sign-up Information page.

Managing authentication information

Authentication information automatically saves the credentials the user used for tool registration, usage, and related activities. If necessary, you can add new credentials, or modify or delete existing credentials.

To manage authentication information, follow the steps below.

1. Click the Admin icon at the top right of the Main page. You will be taken to the Tenant Dashboard page.
2. Click the Registration Information menu in the left menu. You will be taken to the Registration Information page.
3. On the Registration Information page, click the Authentication Information tab.

Add authentication information

To add authentication information, follow these steps.

1. In the Credentials tab, click the Add button. The Add Credentials popup opens.
2. Add Authentication Info Enter the information in the popup window.
3. All tools and URLs that the user can access are displayed.
4. After completing the information entry, click the Connection Test button.
5. Click the Save button.

Modify authentication information

To modify the authentication information, follow these steps.

1. In the Authentication Information tab, click the authentication information you want to edit. The Edit Authentication Information popup will open.
2. Edit Authentication Information After entering the information in the popup window, click the Connection Test button.
3. Save button is enabled, click the Save button.

Delete authentication information

To delete the credentials, follow these steps.

1. In the Credential tab, select the checkbox of the credential you want to delete.
2. Click the Delete button in the Authentication information list.
3. In the confirmation popup, click the Confirm button.

Manage Subscribed Tenants

Users can view the list of tenants they have joined.
You can also request to join a new tenant, and you can leave a tenant you are already a member of.

To manage the tenant you have joined, follow these steps.

1. Click the Admin icon at the top right of the Main page. You will be taken to the Tenant Dashboard page.
2. Click the Sign-up Information menu in the left menu. You will be taken to the Sign-up Information page.
3. On the Registration Info page, click the Registered Tenant tab.

Request tenant registration

To request tenant enrollment, follow the steps below.

1. Click the Join button in the Joined Tenant tab. The Tenant Join Request popup window opens.
2. Tenant Registration Request In the popup window, enter the tenant code you wish to register and click the Search icon.
3. Enter the request reason and click the Add button.
4. After selecting the permissions of the added tenant, click the Save button.
5. Click the Confirm button in the confirmation popup.

Leave tenant

To withdraw from the tenant, follow the steps below.

1. In the Joined Tenants tab, select the checkbox of the tenant you wish to withdraw.
2. Click the Delete button.
3. In the confirmation popup, click the Confirm button.

Manage Joined Project Groups

Users can view the list of project groups they have joined.

To manage the project groups you have joined, follow these steps.

1. Click the Admin icon at the top right of the Main page. You will be taken to the Tenant Dashboard page.
2. From the left menu, click the Sign-up Information menu. You will be taken to the Sign-up Information page.
3. On the Sign-up Information page, click the Joined Project Group tab.

When you click a project group in the project group list, you are taken to the Project Group Management page.

For detailed information on project group management, please refer to the Project Group Overview.

Manage Joined Projects

Users can view the list of projects they have joined.

To manage the projects you have joined, follow these steps.

1. Click the Admin icon at the top right of the Main page. You will be taken to the Tenant Dashboard page.
2. Click the Sign-up Information menu in the left menu. You will be taken to the Sign-up Information page.
3. On the Sign-up Information page, click the Joined Projects tab.

When you click a project in the project list, you are taken to the Project Management page.

For detailed information about the project, see the 프로젝트.

2.2.2 - Tutorial (From Project Creation to Build/Deploy)

Through the following steps, the user can create a DevOps Console project, build the source to create an image, and deploy the Helm chart to a Kubernetes cluster.

Create Project Group

Users can create a project group. Users must be a member of the tenant where they will create the project group.

Create Project Group

To create a project group, follow these steps.

1. On the Main page, click the Create Project Group and Start button or the Create Project Group button. The Create Project Group popup opens.
2. After entering the items, click the Save button to complete the creation of the project group.

Register Tenant

To join a tenant, follow these steps.

1. In the Create Project Group popup, click the Tenant Join Shortcut link. The Tenant Join Request popup opens.
2. Enter the tenant code to register in the Tenant Search field accurately and click the Search icon. The tenant information will be retrieved.
3. Verify that the displayed tenant is correct, enter the request reason, and click the Add button. It will be added to the list below.
4. After selecting the permissions for the tenant added to the list below, click the Save button.

(Helm chart deployment)Create a project

Users can create a project that deploys an application to a specific Kubernetes cluster using App.Template, Helm Chart, and Tool Management.

Start Project Creation

To start creating a project, follow these steps.

1. On the Main page, click the Create Project button. The Create Project page opens.

Enter basic information

Enter the basic information of the project. The project name and project ID must be unique and cannot be duplicated.

To enter the basic information, follow the steps below.

1. On the Project Creation page, select the App. Template Utilization option of the Project Configuration Method item.
2. For the deployment target field, select Kubernetes.
3. After entering additional content, click the Start button.

   Item	Explanation
   Project name	Please enter the project name.
   Project ID	Please enter the project ID.
   Project configuration method	Select a project configuration method Use App template: select a pre‑provided App template. Manual configuration: configure without an App template.
   deployment target	Select 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): Package the application as a Docker image and deploy it to a VM server. N/A: Choose this when you do not deploy the build output.
   K8S cluster	Select the target cluster for deployment DevOps Console Only clusters that the user has access rights to can be selected among the K8S clusters.
   namespace	Select the target namespace for deployment Only namespaces that the user has access rights to, among the clusters retrieved from the K8S cluster, can be selected.

   Table. Project creation basic information entry items

Select Application Template

The user can select an application template to configure the project.

If you create a project based on an application template that includes sample source code, you can view the application that will be deployed.

In contrast, using a template labeled Environment Only configures only the build/deployment environment without sample source code.

If you configure a project using an already set up source code repository, select the template marked Environment Only.

To start selecting an application template, follow these steps.

1. On the Application Template screen, enter the template name, select the application template card you want, and then click.
2. When the Next button is enabled, click the Next button.

   Item	Explanation
   Filter	You can easily find application templates using predefined filters.
   search	You can easily find application templates through search.

   Table. Project Creation Application Template Items

Set up the code repository

Users can configure a repository for managing source code through the code repository setup step.

Create new repository and use existing repository activation conditions differ depending on the application template and tool.

To modify or delete stored credentials, refer to Manage Authentication Information.

To set up the code repository, follow these steps.

1. In the Code repository item, select the Code repository type.
2. Select Create new repository or Use existing repository, then enter the information.
3. Enter authentication information and click the Connection Test button.
4. When the Next button is enabled, click the Next button.

   Item	Explanation
   Repository type	Select the code repository to use Registered tool: The user can select and use the types of SCM Repository tools (Github, Gitlab, etc.) that are available. Unregistered tool: You can enter the domain of an unregistered tool to use it. The unregistered tool entry appears only when the source code is not included (Environment Only) App. Template.
   New/Existing usage	Please select New repository creation or whether to use an existing repository. Activation status varies depending on specific conditions. For details, refer to Table. Activation conditions for creating a new repository and using an existing repository.
   Repository information	Enter repository information When creating a new repository, the URL is formed from the project group name/project name.
   Authentication information	Enter authentication information If you do not have an account, Don’t have an account? click the link to open the Account Creation Information popup where you can create an account. After creating a new account, be sure to change your password via the Set Initial Password link.
   (Unregistered tool) Repository information	Enter repository information You can use a code repository that is not registered as a tool in DevOps Console. Click the URL Check button to undergo an additional verification process.

   Table. Project Creation Code Repository Settings

Configure code quality

Users can configure a repository for quality management.

To set code quality, follow these steps.

1. In the Code Quality item, select Repository Type.
2. Enter Basic Information and Authentication Information, then click the Connection Test button.
3. Next button is enabled, click the Next button.

   Item	Explanation
   Repository type	Select the repository to use The types of Code Quality tools available to the user are displayed.
   New / Existing / Unused status	Select repository creation method If you select Create new repository, you must enter the quality project name/quality project key. If you select Do not create, you can proceed directly to the next step.
   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 credentials You can create a new user or use existing authentication credentials.

   Table. Project Creation Code Quality Settings

Configure image repository

Users can configure a repository to store the built container images through the image repository configuration step.

To modify or delete stored credentials, refer to Manage Authentication Information.

To set up the image repository, follow these steps.

1. In the Image Repository item, select the Repository Type.
2. Create new repository / Use existing repository select, then enter the information.
3. Enter authentication information and click the Connection Test button.
4. When the Next button is enabled, click the Next button.

   Item	Explanation
   Repository type	Select the repository type to use The types of Image Registry tools available to the user are displayed.
   Repository information	Select the repository creation method. When creating a new repository, the URL is formed with the project group name/project name.
   Authentication information	Enter your credentials.

   Table. Project Creation Image Repository Settings

Configure the deployment target environment

Users can deploy by directly configuring via Helm charts.

Helm release name and Helm chart when selected, the Helm chart installation options and the default Values.yaml entries included in the chart are displayed.

Available Helm charts are associated with the App template. You can edit or delete them through Manage supported Helm charts.

To set the deployment target environment, follow these steps.

1. In the Deployment target field, select Configure directly via Helm chart.
2. Please enter the Helm release name.
3. Click the Search button to select the Helm chart to use.
4. After editing Values.yaml, click the Validation Check button.
5. When the Next button is enabled, click the Next button.

   Item	Explanation
   deployment target	Please select the deployment target.
   Helm release name	Enter the name of the Helm release to create. The name must be unique within the namespace of the target cluster.
   Helm chart	Select a Helm chart. When a Helm chart is selected, detailed information about the chosen chart is displayed below
   K8S information	Shows the information of the Kubernetes cluster required for configuring Value.yaml.
   Values. yaml	Edit the contents of Values.yaml. values.yaml file to be used when installing the Helm chart.

   Table. Project creation deployment target environment configuration items

Setting up the Build Pipeline

Users can configure pipelines that build and deploy applications.

You can view each stage of the pipeline to be configured and rename the build job.

To set up the build pipeline, follow these steps.

1. Build Pipeline screen branches based on IDP integration status.
   • For IDP-integrated Jenkins, click the User Check button to perform User Registration Confirmation.
   • For Jenkins not integrated with IDP, enter the authentication information and click the Connection Test button.
2. When the Next button is enabled, click the Next button.

   Item	Explanation
   Build/Deployment pipeline	Displays build/deployment pipeline information. The build/deployment pipeline is displayed based on the information registered in the App template’s Manage Pipeline Templates.
   Category	Select the development/operation distinction. The permissions for the pipeline vary according to the development/operation distinction. Refer to Table. Role-based permissions within the project (1) for role-based permissions.
   URL	Select Jenkins to configure the pipeline, then enter the job name. The Jenkins instances available to the user are displayed.
   Build Agent	Select the agent to be used for pipeline builds. For information about the agent, please refer to Managing agents (kubernetes), Managing agents (VM).
   Build environment OS	Displays the OS information of the environment in which the build agent runs.
   User information	IDP Integrated Jenkins Click the User Check button to verify user registration. If you are not registered as a Jenkins user, when the User Registration Guide popup appears, click the Go to Jenkins link to proceed with User Sign‑Up or Initial Jenkins Login. IDP Non‑Integrated Jenkins Enter the authentication information and click the Connection Test button.
   Set environment variables	Set the environment variables to be registered in the Jenkins pipeline.
   Image Tag Pattern	Select the tag assignment method for the container image.
   Deploy Strategy	Select the deployment method for the container image.
   Recipient of deployment results	Select the user who will receive the results after the build pipeline completes.

   Table. Project creation build pipeline configuration items

Customize Settings

The user can specify and modify the path of the Dockerfile file used for the build.

Additionally, you can view the final script generated based on the information configured in 빌드 파이프라인 설정하기 and also edit it.

Dockerfile, follow these steps to configure the pipeline script.

1. After entering information on the Custom settings page, click the Connection Test button.
2. Click the Next button when the Next button is enabled.

   Item	Explanation
   Dockerfile configuration	Create New Dockerfile or Use Existing Dockerfile. Please select. «Use Existing Dockerfile is only selectable after choosing the Environment Only App template and, in 코드 저장소 설정하기, selecting Use Existing Repository.
   Dockerfile path	Specify the Dockerfile file path in the source code.
   Branch name	The branch name is automatically registered when you set it in Code Repository Configuration.
   Dockerfile	Check and modify the contents of the Dockerfile.
   pipeline script	Check and modify the pipeline script.

   Table. Project Creation Custom Settings Items

Complete project creation

The user can review the project and tool information to be created and start project creation.

To complete project creation, follow the steps below.

1. Summary Information After checking the information on the screen, click the Complete button.
2. Project Creation popup window opens and the project creation proceeds.
3. After the project creation is complete, click the Confirm button to go to the Project page.

Check Build Pipeline Execution

On the Project page, you can view the pipeline execution status, and once the initial project creation is complete, the build pipeline runs automatically.

If the build pipeline fails, use the left Build Pipeline menu to modify and rerun the pipeline.

To verify the build pipeline execution, follow these steps.

1. On the Main page, click the Project card. You will be taken to the Project Dashboard page.
2. Click the Build/Deploy > Build Pipeline menu in the left menu.

Check deployment results

After the pipeline finishes running, you can check the Helm chart deployment results.

For detailed information about the Helm chart deployment results, refer to the Helm release.

To verify the deployment results, follow the steps below.

1. Main page, click the Project card. Project Dashboard page will be displayed.
2. Click the Build/Deploy > Kubernetes Deploy menu in the left menu. You will be taken to the Kubernetes Deploy page.
3. Click the Helm Release list to view detailed deployment results.

2.2.2.1 - Add Build/Deploy (Helm Chart Deployment)

The user can, through the following steps, create a new build pipeline in an already created DevOps Console project, build the source to create an image, and perform Helm chart deployment to a Kubernetes cluster.

Through Helm install, the deployed Helm release will be used in Deploy to K8S stage configuration.

Getting Started with Build/Deploy Additions

To begin adding build and deployment, follow these steps.

1. Click the Project card on the Main page. You will be taken to the Project Dashboard page.

Add code repository (Option)

To add a code repository, follow these steps.

1. On the Main page, click the Project card. You will be taken to the Project Dashboard page.
2. Click Repository > Code Repository in the left menu.
3. Click the Add Code Repository button at the top right. The Add Code Repository page opens.
4. Enter/set each item and click the Connection Test button.
5. Click the Save button to complete Add code repository.

   Item	Explanation
   Repository type	Select the repository to use Registered tool: The user can select and use the types of SCM Repository tools (Github, Gitlab, etc.) that are available. Unregistered tool: You can enter the domain of a tool that will not be registered to use it. The unregistered tool option appears only for App templates that do not include source code (Environment Only).
   New/Existing usage	Select Create new repository or Use existing repository The activation status changes depending on specific conditions. For more information, see Table. Conditions for activating new repository creation and existing repository usage.
   Repository information	Enter repository information When creating a new repository, the URL is formed from the project group name/project name.
   Authentication information	Enter authentication credentials.
   Repository information	Enter repository information You can use a code repository that is not registered as a tool in DevOps Console. Click the URL Check button to proceed with the verification process.

   Table. Code Repository Configuration Items

Add image repository (Option)

To add an image repository, follow these steps.

App. Add image repository

1. On the Image Repository page, click the App. Add Image Repository button in the upper right. You will be taken to the App. Add Image Repository page.
2. App. Add Image Repository page, enter and configure each item.
3. Connection Test Click the button.
4. Click the Save button.

   Item	Explanation
   Select repository type	Select the image repository type. To use an image repository not registered in the Devops Console, select the Image Registry type.
   Choose whether to create a repository	Choose whether to create a new repository or use an existing one. If you selected the Docker hub or Image Registry type earlier, you can only select Use existing repository.
   Registered tool	Enter repository information.
   Unregistered tool	Enter repository information You can register an image repository that is not registered with the DevOps Console tool. Click the URL Check button to proceed with the verification process. Only Use existing repository can be selected.

   Table. App. Add Image Repository Input Fields

Add pull-only image repository

1. On the Image Repository page, click the Add Pull-Only Image Repository button in the upper right. You will be taken to the Add Pull-Only Image Repository page.
2. Add Pull‑only Image Repository On the page, enter and configure each field.
3. Connection Test Click the button.
4. Click the Save button.

Install Helm

To install Helm, follow these steps.

1. Click the Project card on the Main page. You will be taken to the Project Dashboard page.
2. Click the Build/Deploy > HelmInstall menu in the left menu.
3. In the K8S cluster field, select the K8S cluster you wish to install.
4. Click the Helm chart you want to install to go to the Helm Chart Details screen.
5. Click the Helm Install button. It navigates to the Helm Chart Install screen.
6. Enter each item and click the Next button.

   Item	Explanation
   Release name	Enter the name to use in the Helm chart release. It must be unique and cannot be duplicated within the namespace.
   Category	Development, Operations
   Version	Select the version of the chart you want to install with Helm.
   K8S cluster	Displays the target K8S cluster for Helm install. Changes cannot be made, and if you wish to change, please select the K8S cluster from Start Helm Install.
   namespace	Select the target namespace for the helm install from the list.
   Reference information	This is reference information provided by the selected K8S cluster. Click each tab to view detailed information.
   Default Values.yaml included in the chart	You can edit the values.yaml file to run helm install with the desired values. If needed, refer to the reference information and edit the values.yaml file with those values.
   Writing type	Form type items are displayed only for Helm charts that support Form input Form: Enter the items shown on the screen. For creating Helm charts that support Form input, see Creating Helm charts that support Form input. values.yaml: Edit values in the yaml editor screen just like a regular Helm chart. Form / values.yaml input can be toggled, but switching clears any previously entered data.
   Form input	This is the screen displayed when you select Form in the creation type; review each item and enter the values. After completing the entry, click the Validation Check button to verify the input values.

   Table. Helm Install Configuration Items
7. Helm chart installation A popup window opens. Click the Run button to complete the Helm install.
8. When the installation is complete, the Kubernetes deployment page opens.

Add Build Pipeline

To add a build pipeline, follow these steps.

1. On the Main page, click the Project card. You will be taken to the Project Dashboard page.
2. In the left menu, click the Build/Deploy > Build Pipeline menu. You will be taken to the Build Pipeline page.
3. Build Pipeline page, click the Add Pipeline button at the top right. You will be taken to the Add Pipeline page.
4. Add Pipeline Enter or configure each field on the page.
5. Click the Next button.

   Item	Explanation
   Category	Select Development or Operations The actions that each role can perform differ depending on development or operations. Refer to Table. Role-specific permissions within the project (1) for role-specific permissions.
   Jenkins URL	Select Jenkins from the list to add a build pipeline.
   Build Agent	Select the agent (build environment) on which the build pipeline will run. Click the Info icon to view the list of tools provided by the agent.
   Build environment OS	Displays the OS information of the environment where the build agent runs.
   Folder type	Select the folder type. Existing folder: Add a pipeline under an already created folder in Jenkins. New folder: Create a new folder in Jenkins and add a pipeline under it.
   folder	Select a folder from the list or enter the name of a new folder to create.
   Pipeline name	Please enter the pipeline name.
   Parameter setting	Set the parameters to be used in the pipeline.
   Environment variable configuration	Set the environment variables to be used in the pipeline.
   Stage Settings	Configure the stage to be used in the pipeline.
   Configure email recipients for build results	Set the recipients who will receive the result email after the pipeline completes (success/failure).

   Table. Additional Build Pipeline Settings

Setting parameters

Follow these steps to set the parameters to use when running the pipeline.

1. Click the Parameter area. The Parameter registration page opens on the right.
2. When you click the Add button, the Add Parameter popup window opens.
3. Add a parameter and click the Apply button to complete the parameter configuration.

Setting Environment Variables

Follow these steps to set environment variables for use in the pipeline.

1. Click the Environment Variable area. The Environment Variable Registration page opens on the right.
2. A list of pre-registered environment variables appears, and select the checkboxes for the environment variables you want to use.
3. Check the selected environment variable and click the Apply button to complete the environment variable configuration.

Configure email recipients for build results

To set the recipients who will receive the build results by email, follow these steps.

1. Click the Mail Recipient area. The Add Mail Recipient page opens on the right.
2. In the Search area, search for the recipient and add them.
3. Click the Apply button to complete the mail recipient settings.

Configure additional stage

Setting up the Checkout stage

To add a Checkout stage, follow these steps.

1. Click the New Stage area. The stage settings page opens on the right.
2. Choose Checkout as the Stage type.
3. Enter the information and click Apply. (In the URL, you can select the code repository you added from Add Code Repository (Option).)

   Item	Explanation
   URL	Select the code repository to perform the checkout.
   Branch name	Enter the name of the branch to checkout.

   Table. Checkout Stage Settings

Configure the Build stage

To add a Build stage, follow these steps.

1. Click the Add icon to add a new stage.
2. Click the New Stage area. The Stage Settings page opens on the right.
3. On the Stage Settings page, select Build as the Stage Type.
4. After entering information on the Stage Settings page, click the Apply button.

   Item	Explanation
   language	Select the programming language used by the application.
   Build tool	Select the Build tool used for building the application. Provides default Shell commands based on the selected Build tool.
   Shell command	Enter the command to use for building the application. All commands available in the Shell can be used.

   Table. Build stage input items

Setting Up Docker Build Stages

To add a Docker Build stage, follow these steps.

1. Click the Add icon to add a new stage.
2. Click the New Stage area. The Stage Settings page opens on the right.
3. Select Docker Build as the Stage Type.
4. After entering the information, click the Apply button. (You can select the image repository you added in Registry URL from Add Image Repository (Option).)

Deploy to K8S Stage Configuration

Deploy to K8S To add a stage, follow the steps below.

1. Click the Add icon to add a new stage.
2. Click the New Stage area. The stage settings page opens on the right.
3. Select Deploy to K8S as the Stage type.
4. After entering the information, click the Apply button. (Type Helm Release (Helm Chart type) can be selected to choose the Helm Release added in 헬름인스톨 하기.)

Check the final pipeline script

1. Check the build pipeline script that will actually be generated. If needed, edit the script directly.
2. Click the Complete button to finish adding the pipeline.

Pipeline addition result

2.2.2.2 - Add Build/Deploy (Workload Deployment)

The user can, through the following steps, create a new build pipeline in an already created DevOps Console project, build the source to create an image, and perform workload deployment on a Kubernetes cluster.

The workload added via Add Workload will be used in Deploy to K8S Stage Setup.

Build/Deploy Add Getting Started

To begin adding build/deployment, follow these steps.

1. Click the Project card on the Main page. You will be taken to the Project Dashboard page.

Add code repository (Option)

To add a code repository, follow these steps.

1. On the Code Repository page, click the Add Code Repository button in the upper right. You will be taken to the Add Code Repository page.
2. On the Add Code Repository page, enter and configure each item.
3. Connection Test Click the button.
4. Click the Save button.

   Item	Explanation
   Repository type	Select the repository to use Registered tools: Users can select and use the types of SCM Repository tools (Github, Gitlab, etc.) that are available. Unregistered tools: You can enter the domain of a tool that is not registered. The unregistered tool entry appears only for App templates that do not include source code (Environment Only).
   New/Existing usage	Select Create new repository or Use existing repository The activation status varies depending on specific conditions. For details, see Table. Conditions for activating new repository creation and existing repository usage.
   Repository information	Enter repository information When creating a new repository, the URL is formed from the project group name/project name.
   Authentication information	Enter authentication credentials.
   Repository information	Enter repository information You can use a code repository that is not registered as a tool in DevOps Console. You must also go through the URL check process.

   Table. Code Repository Add Input Items

Add image repository (Option)

To add an image repository, follow these steps.

App. Add image repository

1. On the Image Repository page, click the App. Add Image Repository button in the upper right. You will be taken to the App. Add Image Repository page.
2. App. Add Image Repository page, enter and configure each item.
3. Connection Test Click the button.
4. Click the Save button.

   Item	Explanation
   Select repository type	Select the image repository type. To use an image repository not registered in the Devops Console, select the Image Registry type.
   Choose whether to create a repository	Choose whether to create a new repository or use an existing one. If you selected the Docker hub or Image Registry type earlier, you can only select Use existing repository.
   Registered tool	Enter repository information.
   Unregistered tool	Enter repository information You can register an image repository that is not registered with the DevOps Console tool. Click the URL Check button to proceed with the verification process. Only Use existing repository can be selected.

   Table. App. Add Image Repository Input Fields

Add pull-only image repository

1. On the Image Repository page, click the Add Pull-Only Image Repository button in the upper right. You will be taken to the Add Pull-Only Image Repository page.
2. Add Pull‑only Image Repository On the page, enter and configure each field.
3. Connection Test Click the button.
4. Click the Save button.

Add workload

To add a workload, follow the steps below.

1. On the Main page, click the Project card. You will be taken to the Project Dashboard page.
2. Click the Build/Deploy > Kubernetes Deploy menu in the left menu. You will be taken to the Kubernetes Deploy page.
3. On the Kubernetes deployment page, click the Add workload menu. The Add workload popup opens.
4. Add Workload Enter the information in the popup window and click the Save button.
5. In the confirmation popup, click the Confirm button to complete adding the workload.

   Item	Explanation
   Query target	Only workloads deployed with the same Base image as the App template used when the project was first created are displayed.
   Workload already registered in the project	Shows the workload already registered in the project. Workloads already registered in the project cannot be added.

   Table. Additional Workload Input Items

Modify K8S authentication information

K8S credentials are the authentication information used to verify permission to use a K8S cluster/namespace when performing a deployment in the build pipeline.

To modify the K8S credentials, follow these steps.

1. On the Deployment Details page, click the Edit Credentials icon to the right of K8S Cluster/Namespace. The Edit Credentials popup will open.
2. Authentication information is fixed to the logged-in user’s account. Click the Save button to edit.
3. In the confirmation popup, click the Confirm button.
4. K8S authentication information will be changed to the logged-in user.

Add Build Pipeline

To add a build pipeline, follow these steps.

1. On the Main page, click the Project card. You will be taken to the Project Dashboard page.
2. In the left menu, click the Build/Deploy > Build Pipeline menu. You will be taken to the Build Pipeline page.
3. Build Pipeline page, click the Add Pipeline button at the top right. You will be taken to the Add Pipeline page.
4. Add Pipeline Enter or configure each field on the page.
5. Click the Next button.

   Item	Explanation
   Category	Select Development or Operations The actions that each role can perform differ depending on development or operations. Refer to Table. Role-specific permissions within the project (1) for role-specific permissions.
   Jenkins URL	Select Jenkins from the list to add a build pipeline.
   Build Agent	Select the agent (build environment) on which the build pipeline will run. Click the Info icon to view the list of tools provided by the agent.
   Build environment OS	Displays the OS information of the environment where the build agent runs.
   Folder type	Select the folder type. Existing folder: Add a pipeline under an already created folder in Jenkins. New folder: Create a new folder in Jenkins and add a pipeline under it.
   folder	Select a folder from the list or enter the name of a new folder to create.
   Pipeline name	Please enter the pipeline name.
   Parameter setting	Set the parameters to be used in the pipeline.
   Environment variable configuration	Set the environment variables to be used in the pipeline.
   Stage Settings	Configure the stage to be used in the pipeline.
   Configure email recipients for build results	Set the recipients who will receive the result email after the pipeline completes (success/failure).

   Table. Additional Build Pipeline Settings

Setting Parameters

Follow these steps to set the parameters used when running the pipeline.

1. Click the Parameter card.
2. Click the Add button to add a parameter.
3. Click the Apply button to complete the parameter settings.

Setting Environment Variables

Follow these steps to set environment variables for use in the pipeline.

1. Click the Environment Variable area. The Environment Variable Registration page opens on the right.
2. A list of pre-registered environment variables appears, and select the checkboxes for the environment variables you want to use.
3. Check the selected environment variable and click the Apply button to complete the environment variable configuration.

Configure email recipients for build results

To set the recipients who will receive the build results by email, follow these steps.

1. Click the Mail Recipient area. The Add Mail Recipient page opens on the right.
2. In the Search area, search for the recipient and add them.
3. Click the Apply button to complete the mail recipient settings.

Add additional stage

Checkout stage setup

To add a Checkout stage, follow these steps.

1. Click the New Stage area. The Stage Settings page opens on the right.
2. On the Stage Settings page, select Checkout as the Stage Type.
3. After entering the information, click the Apply button. (You can select the code repository you added from 코드 저장소 추가하기 (Option) on the URL.)

   Item	description
   URL	Select the code repository to perform the checkout.
   Branch name	Enter the name of the branch to checkout.

   표. Checkout 스테이지 입력 항목

Setting up the Build stage

To add a Build stage, follow these steps.

1. Click the Add icon to add a new stage.
2. Click the New Stage area. The Stage Settings page opens on the right.
3. On the Stage Settings page, select Build as the Stage Type.
4. After entering information on the Stage Settings page, click the Apply button.

   Item	Explanation
   language	Select the programming language used by the application.
   Build tool	Select the Build tool used for building the application. Provides default Shell commands based on the selected Build tool.
   Shell command	Enter the command to use for building the application. All commands available in the Shell can be used.

   Table. Build stage input items

Docker Build Stage Setup

To add a Docker Build stage, follow these steps.

1. Click the Add icon to add a new stage.
2. Click the New Stage area. The Stage Settings page opens on the right.
3. Select Docker Build as the Stage Type.
4. After entering the information, click the Apply button. (You can select the image repository you added in Registry URL from Add Image Repository (Option).)

Deploy to K8S Stage Setup

Deploy to K8S To add a stage, follow the steps below.

1. Click the + icon to add a new stage.
2. Click the New Stage area. The Stage Settings page opens on the right.
3. On the Stage Settings page, select Deploy to K8S as the Stage Type.
4. On the Stage Settings page, after entering the information, click the Apply button. (If you select a workload in the type, you can select the workload added in 워크로드 추가하기.)

Check the final pipeline script

1. Check the build pipeline script that will actually be generated. If needed, edit the script directly.
2. Click the Complete button to finish adding the pipeline.

Pipeline addition result

2.2.2.3 - Add Build/Deploy (VM Deployment)

The user can, through the following steps, create a new build pipeline in an already created DevOps Console project, build the source to create an image, and proceed with (VM deployment) on the VM server.

The VM server group/VM server added via Add VM Server Group/VM Server (Option) will be used in Configure Deploy to VM Stage.

Build/Deploy Add Getting Started

To begin adding build/deployment, follow these steps.

1. On the Main page, click the Project card to go to the Project Dashboard page.

Add code repository (Option)

To add a code repository, follow these steps.

1. On the Code Repository page, click the Add Code Repository button in the upper right. You will be taken to the Add Code Repository page.
2. On the Add Code Repository page, enter and configure each item.
3. Connection Test Click the button.
4. Click the Save button.

   Item	Explanation
   Repository type	Select the repository to use Registered tools: Users can select and use the types of SCM Repository tools (Github, Gitlab, etc.) that are available. Unregistered tools: You can enter the domain of a tool that is not registered. The unregistered tool entry appears only for App templates that do not include source code (Environment Only).
   New/Existing usage	Select Create new repository or Use existing repository The activation status varies depending on specific conditions. For details, see Table. Conditions for activating new repository creation and existing repository usage.
   Repository information	Enter repository information When creating a new repository, the URL is formed from the project group name/project name.
   Authentication information	Enter authentication credentials.
   Repository information	Enter repository information You can use a code repository that is not registered as a tool in DevOps Console. You must also go through the URL check process.

   Table. Code Repository Add Input Items

Add image repository (Option)

To add an image repository, follow these steps.

App. Add image repository

1. On the Image Repository page, click the App. Add Image Repository button in the upper right. You will be taken to the App. Add Image Repository page.
2. App. Add Image Repository page, enter and configure each item.
3. Connection Test Click the button.
4. Click the Save button.

   Item	Explanation
   Select repository type	Select the image repository type. To use an image repository not registered in the Devops Console, select the Image Registry type.
   Choose whether to create a repository	Choose whether to create a new repository or use an existing one. If you selected the Docker hub or Image Registry type earlier, you can only select Use existing repository.
   Registered tool	Enter repository information.
   Unregistered tool	Enter repository information You can register an image repository that is not registered with the DevOps Console tool. Click the URL Check button to proceed with the verification process. Only Use existing repository can be selected.

   Table. App. Add Image Repository Input Fields

Add pull-only image repository

1. On the Image Repository page, click the Add Pull-Only Image Repository button in the upper right. You will be taken to the Add Pull-Only Image Repository page.
2. Add Pull‑only Image Repository On the page, enter and configure each field.
3. Connection Test Click the button.
4. Click the Save button.

Add artifact repository (Option)

To add an artifact repository, follow these steps.

1. Click the Add Artifact Repository button at the top right of the Artifact Repository page. You will be taken to the Add Artifact Repository page.
2. On the Add Artifact Repository page, enter and configure each item.
3. Connection Test Click the button.
4. Click the Save button.

   Item	Explanation
   Select whether to create a repository	Choose whether to create a new repository or use an existing one.
   Enter basic information	Base URL, select repository type and enter repository/authentication information.

   Table. Input fields for adding an artifact repository

Add VM Server Group/VM Server (Option)

To add a VM server group, follow these steps.

1. Click the Management icon at the top right of the Main page. You will be taken to the Tenant Dashboard page.
2. Click the Deployment Target > VM Server Group menu in the left menu. You will be taken to the VM Server Group page.
3. On the VM Server Group page, click the Add button. It navigates to the Add VM Server Group page.
4. Enter the basic information, then click the Save button to complete the VM server group configuration.

   Item	Explanation
   Server group name	Enter the VM server group name.
   Explanation	Please enter a description.
   type	Select the type of VM server group SSH: Perform deployment using SSH commands when deploying a VM. Agent: Perform deployment using an agent when deploying a VM. (Connect Agent)
   VM server	Add: Add the VM server that belongs to the VM server group. Delete: Check the checkbox of the VM server you want to delete from the VM server group, then click Delete to remove it.

   Table. VM Server Group Add Input Items

Add VM server

To add a VM server, you need Manager permission for the corresponding VM server group.

To add a VM server, follow the steps below.

1. Click the Admin icon at the top right of the Main page. Navigate to the Tenant Dashboard page.
2. Click the Deployment Target > VM Server Group menu in the left menu. You will be taken to the VM Server Group page.
3. VM server group page, click the VM server group in the VM server group list where you want to add a VM server. You will be taken to the VM server group detail page.
4. On the VM Server Group Details page, click the Add button. You will be taken to the Add VM Server page.
5. Add VM Server page, after entering the basic information, click the Add button to complete the VM server configuration.

   Item	Explanation
   Server name	Enter the VM server name.
   Explanation	Enter the description.
   IP	Please enter the IP.
   SSH Port	Enter the port of the VM server to use for SSH connections.
   OS	Please enter the OS.
   Location	Please select a location.
   Authentication information	Enter the authentication information for the VM server to be used for SSH connections.
   Secret Key	This is the secret key for authenticating the VM server where the agent is installed.

   Table. VM Server Additional Input Items

Add Build Pipeline

To add a build pipeline, follow these steps.

1. On the Main page, click the Project card. You will be taken to the Project Dashboard page.
2. In the left menu, click the Build/Deploy > Build Pipeline menu. You will be taken to the Build Pipeline page.
3. Build Pipeline page, click the Add Pipeline button at the top right. You will be taken to the Add Pipeline page.
4. Add Pipeline Enter or configure each field on the page.
5. Click the Next button.

   Item	Explanation
   Category	Select Development or Operations The actions that each role can perform differ depending on development or operations. Refer to Table. Role-specific permissions within the project (1) for role-specific permissions.
   Jenkins URL	Select Jenkins from the list to add a build pipeline.
   Build Agent	Select the agent (build environment) on which the build pipeline will run. Click the Info icon to view the list of tools provided by the agent.
   Build environment OS	Displays the OS information of the environment where the build agent runs.
   Folder type	Select the folder type. Existing folder: Add a pipeline under an already created folder in Jenkins. New folder: Create a new folder in Jenkins and add a pipeline under it.
   folder	Select a folder from the list or enter the name of a new folder to create.
   Pipeline name	Please enter the pipeline name.
   Parameter setting	Set the parameters to be used in the pipeline.
   Environment variable configuration	Set the environment variables to be used in the pipeline.
   Stage Settings	Configure the stage to be used in the pipeline.
   Configure email recipients for build results	Set the recipients who will receive the result email after the pipeline completes (success/failure).

   Table. Additional Build Pipeline Settings

Setting Parameters

Follow these steps to set the parameters used when running the pipeline.

1. Click the Parameter card.
2. Click the Add button to add a parameter.
3. Click the Apply button to complete the parameter settings.

Setting Environment Variables

Follow these steps to set environment variables for use in the pipeline.

1. Click the Environment Variable area. The Environment Variable Registration page opens on the right.
2. A list of pre-registered environment variables appears, and select the checkboxes for the environment variables you want to use.
3. Check the selected environment variable and click the Apply button to complete the environment variable configuration.

Configure email recipients for build results

To set the recipients who will receive the build results by email, follow these steps.

1. Click the Mail Recipient area. The Add Mail Recipient page opens on the right.
2. In the Search area, search for the recipient and add them.
3. Click the Apply button to complete the mail recipient settings.

Configure additional stage

Setting up the Checkout stage

To add a Checkout stage, follow these steps.

1. Click the New Stage area. The Stage Settings page opens on the right.
2. On the Stage Settings page, select Checkout as the Stage Type.
3. After entering the information, click the Apply button. (You can select the code repository you added from 코드 저장소 추가하기 (Option) on the URL.)

   Item	description
   URL	Select the code repository to perform the checkout.
   Branch name	Enter the name of the branch to checkout.

   표. Checkout 스테이지 입력 항목

Setting up the Build stage

To add a Build stage, follow these steps.

1. Click the Add icon to add a new stage.
2. Click the New Stage area. The Stage Settings page opens on the right.
3. On the Stage Settings page, select Build as the Stage Type.
4. After entering information on the Stage Settings page, click the Apply button.

   Item	Explanation
   language	Select the programming language used by the application.
   Build tool	Select the Build tool used for building the application. Provides default Shell commands based on the selected Build tool.
   Shell command	Enter the command to use for building the application. All commands available in the Shell can be used.

   Table. Build stage input items

Configuring Docker Build Stage

To add a Docker Build stage, follow these steps.

1. Click the Add icon to add a new stage.
2. Click the New Stage area. The Stage Settings page opens on the right.
3. Select Docker Build as the Stage Type.
4. After entering the information, click the Apply button. (You can select the image repository you added in Registry URL from Add Image Repository (Option).)

Deploy to VM Stage Setup

To add a Deploy to VM stage, follow these steps.

1. + Click the icon to add a new stage.
2. Click the New Stage area. The Stage Settings page opens on the right.
3. On the Stage Settings page, select Deploy to VM as the Stage Type.
4. On the Stage Settings page, after entering the information, click the Apply button.

Check the final pipeline script

1. Check the build pipeline script that will actually be generated. If needed, edit the script directly.
2. Click the Complete button to finish adding the pipeline.

Pipeline addition result

2.2.2.4 - Check Deployment Target Namespace Permissions (Before Project Creation)

The user should create a DevOps Console project following the steps below, verify that they have permission for the target cluster / namespace before building and deploying the source, and, if necessary, request the responsible person to add permissions to the cluster / namespace.

DevOps Console K8S Cluster Namespace Permission Check

To verify permissions for a namespace of the K8S cluster used in the DevOps Console, follow these steps.

1. Main page, click the Admin icon in the top right. Tenant Dashboard page will open.
2. In the left menu, click the Deployment Target > K8S Cluster menu. You will be taken to the K8S Cluster list page.
3. Click the K8S cluster. You will be taken to the Details page of the selected K8S cluster.
4. Click the Namespace tab. The Namespace List screen appears.
5. Clicking the namespace takes you to the Namespace Details page.

2.3 - Project

2.3.1 - Project Overview

Users can view not only the detailed information of the project but also related Helm release information, the tools they are using, and other relevant details.

Users with a project role of Master or higher can edit the project name through this menu, and the Owner can delete the project.

Project Overview Getting Started

To start using the project overview, follow these steps.

1. On the Main page, click the Project card. You will be taken to the Project Dashboard page.
2. From the left menu, click the Project Overview menu. The Project Overview screen appears.

Modify project name

To change the project name, follow these steps.

1. Project Overview On the screen, click the Edit Project Name button at the top right. The Edit Project Name popup window will open.
2. Edit Project Name In the popup window, edit the project name and click the Save button to complete the project name edit.

Delete Project

To delete a project, follow these steps.

1. Project Overview On the screen, click the Delete Project button in the upper right. The Delete Project popup window opens.
2. In the Project Deletion popup, click the Confirm button. You will be taken to the Project Deletion page.
3. On the Project Deletion page, enter and select the required information, then click the Delete button. The Project Deletion popup window opens.
4. Project Deletion Enter the project name in the popup window.
5. Click the Confirm button to complete the project deletion.

   Item	Explanation
   Check project name	Enter the name of the current project you want to delete.
   Delete Helm release Delete build pipeline Delete code repository	If you want to delete together with the project, select Select: When the project is deleted, the actual physical deletion command is executed. Deselect: It is only logically deleted in DevOps Console, and remains in each tool.

   Table. Project Deletion Input Items

Manage all projects

1. Click the Admin icon at the top right of the Main page. Navigate to the Tenant Dashboard page.
2. Click the Tenant > Project menu in the left menu. You will be taken to the Project page.

2.3.2 - Create Project

2.3.2.1 - Create Project (Helm Chart Deployment)

Users can create a project that deploys 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.

1. Click the Create Project button on the Main page. You will be taken to the Create Project page.

Enter basic information

Enter the basic information of the project. The project name and project ID must be unique and cannot be duplicated.

To enter the basic information, follow the steps below.

1. On the Project Creation page, select the App. Template Utilization option of the Project Configuration Method item.
2. For the deployment target field, select Kubernetes.
3. After entering additional content, click the Start button.

   Item	Explanation
   Project name	Please enter the project name.
   Project ID	Please enter the project ID.
   Project configuration method	Select a project configuration method Use App template: select a pre‑provided App template. Manual configuration: configure without an App template.
   deployment target	Select 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): Package the application as a Docker image and deploy it to a VM server. N/A: Choose this when you do not deploy the build output.
   K8S cluster	Select the target cluster for deployment DevOps Console Only clusters that the user has access rights to can be selected among the K8S clusters.
   namespace	Select the target namespace for deployment Only namespaces that the user has access rights to, among the clusters retrieved from the K8S cluster, can be selected.

   Table. Project creation basic information entry items

App. Select Template

The user can select an application template to configure the project.

If you create a project based on an application template that includes sample source code, you can view the application that will be deployed.

In contrast, using a template labeled Environment Only configures only the build/deployment environment without sample source code.

If you configure a project using an already set up source code repository, select the template marked Environment Only.

To start selecting an application template, follow these steps.

1. On the Application Template screen, enter the template name, select the application template card you want, and then click.
2. When the Next button is enabled, click the Next button.

   Item	Explanation
   Filter	You can easily find application templates using predefined filters.
   search	You can easily find application templates through search.

   Table. Project Creation Application Template Items

Configure code repository

Users can configure a repository for managing source code through the code repository setup step.

Create new repository and use existing repository activation conditions differ depending on the application template and tool.

To modify or delete stored credentials, refer to Manage Authentication Information.

To set up the code repository, follow these steps.

1. In the Code repository item, select the Code repository type.
2. Select Create new repository or Use existing repository, then enter the information.
3. Enter authentication information and click the Connection Test button.
4. When the Next button is enabled, click the Next button.

   Item	Explanation
   Repository type	Select the code repository to use Registered tool: The user can select and use the types of SCM Repository tools (Github, Gitlab, etc.) that are available. Unregistered tool: You can enter the domain of an unregistered tool to use it. The unregistered tool entry appears only when the source code is not included (Environment Only) App. Template.
   New/Existing usage	Please select New repository creation or whether to use an existing repository. Activation status varies depending on specific conditions. For details, refer to Table. Activation conditions for creating a new repository and using an existing repository.
   Repository information	Enter repository information When creating a new repository, the URL is formed from the project group name/project name.
   Authentication information	Enter authentication information If you do not have an account, Don’t have an account? click the link to open the Account Creation Information popup where you can create an account. After creating a new account, be sure to change your password via the Set Initial Password link.
   (Unregistered tool) Repository information	Enter repository information You can use a code repository that is not registered as a tool in DevOps Console. Click the URL Check button to undergo an additional verification process.

   Table. Project Creation Code Repository Settings

Configure Code Quality

Users can configure a repository for quality management.

To set code quality, follow these steps.

1. In the Code Quality item, select Repository Type.
2. Enter Basic Information and Authentication Information, then click the Connection Test button.
3. Next button is enabled, click the Next button.

   Item	Explanation
   Repository type	Select the repository to use The types of Code Quality tools available to the user are displayed.
   New / Existing / Unused status	Select repository creation method If you select Create new repository, you must enter the quality project name/quality project key. If you select Do not create, you can proceed directly to the next step.
   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 credentials You can create a new user or use existing authentication credentials.

   Table. Project Creation Code Quality Settings

Configure Image Repository

Users can configure a repository to store the built container images through the image repository configuration step.

To modify or delete stored credentials, refer to Manage Authentication Information.

To set up the image repository, follow these steps.

1. In the Image Repository item, select the Repository Type.
2. Create new repository / Use existing repository select, then enter the information.
3. Enter authentication information and click the Connection Test button.
4. When the Next button is enabled, click the Next button.

   Item	Explanation
   Repository type	Select the repository type to use The types of Image Registry tools available to the user are displayed.
   Repository information	Select the repository creation method. When creating a new repository, the URL is formed with the project group name/project name.
   Authentication information	Enter your credentials.

   Table. Project Creation Image Repository Settings

Configure the deployment target environment

Users can deploy by directly configuring via Helm charts.

Helm release name and Helm chart when selected, the Helm chart installation options and the default Values.yaml entries included in the chart are displayed.

Available Helm charts are associated with the App template. You can edit or delete them through Manage supported Helm charts.

To set the deployment target environment, follow these steps.

1. In the Deployment target field, select Configure directly via Helm chart.
2. Please enter the Helm release name.
3. Click the Search button to select the Helm chart to use.
4. After editing Values.yaml, click the Validation Check button.
5. When the Next button is enabled, click the Next button.

   Item	Explanation
   deployment target	Please select the deployment target.
   Helm release name	Enter the name of the Helm release to create. The name must be unique within the namespace of the target cluster.
   Helm chart	Select a Helm chart. When a Helm chart is selected, detailed information about the chosen chart is displayed below
   K8S information	Shows the information of the Kubernetes cluster required for configuring Value.yaml.
   Values. yaml	Edit the contents of Values.yaml. values.yaml file to be used when installing the Helm chart.

   Table. Project creation deployment target environment configuration items

Setting up the build pipeline

Users can configure pipelines that build and deploy applications.

You can view each stage of the pipeline to be configured and rename the build job.

To set up the build pipeline, follow these steps.

1. Build Pipeline screen branches based on IDP integration status.
   • For IDP-integrated Jenkins, click the User Check button to perform User Registration Confirmation.
   • For Jenkins not integrated with IDP, enter the authentication information and click the Connection Test button.
2. When the Next button is enabled, click the Next button.

   Item	Explanation
   Build/Deployment pipeline	Displays build/deployment pipeline information. The build/deployment pipeline is displayed based on the information registered in the App template’s Manage Pipeline Templates.
   Category	Select the development/operation distinction. The permissions for the pipeline vary according to the development/operation distinction. Refer to Table. Role-based permissions within the project (1) for role-based permissions.
   URL	Select Jenkins to configure the pipeline, then enter the job name. The Jenkins instances available to the user are displayed.
   Build Agent	Select the agent to be used for pipeline builds. For information about the agent, please refer to Managing agents (kubernetes), Managing agents (VM).
   Build environment OS	Displays the OS information of the environment in which the build agent runs.
   User information	IDP Integrated Jenkins Click the User Check button to verify user registration. If you are not registered as a Jenkins user, when the User Registration Guide popup appears, click the Go to Jenkins link to proceed with User Sign‑Up or Initial Jenkins Login. IDP Non‑Integrated Jenkins Enter the authentication information and click the Connection Test button.
   Set environment variables	Set the environment variables to be registered in the Jenkins pipeline.
   Image Tag Pattern	Select the tag assignment method for the container image.
   Deploy Strategy	Select the deployment method for the container image.
   Recipient of deployment results	Select the user who will receive the results after the build pipeline completes.

   Table. Project creation build pipeline configuration items

Configure Custom Settings

The user can specify and modify the path of the Dockerfile file used for the build.

Additionally, you can view the final script generated based on the information configured in 빌드 파이프라인 설정하기 and also edit it.

Dockerfile, follow these steps to configure the pipeline script.

1. After entering information on the Custom settings page, click the Connection Test button.
2. Click the Next button when the Next button is enabled.

   Item	Explanation
   Dockerfile configuration	Create New Dockerfile or Use Existing Dockerfile. Please select. «Use Existing Dockerfile is only selectable after choosing the Environment Only App template and, in 코드 저장소 설정하기, selecting Use Existing Repository.
   Dockerfile path	Specify the Dockerfile file path in the source code.
   Branch name	The branch name is automatically registered when you set it in Code Repository Configuration.
   Dockerfile	Check and modify the contents of the Dockerfile.
   pipeline script	Check and modify the pipeline script.

   Table. Project Creation Custom Settings Items

Complete project creation

The user can review the project and tool information to be created and start project creation.

To complete project creation, follow the steps below.

1. Summary Information After checking the information on the screen, click the Complete button.
2. Project Creation popup window opens and the project creation proceeds.
3. After the project creation is complete, click the Confirm button to go to the Project page.

2.3.2.2 - Create Project (Workload Deployment)

Users can create a project that deploys to a specific Kubernetes cluster using App.Template, Tool Management and workloads.

Getting Started with Project Creation

To begin creating a project, follow the steps below.

1. On the Main page, click the Create Project button. You will be taken to the Create Project page.

Enter basic information

Enter the basic information of the project. The project name and project ID must be unique and cannot be duplicated.

To enter the basic information, follow the steps below.

1. On the Project Creation page, select the App. Template Utilization option of the Project Configuration Method item.
2. For the deployment target field, select Kubernetes.
3. After entering additional content, click the Start button.

   Item	Explanation
   Project name	Please enter the project name.
   Project ID	Please enter the project ID.
   Project configuration method	Select a project configuration method Use App template: select a pre‑provided App template. Manual configuration: configure without an App template.
   deployment target	Select 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): Package the application as a Docker image and deploy it to a VM server. N/A: Choose this when you do not deploy the build output.
   K8S cluster	Select the target cluster for deployment DevOps Console Only clusters that the user has access rights to can be selected among the K8S clusters.
   namespace	Select the target namespace for deployment Only namespaces that the user has access rights to, among the clusters retrieved from the K8S cluster, can be selected.

   Table. Project creation basic information entry items

Select Application Template

The user can select an application template to configure the project.

If you create a project based on an application template that includes sample source code, you can view the application that will be deployed.

In contrast, using a template labeled Environment Only configures only the build/deployment environment without sample source code.

If you configure a project using an already set up source code repository, select the template marked Environment Only.

To start selecting an application template, follow these steps.

1. On the Application Template screen, enter the template name, select the application template card you want, and then click.
2. When the Next button is enabled, click the Next button.

   Item	Explanation
   Filter	You can easily find application templates using predefined filters.
   search	You can easily find application templates through search.

   Table. Project Creation Application Template Items

Configure code repository

Users can configure a repository for managing source code through the code repository setup step.

Create new repository and use existing repository activation conditions differ depending on the application template and tool.

To modify or delete stored credentials, refer to Manage Authentication Information.

To set up the code repository, follow these steps.

1. In the Code repository item, select the Code repository type.
2. Select Create new repository or Use existing repository, then enter the information.
3. Enter authentication information and click the Connection Test button.
4. When the Next button is enabled, click the Next button.

   Item	Explanation
   Repository type	Select the code repository to use Registered tool: The user can select and use the types of SCM Repository tools (Github, Gitlab, etc.) that are available. Unregistered tool: You can enter the domain of an unregistered tool to use it. The unregistered tool entry appears only when the source code is not included (Environment Only) App. Template.
   New/Existing usage	Please select New repository creation or whether to use an existing repository. Activation status varies depending on specific conditions. For details, refer to Table. Activation conditions for creating a new repository and using an existing repository.
   Repository information	Enter repository information When creating a new repository, the URL is formed from the project group name/project name.
   Authentication information	Enter authentication information If you do not have an account, Don’t have an account? click the link to open the Account Creation Information popup where you can create an account. After creating a new account, be sure to change your password via the Set Initial Password link.
   (Unregistered tool) Repository information	Enter repository information You can use a code repository that is not registered as a tool in DevOps Console. Click the URL Check button to undergo an additional verification process.

   Table. Project Creation Code Repository Settings

Configure Code Quality

Users can configure a repository for quality management.

To set code quality, follow these steps.

1. In the Code Quality item, select Repository Type.
2. Enter Basic Information and Authentication Information, then click the Connection Test button.
3. Next button is enabled, click the Next button.

   Item	Explanation
   Repository type	Select the repository to use The types of Code Quality tools available to the user are displayed.
   New / Existing / Unused status	Select repository creation method If you select Create new repository, you must enter the quality project name/quality project key. If you select Do not create, you can proceed directly to the next step.
   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 credentials You can create a new user or use existing authentication credentials.

   Table. Project Creation Code Quality Settings

Configure Image Repository

Users can configure a repository to store the built container images through the image repository configuration step.

To modify or delete stored credentials, refer to Manage Authentication Information.

To set up the image repository, follow these steps.

1. In the Image Repository item, select the Repository Type.
2. Create new repository / Use existing repository select, then enter the information.
3. Enter authentication information and click the Connection Test button.
4. When the Next button is enabled, click the Next button.

   Item	Explanation
   Repository type	Select the repository type to use The types of Image Registry tools available to the user are displayed.
   Repository information	Select the repository creation method. When creating a new repository, the URL is formed with the project group name/project name.
   Authentication information	Enter your credentials.

   Table. Project Creation Image Repository Settings

Configure the deployment target environment

The user can deploy by selecting Select deployment target workload.

To configure the deployment target environment, follow the steps below.

1. In the Deployment Target item, select Select Deployment Target Workload. The Deployment Target Workload area appears.
2. In the Deployment Target Workload area, select the workload and container to be deployed.
3. When the Next button is enabled, click the Next button.

   Item	Explanation
   deployment target	Select deployment target Configure directly via Helm chart Select workload for deployment target
   Query target	Select the item to view.
   Workload	Select workload Displays the workloads that exist in the selected Kubernetes cluster when starting project creation.
   target container	Select the target container to use for the selected workload.

   Table. Deployment Target Environment Configuration Items

Setting up the build pipeline

Users can configure pipelines that build and deploy applications.

You can view each stage of the pipeline to be configured and rename the build job.

To set up the build pipeline, follow these steps.

1. Build Pipeline screen branches based on IDP integration status.
   • For IDP-integrated Jenkins, click the User Check button to perform User Registration Confirmation.
   • For Jenkins not integrated with IDP, enter the authentication information and click the Connection Test button.
2. When the Next button is enabled, click the Next button.

   Item	Explanation
   Build/Deployment pipeline	Displays build/deployment pipeline information. The build/deployment pipeline is displayed based on the information registered in the App template’s Manage Pipeline Templates.
   Category	Select the development/operation distinction. The permissions for the pipeline vary according to the development/operation distinction. Refer to Table. Role-based permissions within the project (1) for role-based permissions.
   URL	Select Jenkins to configure the pipeline, then enter the job name. The Jenkins instances available to the user are displayed.
   Build Agent	Select the agent to be used for pipeline builds. For information about the agent, please refer to Managing agents (kubernetes), Managing agents (VM).
   Build environment OS	Displays the OS information of the environment in which the build agent runs.
   User information	IDP Integrated Jenkins Click the User Check button to verify user registration. If you are not registered as a Jenkins user, when the User Registration Guide popup appears, click the Go to Jenkins link to proceed with User Sign‑Up or Initial Jenkins Login. IDP Non‑Integrated Jenkins Enter the authentication information and click the Connection Test button.
   Set environment variables	Set the environment variables to be registered in the Jenkins pipeline.
   Image Tag Pattern	Select the tag assignment method for the container image.
   Deploy Strategy	Select the deployment method for the container image.
   Recipient of deployment results	Select the user who will receive the results after the build pipeline completes.

   Table. Project creation build pipeline configuration items

Configure Custom Settings

The user can specify and modify the path of the Dockerfile file used for the build.

Additionally, you can view the final script generated based on the information configured in 빌드 파이프라인 설정하기 and also edit it.

Dockerfile, follow these steps to configure the pipeline script.

1. After entering information on the Custom settings page, click the Connection Test button.
2. Click the Next button when the Next button is enabled.

   Item	Explanation
   Dockerfile configuration	Create New Dockerfile or Use Existing Dockerfile. Please select. «Use Existing Dockerfile is only selectable after choosing the Environment Only App template and, in 코드 저장소 설정하기, selecting Use Existing Repository.
   Dockerfile path	Specify the Dockerfile file path in the source code.
   Branch name	The branch name is automatically registered when you set it in Code Repository Configuration.
   Dockerfile	Check and modify the contents of the Dockerfile.
   pipeline script	Check and modify the pipeline script.

   Table. Project Creation Custom Settings Items

Complete project creation

The user can review the project and tool information to be created and start project creation.

To complete project creation, follow the steps below.

1. Summary Information After checking the information on the screen, click the Complete button.
2. Project Creation popup window opens and the project creation proceeds.
3. After the project creation is complete, click the Confirm button to go to the Project page.

2.3.2.3 - Create Project (ArgoCD Deployment)

Users can create a project that deploys using App.Template, Tool Management, and ArgoCD.

Getting Started with Project Creation

To start creating a project, follow the steps below.

1. On the Main page, click the Create Project button. You will be taken to the Create Project page.

Enter 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 the steps below.

1. Enter the project name and project ID.
2. For the Project Configuration Method item, select App. Template Utilization.
3. Please select deployment target as Kubernetes(ArgoCD).
4. Please select the ArgoCD App creation method.
   • Create a new App: When creating a project, create a new ArgoCD application in ArgoCD.
   • Use existing App: Create a project using the existing ArgoCD application.
5. After completing each input, click the Start button.

App. Select Template

The user can select an application template to configure the project.

If you create a project based on an application template that includes sample source code, you can view the application that will be deployed.

In contrast, using a template labeled Environment Only configures only the build/deployment environment without sample source code.

If you configure a project using an already set up source code repository, select the template marked Environment Only.

To start selecting an application template, follow these steps.

1. On the Application Template screen, enter the template name, select the application template card you want, and then click.
2. When the Next button is enabled, click the Next button.

   Item	Explanation
   Filter	You can easily find application templates using predefined filters.
   search	You can easily find application templates through search.

   Table. Project Creation Application Template Items

Configure code repository

Users can configure a repository for managing source code through the code repository setup step.

Create new repository and use existing repository activation conditions differ depending on the application template and tool.

To modify or delete stored credentials, refer to Manage Authentication Information.

To set up the code repository, follow these steps.

1. In the Code repository item, select the Code repository type.
2. Select Create new repository or Use existing repository, then enter the information.
3. Enter authentication information and click the Connection Test button.
4. When the Next button is enabled, click the Next button.

   Item	Explanation
   Repository type	Select the code repository to use Registered tool: The user can select and use the types of SCM Repository tools (Github, Gitlab, etc.) that are available. Unregistered tool: You can enter the domain of an unregistered tool to use it. The unregistered tool entry appears only when the source code is not included (Environment Only) App. Template.
   New/Existing usage	Please select New repository creation or whether to use an existing repository. Activation status varies depending on specific conditions. For details, refer to Table. Activation conditions for creating a new repository and using an existing repository.
   Repository information	Enter repository information When creating a new repository, the URL is formed from the project group name/project name.
   Authentication information	Enter authentication information If you do not have an account, Don’t have an account? click the link to open the Account Creation Information popup where you can create an account. After creating a new account, be sure to change your password via the Set Initial Password link.
   (Unregistered tool) Repository information	Enter repository information You can use a code repository that is not registered as a tool in DevOps Console. Click the URL Check button to undergo an additional verification process.

   Table. Project Creation Code Repository Settings

Configure Code Quality

Users can configure a repository for quality management.

To set code quality, follow these steps.

1. In the Code Quality item, select Repository Type.
2. Enter Basic Information and Authentication Information, then click the Connection Test button.
3. Next button is enabled, click the Next button.

   Item	Explanation
   Repository type	Select the repository to use The types of Code Quality tools available to the user are displayed.
   New / Existing / Unused status	Select repository creation method If you select Create new repository, you must enter the quality project name/quality project key. If you select Do not create, you can proceed directly to the next step.
   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 credentials You can create a new user or use existing authentication credentials.

   Table. Project Creation Code Quality Settings

Configure Image Repository

Users can configure a repository to store the built container images through the image repository configuration step.

To modify or delete stored credentials, refer to Manage Authentication Information.

To set up the image repository, follow these steps.

1. In the Image Repository item, select the Repository Type.
2. Create new repository / Use existing repository select, then enter the information.
3. Enter authentication information and click the Connection Test button.
4. When the Next button is enabled, click the Next button.

   Item	Explanation
   Repository type	Select the repository type to use The types of Image Registry tools available to the user are displayed.
   Repository information	Select the repository creation method. When creating a new repository, the URL is formed with the project group name/project name.
   Authentication information	Enter your credentials.

   Table. Project Creation Image Repository Settings

Configure the deployment target environment

Create new App

To create a new ArgoCD application and set the target deployment environment, follow the steps below.

1. On the Deployment target environment screen, enter the ArgoCD URL and click the Confirm button.
2. The authentication information entry screen appears.
3. Enter Authentication information and click the Connection Test button.
4. The input screen for the new ArgoCD application appears.
5. Enter ArgoCD application name and ArgoCD project name.
6. Select the Repository type.
7. Please select Helm chart.
8. Information about Helm chart and Helm chart Git repository is displayed.
9. After editing Values.yaml, click the Validation Check button.
10. After entering the Git repository information and authentication details, click the Connection Test button.
11. When the Next button is enabled, click the Next button.

    Item	Explanation
    URL input method	Select the URL input method. Select from the list: the ArgoCD tools registered as tools will appear. Enter manually
    ArgoCD URL	After entering the ArgoCD URL, click the Confirm button. The Authentication Information area appears.
    Authentication information	Enter Authentication Information and click the Connection Test button. The Application Basic Information area opens.
    Application name	Enter the name of the ArgoCD application to create in ArgoCD.
    Project name	Enter the project name of the ArgoCD application.
    Repository type	Select the repository type. Create a new repository with Helm chart: Use a Helm chart to create a Git repository for GitOps. Helm chart information area opens. Use existing Git repository
    Helm chart	Please select a Helm chart.
    Helm chart Git repository	Enter the information for the Git repository to be used by GitOps.

    Table. New App Creation Settings

Use existing App

To configure the target deployment environment using an existing ArgoCD application, follow these steps.

1. Target deployment environment screen, enter ArgoCD URL, then click the Confirm button.
2. The screen for entering the existing ArgoCD application name and credentials appears.
3. Enter the Existing Application Name and Authentication Information, then click the Connection Test button.
4. A URL Check popup window opens to distinguish the Git repository linked to the ArgoCD application..
5. URL Check After editing the Base URL in the popup window, click the Confirm button.
6. The Git repository information associated with the ArgoCD application is displayed.
7. Enter the authentication information for the Git repository, then click the Connection Test button.
8. Enter the yaml file name and key value to change in the Manifest Root path area.
9. When the Next button is enabled, click the Next button.

   Item	Explanation
   URL input method	Select URL input method Select from list: ArgoCD tools registered as tools appear. Enter manually
   ArgoCD URL	After entering the ArgoCD URL, click the Confirm button. The Existing application name and credentials section will appear.
   Application name / authentication information	Enter the Existing application name and credentials, then click the Connection Test button. The Git repository and ArgoCD information area appears.
   URL Check	Separate the Base URL and Path in the full URL.
   Git repository credentials	Enter the credentials for the Git repository used by the selected existing application.
   Image Repo Key	Enter the path to the Yaml file that records the image repository information and the Key value. If the key values for repository and tag are the same, enter the same value.
   Image Tag Key	Enter the path to the Yaml file containing the image tag information and the Key value. If the repository and tag have the same key, enter the same value.
   Image Secret Key	Enter the path to the Yaml file containing the image secret information and the Key value.
   Deploy Strategy Key	Enter the path to the Yaml file containing deployment strategy information and the Key value (optional).

   Table. Existing App usage configuration items

Setting up the build pipeline

Users can configure pipelines that build and deploy applications.

You can view each stage of the pipeline to be configured and rename the build job.

To set up the build pipeline, follow these steps.

1. Build Pipeline screen branches based on IDP integration status.
   • For IDP-integrated Jenkins, click the User Check button to perform User Registration Confirmation.
   • For Jenkins not integrated with IDP, enter the authentication information and click the Connection Test button.
2. When the Next button is enabled, click the Next button.

   Item	Explanation
   Build/Deployment pipeline	Displays build/deployment pipeline information. The build/deployment pipeline is displayed based on the information registered in the App template’s Manage Pipeline Templates.
   Category	Select the development/operation distinction. The permissions for the pipeline vary according to the development/operation distinction. Refer to Table. Role-based permissions within the project (1) for role-based permissions.
   URL	Select Jenkins to configure the pipeline, then enter the job name. The Jenkins instances available to the user are displayed.
   Build Agent	Select the agent to be used for pipeline builds. For information about the agent, please refer to Managing agents (kubernetes), Managing agents (VM).
   Build environment OS	Displays the OS information of the environment in which the build agent runs.
   User information	IDP Integrated Jenkins Click the User Check button to verify user registration. If you are not registered as a Jenkins user, when the User Registration Guide popup appears, click the Go to Jenkins link to proceed with User Sign‑Up or Initial Jenkins Login. IDP Non‑Integrated Jenkins Enter the authentication information and click the Connection Test button.
   Set environment variables	Set the environment variables to be registered in the Jenkins pipeline.
   Image Tag Pattern	Select the tag assignment method for the container image.
   Deploy Strategy	Select the deployment method for the container image.
   Recipient of deployment results	Select the user who will receive the results after the build pipeline completes.

   Table. Project creation build pipeline configuration items

Configure Custom Settings

The user can specify and modify the path of the Dockerfile file used for the build.

Additionally, you can view the final script generated based on the information configured in 빌드 파이프라인 설정하기 and also edit it.

Dockerfile, follow these steps to configure the pipeline script.

1. After entering information on the Custom settings page, click the Connection Test button.
2. Click the Next button when the Next button is enabled.

   Item	Explanation
   Dockerfile configuration	Create New Dockerfile or Use Existing Dockerfile. Please select. «Use Existing Dockerfile is only selectable after choosing the Environment Only App template and, in 코드 저장소 설정하기, selecting Use Existing Repository.
   Dockerfile path	Specify the Dockerfile file path in the source code.
   Branch name	The branch name is automatically registered when you set it in Code Repository Configuration.
   Dockerfile	Check and modify the contents of the Dockerfile.
   pipeline script	Check and modify the pipeline script.

   Table. Project Creation Custom Settings Items

Complete project creation

The user can review the project and tool information to be created and start project creation.

To complete project creation, follow the steps below.

1. Summary Information After checking the information on the screen, click the Complete button.
2. Project Creation popup window opens and the project creation proceeds.
3. After the project creation is complete, click the Confirm button to go to the Project page.

2.3.2.4 - Create Project (VM Deployment)

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 information about the target VM server. For detailed information on VM server registration, refer to Getting Started with VM Server Group.

Getting Started with Project Creation

To start creating a project, follow these steps.

1. On the Main page, click the Create Project button. It navigates to the Create Project page.

Enter basic information

1. On the Create Project page, enter the project name and project ID.
2. For the Project Configuration Method item, select App. Template Utilization.
3. Select VM(Artifact) or VM(Docker) for the Deployment Target field.
   • VM(Artifact) creates a war/jar file and transfers it to the deployment target server.
   • VM(Docker) runs the docker command after the build and image creation.
4. Please select the deployment method.
   • Differences by deployment method: Table. SSH method vs Agent method
5. After each input is completed, click the Start button.

App. Select Template

The user can select an application template to configure the project.

If you create a project based on an application template that includes sample source code, you can view the application that will be deployed.

In contrast, using a template labeled Environment Only configures only the build/deployment environment without sample source code.

If you configure a project using an already set up source code repository, select the template marked Environment Only.

To start selecting an application template, follow these steps.

1. On the Application Template screen, enter the template name, select the application template card you want, and then click.
2. When the Next button is enabled, click the Next button.

   Item	Explanation
   Filter	You can easily find application templates using predefined filters.
   search	You can easily find application templates through search.

   Table. Project Creation Application Template Items

Configure code repository

Users can configure a repository for managing source code through the code repository setup step.

Create new repository and use existing repository activation conditions differ depending on the application template and tool.

To modify or delete stored credentials, refer to Manage Authentication Information.

To set up the code repository, follow these steps.

1. In the Code repository item, select the Code repository type.
2. Select Create new repository or Use existing repository, then enter the information.
3. Enter authentication information and click the Connection Test button.
4. When the Next button is enabled, click the Next button.

   Item	Explanation
   Repository type	Select the code repository to use Registered tool: The user can select and use the types of SCM Repository tools (Github, Gitlab, etc.) that are available. Unregistered tool: You can enter the domain of an unregistered tool to use it. The unregistered tool entry appears only when the source code is not included (Environment Only) App. Template.
   New/Existing usage	Please select New repository creation or whether to use an existing repository. Activation status varies depending on specific conditions. For details, refer to Table. Activation conditions for creating a new repository and using an existing repository.
   Repository information	Enter repository information When creating a new repository, the URL is formed from the project group name/project name.
   Authentication information	Enter authentication information If you do not have an account, Don’t have an account? click the link to open the Account Creation Information popup where you can create an account. After creating a new account, be sure to change your password via the Set Initial Password link.
   (Unregistered tool) Repository information	Enter repository information You can use a code repository that is not registered as a tool in DevOps Console. Click the URL Check button to undergo an additional verification process.

   Table. Project Creation Code Repository Settings

Configure Code Quality

Users can configure a repository for quality management.

To set code quality, follow these steps.

1. In the Code Quality item, select Repository Type.
2. Enter Basic Information and Authentication Information, then click the Connection Test button.
3. Next button is enabled, click the Next button.

   Item	Explanation
   Repository type	Select the repository to use The types of Code Quality tools available to the user are displayed.
   New / Existing / Unused status	Select repository creation method If you select Create new repository, you must enter the quality project name/quality project key. If you select Do not create, you can proceed directly to the next step.
   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 credentials You can create a new user or use existing authentication credentials.

   Table. Project Creation Code Quality Settings

Configure Artifact Repository

Users can configure a repository for artifacts.

If you select Uncreated, you can proceed directly to the next step.

To configure the artifact repository, follow these steps.

1. On the Artifact Repository screen, select the repository type.
2. Enter the basic information and authentication information, then click the Connection Test button.
3. When the Next button is enabled, click the Next button.

   Item	Explanation
   Repository type	Select the repository type to use The types of Artifact Repository tools available to the user are displayed.
   New / Existing / Unused status	Select the repository creation method If you select Uncreated, you can proceed directly to the next step.
   Base URL / Endpoint URL	Select a Nexus URL or an Object Storage URL.
   Storage type / bucket name	In the case of Nexus, it is automatically registered as raw(hosted). In the case of Object Storage, the bucket name entered during tool registration is automatically registered.
   Repository name / Folder name	Enter the repository name to use in Nexus. Enter the folder name to use in Object Storage.
   Authentication information	Enter authentication information You can create a new user or use existing authentication information.

   Table. Artifact Repository Configuration Input Items

Configure the deployment target environment

To set the deployment target environment, follow these steps.

1. Deployment Target Environment on the screen, after entering the required information, click the Next button.

   Item	Explanation
   Deployment configuration	Choose whether to write a deployment script manually When selecting to write a deployment script manually, write the content in the custom step.
   Deployment method	The selected deployment method is displayed. Table. SSH method vs Agent method
   Artifact repository	The address of the repository to use when the agent mode is selected is displayed. Deployment mode is enabled when it is Agent.
   Manual deployment	Select the default value for manual deployment Select the default setting for parameters related to manual deployment when running the pipeline.
   Deployment order	If there are multiple target servers, choose whether to deploy in parallel or sequentially.
   Deployment target settings	Set the deployment target server. When you click Settings, the Deploy Target VM Settings popup opens.
   Automatic recovery setting	Select whether to enable automatic rollback If the deployment fails, it will be rolled back to the most recent successful deployment. Deployment method is enabled when it is Agent.
   Command before file deployment	Write the commands that need to be executed before file deployment.
   File to send	Source: Enter the file path after the build pipeline execution path (Jenkins workspace). Target: Enter the path where the file will be deployed on the VM server. Add button can be used to add files.
   Command after file distribution	Write the commands that must be executed after file deployment.

   Table. Deployment Target Environment Configuration Items

Setting up the build pipeline

Users can configure pipelines that build and deploy applications.

You can review each stage of the pipeline to be configured and rename the build job.

To set up the build pipeline, follow these steps.

1. In the build pipeline configuration step, enter the authentication information and click the Connection Test button.
2. Next button is enabled, click the Next button.

   Item	Explanation
   Build/Deployment pipeline	Displays build/deployment pipeline information. The build/deployment pipeline is displayed based on the information registered in the App. template’s Manage Pipeline Templates
   Category	Select Development/Operation mode The permissions for the pipeline vary depending on the Development/Operation distinction. Refer to Table. Permissions by role within the project (1) for role-specific permissions.
   URL	Select Jenkins to configure the pipeline, then enter the Job name Jenkins available to the user appears.
   Build Agent	Select the agent to be used for pipeline builds For information about agents, refer to Managing agents (kubernetes), Managing agents (VM).
   Build environment OS	Displays the OS information of the environment in which the build agent runs.
   Authentication information	Enter the credentials for Jenkins.
   Set environment variables	Jenkins Set the environment variables to be registered in the pipeline.
   Deployment result recipient	Select the user who will receive the results after the build pipeline completes.

   Table. Build pipeline configuration input items

Configure Custom Settings

In the deployment target server and deployment settings step, if you select the deployment configuration item write deployment script directly, complete the deployment configuration by modifying the pipeline contents at this stage.

To customize the settings, follow these steps.

1. After reviewing and editing the content in the Custom step, click the Next button.

Complete project creation

The user can review the project and tool information to be created and start project creation.

To complete project creation, follow the steps below.

1. Summary Information After checking the information on the screen, click the Complete button.
2. Project Creation popup window opens and the project creation proceeds.
3. After the project creation is complete, click the Confirm button to go to the Project page.

2.3.2.5 - Create Project (Empty)

The user can create an Empty (Empty) project without any configuration.

To create an empty project and configure build/deployment, the user must manually perform tasks such as Add code repository, Add image repository, Install Helm, Add build pipeline.

Getting Started with Project Creation

To start creating an empty project, follow these steps.

1. On the Main page, click the Create Project button. You will be taken to the Create Project page.

Enter basic information

Enter the basic information for the project. The project name and project ID must be unique and cannot be duplicated.

To enter the basic information, follow these steps.

1. On the Project Creation page, select Direct Configuration under the Project Configuration Method item.
2. Enter Project Name and Project ID, then click the Start button. The Summary Information screen appears.

Complete project creation

The user can review the project and tool information to be created and start project creation.

To complete project creation, follow the steps below.

1. Summary Information After checking the information on the screen, click the Complete button.
2. Project Creation popup window opens and the project creation proceeds.
3. After the project creation is complete, click the Confirm button to go to the Project page.

2.3.3 - Start Project

The user can create a project via Create a project.

On the project page, users can utilize various menus for project management.

Getting Started

To start the project, follow these steps.

1. On the Main page, click the Project card. You will be taken to the Project Dashboard page.

Project menu

Dashboard

Dashboard (Project Dashboard)

This is a dashboard menu that lets you view information about the individual items that make up the project at a glance.

Build/Deployment

Build pipeline(Build/Deploy - Build Pipeline)

This menu allows you to view the Jenkins pipeline and perform and modify build/deployment tasks.

Kubernetes deployment (Build/Deploy - Kubernetes Deployment)

This menu lets you view the list of deployed Helm releases and their deployment status.

VM deployment (Build/Deploy - VM Deployment)

This menu allows you to view the list of deployed VMs and their deployment status.

Helm install (Helm install)

This is the menu where you can view Helm charts.

Ingress/Service management (Ingress/Service management)

A menu where you can view and add Ingress/Service.

Kubernetes Secret management (Kubernetes Secret management)

This menu allows you to view and add Kubernetes Secrets.

Environment Variable Management (환경변수 관리)

This is a menu that allows you to view and add environment variables.

storage

Code repository (repository)

This is a menu that allows you to view and add code repositories for a project.

Artifact Repository (Artifact Repository)

This menu lets you view and add the project’s image repository.

Image Repository (Image Repository)

This menu allows you to view and add the project’s image repository.

Chart repository (Chart repository)

This menu lets you view and add a project’s chart repositories.

Helm chart (헬름차트)

A menu for viewing and adding project Helm charts.

Quality

Code Quality (Code Quality)

Project code quality. This is a menu that allows you to view and add projects.

Project Overview

Project Overview (프로젝트 개요)

This menu allows you to view not only the project’s detailed information but also related Helm release information and details about the tools you are using.

member

Member (Project Member)

This is a menu for managing project users.

2.3.4 - Project Dashboard

You can view the information of individual items that make up the project at a glance on the dashboard.

Getting Started with Project Dashboard

To start using the dashboard, follow these steps.

1. Click the Project card on the Main page. You will be taken to the Project Dashboard page.
2. Click the Dashboard menu in the left menu.

   Item	Explanation
   Project information	Displays the basic project information.
   pipeline	Displays the status of pipelines added to the build pipeline. Click the numeric link to view the status of other pipelines.
   Helm release status	You can check the status of the Helm release added to the Kubernetes deployment.
   Blue/Green deployment status	You can check the status of blue/green deployments.
   Canary status	You can check the canary status.
   ArgoCD application status	You can check the status of the ArgoCD application added to the Kubernetes deployment.
   Kubernetes deployment history	Displays the Kubernetes deployment history in reverse chronological order.
   VM deployment history	Displays the VM deployment history in reverse chronological order.
   code quality	Displays code quality tool analysis information by integrating with the code quality tool.
   Code history	Displays the history of the added code repository. For the following items, you can select from the list to display in the code history. Git configuration Git Branch
   Scale and Usage Status	Displays the project’s users, tools, and build/deployment status.
   Monthly pipeline execution trend	Shows the monthly pipeline execution count, average execution interval, and execution time for the project.
   Inactive pipeline	Shows a list of pipelines that have not been run and have no successful history, according to the reference date.
   Required stage	Shows which stage tasks were performed in the pipeline, based on the code repository.
   Recent event history	You can view the recent event history that occurred in the project.

   Table. Project Dashboard Display Items

2.3.5 - Project Members

It includes features to grant other users access to the project, modify the permissions of users who already have access, or delete permissions so they can no longer access the project.

Getting Started with Project Members

To start using project members, follow these steps.

1. On the Main page, click the Project card. You will be taken to the Project Dashboard page.
2. Click the Member menu in the left menu. The Member screen appears.

Add Project Member

To add members to a project, follow these steps.

1. Click the Add button in the Member list. Member Add popup opens.
2. After completing the settings in the Add Member popup, click the Confirm button to finish adding a project member.

   Item	Explanation
   User tab	After searching for the email, click the Add button to add as a member.
   Project tab	Select to add all members from another project to the current project’s members.
   Add member	Click the user you want to add as a project member to add them.
   Permission Settings	Set the role to assign to members. Owner Master Developer Viewer
   Delete member	Click the X icon to delete from the project members.

   Table. Project Member Add Screen Items

Change Project Member Role

To change a project member’s role, follow these steps.

1. Identify the user whose role you want to change in the Member list.
2. Select the user’s project role from the list. It is saved immediately upon selection, and the user’s project role will be updated.

Delete project member

To remove a member from a project, follow these steps.

1. In the Member list, select the checkbox of the user you wish to delete.
2. Click the Delete button above the Member list to remove the selected user from the project members.

2.4 - Build/Deploy

2.4.1 - Build Pipeline

Users can group consecutive tasks into a single pipeline. The pipeline configured here is created as a Jenkins pipeline.

Starting the Build Pipeline

To start using the build pipeline, follow these steps.

1. Click the Project card on the Main page. You will be taken to the Project Dashboard page.
2. In the left menu, click the Build/Deploy > Build Pipeline menu. You will be taken to the Build Pipeline page.

Add Build Pipeline

To add a build pipeline, follow these steps.

1. On the Main page, click the Project card. You will be taken to the Project Dashboard page.
2. In the left menu, click the Build/Deploy > Build Pipeline menu. You will be taken to the Build Pipeline page.
3. Build Pipeline page, click the Add Pipeline button at the top right. You will be taken to the Add Pipeline page.
4. Add Pipeline Enter or configure each field on the page.
5. Click the Next button.

   Item	Explanation
   Category	Select Development or Operations The actions that each role can perform differ depending on development or operations. Refer to Table. Role-specific permissions within the project (1) for role-specific permissions.
   Jenkins URL	Select Jenkins from the list to add a build pipeline.
   Build Agent	Select the agent (build environment) on which the build pipeline will run. Click the Info icon to view the list of tools provided by the agent.
   Build environment OS	Displays the OS information of the environment where the build agent runs.
   Folder type	Select the folder type. Existing folder: Add a pipeline under an already created folder in Jenkins. New folder: Create a new folder in Jenkins and add a pipeline under it.
   folder	Select a folder from the list or enter the name of a new folder to create.
   Pipeline name	Please enter the pipeline name.
   Parameter setting	Set the parameters to be used in the pipeline.
   Environment variable configuration	Set the environment variables to be used in the pipeline.
   Stage Settings	Configure the stage to be used in the pipeline.
   Configure email recipients for build results	Set the recipients who will receive the result email after the pipeline completes (success/failure).

   Table. Additional Build Pipeline Settings

Setting Parameters

Follow these steps to set the parameters used when running the pipeline.

1. Click the Parameter card.
2. Click the Add button to add a parameter.
3. Click the Apply button to complete the parameter settings.

Setting Environment Variables

Follow these steps to set environment variables for use in the pipeline.

1. Click the Environment Variable area. The Environment Variable Registration page opens on the right.
2. A list of pre-registered environment variables appears, and select the checkboxes for the environment variables you want to use.
3. Check the selected environment variable and click the Apply button to complete the environment variable configuration.

Setting up the stage

To set up the stages to be used in the pipeline, follow these steps.

1. Click the New Stage card. The Stage area appears on the right.
2. In the Stage area, select the tool and Stage type.
3. Enter the required information according to the stage type and click the Apply button to complete the stage configuration.

Configure email recipients for build results

To set the recipients who will receive the build results by email, follow these steps.

1. Click the Mail Recipient area. The Add Mail Recipient page opens on the right.
2. In the Search area, search for the recipient and add them.
3. Click the Apply button to complete the mail recipient settings.

Check the final pipeline script

1. Check the build pipeline script that will actually be generated. If needed, edit the script directly.
2. Click the Complete button to finish adding the pipeline.

Pipeline addition result

1. The added result appears on the Build Pipeline page.

Managing Build Pipelines

Build pipeline list

Build Pipeline Credentials

When performing build pipeline actions (run, stop, edit, delete, etc.), user credentials are required, so you may request them from the user as needed.

When integrating IDP with Jenkins

If you are not registered as a Jenkins user, when the User Registration Guide popup appears, click the Go to Jenkins link to sign up or perform your first Jenkins login.

For Jenkins without IDP integration

Jenkins credentials are not stored; when the Add Account popup appears, select Use Existing User or Create New User in Account Type to add credentials.

Run Build Pipeline

To run the build pipeline, follow these steps.

1. On the Build pipeline page, click the Run button of the build pipeline you want to execute.
2. If there are parameters, the Pipeline Execution Parameter Input popup window opens.
3. After entering the required fields, click the Confirm button.

View build pipeline execution logs

Follow these steps to view the build pipeline execution logs.

1. On the Build Pipeline page, click the Log button of the build pipeline you want to run.
2. pipeline log A popup window opens, allowing you to view the execution log.

Build pipeline build history view

To view the complete build history of the build pipeline, follow these steps.

1. On the Build pipeline page, click the More icon of the build pipeline you want to view.
2. Click the Build History menu. The Build History page opens.

   Item	Explanation
   Config Diff	Config Diff The popup window opens.
   log	Pipeline Log The popup window opens.
   Additional menu	Navigate to the Build Details page.
   View pipeline stage	Click the Expand icon to expand the stage view.

   Table. Build Pipeline List View Feature

Compare configuration information

You can compare the configuration information with previous build history using the Config Diff button.

Log View

Through the Log button, you can view the logs of the build history.

Build Details

You can view detailed build information via the More icon.

Modify Build Pipeline

To modify the build pipeline, follow these steps.

1. On the Build pipeline page, click the More icon of the build pipeline you want to edit.
2. Click the Edit Pipeline button. You will be taken to the Edit Pipeline page.

Edit the script directly

To edit the pipeline script directly, follow these steps.

1. In the script editor window of the Pipeline Edit page, directly enter a script that conforms to the syntax supported by Jenkins.
2. After completing the input, click the Save button to finish editing the pipeline.

Modify using the Script Generator feature

Follow these steps to modify the pipeline script using the Script Generator feature.

1. On the Pipeline Edit page, change Script Generator to ON.
2. Select the build agent and script type.
3. After completing Stage Setup, click the Create Script button to generate the script.
4. Refer to the generated script to modify the pipeline, and click the Save button to complete the pipeline modification.

   Item	Explanation
   Script Generator	Turn the Script Generator feature ON/OFF.
   Script Basic Information	Select the basic information for script generation.
   Existing script	This is an existing script.
   New script	This is a new script generated by the Script Generator.
   Script modification	Refer to the newly created script and directly edit the existing script on the left.
   Update Jenkins Credential	If the newly created script contains new credentials, click the Jenkins Credential Update button. This updates (saves) the credentials in Jenkins.
   K8S Secret update	Deploy to K8S stage: when changing the K8S Secret, click the K8S Secret Update button. Update (save) it for use during Secret creation and deployment.

   Table. Script Generator feature

Clone Build Pipeline

To duplicate the build pipeline, follow these steps.

1. Click the More icon of the build pipeline you want to clone.
2. Click the Clone Pipeline menu. The Clone Pipeline popup window opens.
3. After completing the information entry, click the Save button to finish replicating the pipeline.

   Item	Explanation
   Pipeline replication information	Enter the information for the pipeline to be cloned.
   Pipeline modification	Modify the pipeline to be cloned. Note: Modify the build pipeline

   Table. Build Pipeline Replication Feature

Delete Build Pipeline

To delete a build pipeline, follow these steps.

1. On the Build pipeline page, click the More icon of the build pipeline you want to delete.
2. Click the Delete Pipeline menu. The Delete Pipeline popup window opens.
3. Delete Pipeline In the popup window, click the Confirm button to complete the pipeline deletion.

2.4.1.1 - Stage

The user can view the description of stage types and each stage-specific item.

You can configure stages in Add Build Pipeline or Edit Build Pipeline.

Common Items

Stage Settings page is organized as follows.

Checkout

This stage executes the checkout command on the Git repository registered in the code repository.

Select Checkout as the stage type.

Build

This is the stage that executes the command to build the application.

Select Build as the stage type.

Docker Build

This stage performs the Docker image build.

Select Docker Build as the stage type.

example script

The build pipeline script generated as a result of the example is as follows.

Deploy to K8S

This is the stage that performs a Kubernetes deployment.

Select Deploy to K8S as the stage type.

Deploy to VM

This is the stage that performs VM deployment.

Select Deploy to VM as the stage type.

Trigger Build

This is a stage that runs the pipeline remotely.

Select Trigger Build as the stage type.

Check Remote Execution Information

Remote execution information (parent/child pipelines) through the Trigger Build stage can be viewed on the Build Details screen.

Other stages

2.4.1.2 - Multibranch Pipeline