Tools & Templates

• 1: Tool Management
• 2: App Template
• 3: Register User-installed Jenkins Tool

1 - Tool Management

Tools refer to applications that interact with the DevOps Console to support CI/CD functionality.

Please refer to Tool Classification for the list of tools supported by DevOps Console.

Getting Started with Tool Management

To begin tool management, follow the steps below.

1. Click the Management 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 Tools & Templates > Tools menu. You will be taken to the Tools page.

Tool type

Each tool’s applicable domain varies according to its type.

Tool classification

The list of tools currently supported by the DevOps Console is as follows.

Admin

Indicates the selected tenant or project group when adding a tool with the tenant/project group type.
Distinguish the types of management affiliation using the following icons.

• The management belongs to the tenant.
• The management affiliation is the project group.

Add tool

To add a tool, follow these steps.

1. On the Tool page, click the Add button. The Add Tool popup appears.

Select tool support type

1. Add Tool Select the tool’s supported type in the popup window.
2. Complete the selection and click the Next button. The Basic Information input screen appears.

   Item	Explanation
   type	Select the tool’s supported type Refer to 툴 유형 for descriptions by type.
   Tenant/Project Group	Select which tenant/project group to map to.

   Table. Supported type selection items when adding a tool

Enter basic information

1. Add Tool In the Basic Information input screen of the popup, select the tool category and the tool. The input screen changes based on the selected tool.
   • Refer to Tool Classification for explanations by tool category.
2. After entering the required information, click the Connection Test button.
3. Click the Next button.

SCM Repository

CICD Pipeline

Image Registry

Code Quality

Artifact Repository

Helm Chart Repository

Project Management Software

Enter additional information

1. Tool addition In the popup window’s Basic Information input screen, when you click the Next button, the Additional Information input screen appears.
2. Select each item and click the Complete button.
3. In the confirmation popup, click the Confirm button to complete adding the tool.

   Item	description
   Use status	Select whether to use the tool in this tenant/project group.
   Whether new creation is possible	Select whether to allow creating a new repository in the given tenant/project group. It is displayed only when the tool category is SCM Repository.

   Table. Additional Information Input Items

Tool Details

To begin managing the tool’s detailed information, follow these steps.

1. On the Tool page, click the tool for which you want to manage detailed information. You will be taken to the Tool Details page.

Manage tool basic information

To check the tool’s basic information, follow these steps.

1. On the Tool Details page, click the Basic Information tab.

To modify the tool’s basic information, follow these steps.

1. On the Tool Details page, click the Basic Information tab.
2. Click the Edit button.
3. After editing the required information, click the Save button.

Managing Global Tools

Jenkins web interface’s Jenkins Management > Global Tool Configuration menu can be operated from the DevOps Console.
Only one-way registration to Jenkins is supported from the DevOps Console. (In other words, changes made by the user in the DevOps Console will overwrite the information in Jenkins.)
Users can manage the list of tools available in Jenkins, and tools registered in Global Tools are used in Tools when configuring a stage.

To manage the global tool, follow the steps below.

1. On the Tool Details page, click the Global Tool tab.

Add global tool

To add a global tool, follow these steps.

1. In the Global Tool tab, click the Edit icon of the item you want to add. The Global Tool Management popup opens.
   • Essential tool is automatically configured in the DevOps Console.
   • essential tool cannot be deleted, and only the home path can be modified.
2. Click the Add button. A new row will be added at the bottom of the list.
3. Enter the information in the newly added row and click the Save button.
4. Click the Confirm button in the confirmation popup to complete.

   Item	description
   Tool types	The tool type is set automatically.
   Name	Please enter the tool name.
   Home path	Enter the path where the tool is installed.

   Table. Global Tool Additional Input Items

Modify Global Tool

To modify the global tool, follow these steps.

1. Click the Edit icon of the item you want to add in the Global Tool tab. The Global Tool Management popup opens.
2. After editing the content, click the Save button.
3. In the confirmation popup, click the Confirm button to complete.

Delete Global Tool

To delete the global tool, follow these steps.

1. Click the Edit icon of the item you want to add in the Global Tool tab. The Global Tool Management popup window opens.
2. After deleting the list, click the Save button.
3. In the confirmation popup, click the Confirm button to complete.

Managing agents (kubernetes)

Users can manage the agents (slave) used for builds in Jenkins.

Jenkins web screen’s 1) Jenkins Management > System Configuration > Cloud > Pod Templates or 2) Jenkins Management > Node Management > Configure Clouds > Pod Templates menu is a feature that can be operated from the DevOps Console.

DevOps Console only supports one-way registration to Jenkins. (In other words, changes made by the user in DevOps Console will overwrite the information in Jenkins.)

To manage the agent (Kubernetes), follow the steps below.

1. On the Tool Details page, click the Agent (Kubernetes) tab.
2. Click the information icon in the Pod Template Management list. The Pod Template Usage Guide popup opens.

Adding Container Resource Types

To add a container resource type, follow these steps.

1. On the Tool Details page, click the Agent (Kubernetes) tab.
2. Click the Edit icon of Container Resource Type Management. The Container Resource Type Management popup window opens.
3. Click the Add button, enter the content, and then click the Save button.
4. In the confirmation popup, click the Confirm button to complete.

   Item	description
   Whether to use	Set the usage. To change the usage, there must be no build pipeline configured using the Jenkins tool.
   Resource Type	Please enter the resource name.
   CPU/Memory (Request)	When configuring the Kubernetes Pod Agent, enter the requested resource values to be used.
   CPU/Memory (Limit)	Enter the limit values for the resources to be used when configuring the Kubernetes Pod Agent.

   Table. Container Resource Type Additional Input Items

Modify container resource type

To modify the container resource type, follow these steps.

1. On the Tool Details page, click the Agent (Kubernetes) tab.
2. Click the Edit icon of Container Resource Type Management. The Container Resource Type Management popup opens.
3. After editing the content, click the Save button.
4. In the confirmation popup, click the Confirm button to complete.

Delete Container Resource Type

To delete a container resource type, follow these steps.

1. On the Tool Details page, click the Agent (Kubernetes) tab.
2. Click the Edit icon of Container Resource Type Management. The Container Resource Type Management popup opens.
3. After deleting the content, click the Save button.
4. In the confirmation popup, click the Confirm button to complete.

Add Pod Template

To add a Pod Template, follow these steps.

1. On the Tool Details page, click the Agent (Kubernetes) tab.
2. Pod Template Management Click the Add button in the list. The Add Agent (Kubernetes) screen appears.
3. After entering the content, click the Save button.
4. In the confirmation popup, click the Confirm button to complete.

   Item	description
   Target Kubernetes	Select the target Kubernetes to which the Pod Template will be added Displays the list of Kubernetes clusters registered in Jenkins.
   Agent name	Enter the name of the Pod Template.
   Label	Enter the Label value to invoke the agent in the Jenkins Pipeline Script.
   Inherited Pod Template	Select the Pod Template that inherits configuration values (environment variables, Volume…) Shows the list of Pod Templates registered in the actual Jenkins.
   container	Enter the name, Docker image, working directory, command, and argument values that map to the Container Template field in Jenkins. Required container information cannot be deleted, and its name cannot be changed.
   Tool path	Information that maps to the Tool Locations field in Jenkins, enter the name/home path Only tools that have been added to the global tool list can be selected.
   Support stage	Select the supported stage configuration This information is used for configuring the build pipeline template in the DevOps Console. Required stage information cannot be deselected.

   Table. Input items for adding a Pod Template

Pod Template Details

To view the detailed information of a Pod Template, follow these steps.

1. On the Tool Details page, click the Agent (Kubernetes) tab.
2. Pod Template Management Click the Details button of the agent you want to view from the list. The Agent (Kubernetes) Details screen appears.

Modify Pod Template

To modify the Pod Template, follow these steps.

1. On the Tool Details page, click the Agent (Kubernetes) tab.
2. Pod Template Management Click the View Details button of the agent you want to view in the list. The Agent (Kubernetes) Details screen appears.
3. Click the Edit button.
4. After editing the content, click the Save button.
5. In the confirmation popup, click the Confirm button to complete the edit.

Delete Pod Template

To delete a Pod Template, follow these steps.

1. On the Tool Details page, click the Agent (Kubernetes) tab.
2. Pod Template Management In the list, click the Details button of the agent you want to view. Agent (Kubernetes) Details screen appears.
3. Click the Delete button.
4. In the confirmation popup, click the Confirm button to complete the deletion.

Managing Agents (VM)

You can manage the list of Nodes available for use in Jenkins.
This feature allows you to operate the Jenkins Management > Node Management menu of Jenkins from the DevOps Console.
DevOps Console only supports one-way registration to Jenkins. (In other words, changes made by the user in DevOps Console will overwrite the information in Jenkins.)

To manage the agent (VM), follow the steps below.

1. On the Tool Details page, click the Agent (VM) tab.
2. Click the Info icon in the Node Management list. The Node Usage Guide popup opens.

Manage Agent Connections

Register the tunneling port that connects the actual Jenkins and the agent (VM). The tunneling port may vary for each Jenkins.

To manage agent connections, follow these steps.

1. On the Tool Details page, click the Agent (VM) tab.
2. Click the Edit icon of Agent Connection Management. The Agent Connection Management popup window opens.
3. After entering the content, click the Save button.

Add Agent (VM)

To add an agent (VM), follow the steps below.

1. On the Tool Details page, click the Agent (VM) tab.
2. Click the Add button in Agent Connection Management. The Add Agent (VM) screen appears.
3. After entering the content, click the Save button.
4. In the confirmation popup, click the Confirm button to complete the deletion.

   Item	description
   Target OS	Enter the VM’s OS information.
   Agent name	Enter the VM name.
   Remote root directory	Enter the directory path.
   Label	Enter the Label value to invoke the agent in the Jenkins Pipeline Script.
   Tool path	Information that maps to the Jenkins Tool Locations field, enter the name/home path Only tools added to the global tool list can be selected.
   Support stage	Select the supported stage configuration This information is used for configuring the build pipeline template in the DevOps Console. Required stage information cannot be deselected.

   Table. Agent (VM) Add Input Items

Agent (VM) Details

To view the detailed information of an agent (VM), follow the steps below.

1. On the Tool Details page, click the Agent (VM) tab.
2. In the Node Management list, click the agent. The Agent (VM) Details screen appears.
3. Click the Information icon of Jenkins - Agent Connection Information.
4. Agent Connection Guide The popup window opens.

Integrate Agent (VM)

To register and use the agent (VM), you must connect to the actual VM server.

To integrate the agent (VM), follow these steps.

1. On the Tool Details page, click the Agent (VM) tab.
2. From the Node Management list, click the agent you want to integrate. The Agent (VM) Details screen appears.
3. Refer to jnlpUrl and secret.
4. Click the Info icon of Jenkins - Agent Connection Information. The Agent Connection Guide popup opens.
5. Agent File Download Click the button to download the agent.jar file.
   • There may be issues running depending on the version of agent.jar.
   • You can also download it directly from your own Jenkins. ({JENKINS_URL}/jnlpJars/agent.jar)
6. Connect to the VM server to be deployed and create a directory.
7. Copy the downloaded agent.jar file to the generated directory.
8. Run the following command in the generated directory path.

java -jar agent.jar -jnlpUrl {jnlpUrl} -secret {secret}

java -jar agent.jar -jnlpUrl {jnlpUrl} -secret {secret}

Modify Agent (VM)

To modify the agent (VM), follow the procedure below.

1. On the Tool Details page, click the Agent (VM) tab.
2. Click the agent you want to edit in the Node Management list. The Agent (VM) Details screen appears.
3. Click the Edit button.
4. After editing the content, click the Save button.
5. In the confirmation popup, click the Confirm button to complete.

Delete Agent (VM)

To delete the agent (VM), follow these steps.

1. On the Tool Details page, click the Agent (VM) tab.
2. Click the agent you want to delete from the Node Management list. The Agent (VM) Details screen appears.
3. Click the Delete button.
4. Click the Confirm button in the confirmation popup to complete.

Managing Global Libraries

You can manage the list of libraries available in the build pipeline. The Jenkins Management → System Settings → Global Pipeline Libraries menu of Jenkins can be managed through the DevOps Console.
The Credential information linked to the library can be viewed in the Jenkins Management > Manage Credentials menu.
DevOps Console only supports one-way registration to Jenkins. (In other words, changes made by the user in DevOps Console will overwrite the information in Jenkins.)

To manage the agent(VM), follow these steps.

1. On the Tool Details page, click the Global Library tab.

Add Global Library

To add a global library, follow these steps.

1. Tool Details on the page, click the Global Library tab.
2. Click the Add button. The Add Global Library screen appears.
3. After entering the content, click the Save button.
4. In the confirmation popup, click the Confirm button to complete.

   Item	description
   Library name	Enter the name of the library.
   type	It is fixed to SCM and cannot be changed.
   Library URL	Enter the Git repository URL where the library is located.
   Default version	Enter the branch name or tag of the Git repository that contains the library.
   ID	Enter the ID to pull the library.
   password	Enter the password to pull the library.

   Table. Global Library Additional Input Items

Global Library Details

To view the detailed information of the global library, follow these steps.

1. On the Tool Details page, click the Global Library tab.
2. In the Global Library list, click the item you want to view in detail. The Global Library Details screen appears.

Modify Global Library

To modify the global library, follow these steps.

1. On the Tool Details page, click the Global Library tab.
2. From the Global Library list, click the item you want to view in detail. The Global Library Details screen appears.
3. Click the Edit button.
4. After editing the content, click the Save button.
5. Click the Confirm button in the confirmation popup to complete.

Delete Global Library

To delete the global library, follow these steps.

1. Tool Details on the page, click the Global Library tab.
2. Global Library Click the item you want to delete from the list. Global Library Detail screen appears.
3. Click the Delete button.
4. In the confirmation popup, click the Confirm button to complete.

Manage supported tenants/project groups

The user can manage the tenant or project group that will use the tool.

To manage supported tenants or project groups, follow these steps.

1. On the Tool Details page, click the Supported Tenant or Supported Information tab.

Add supported tenant/project group

To add a supported tenant or project group, follow these steps.

1. On the Tool Details page, click the Supported Tenant or Supported Information tab.
2. Click the Add button. The Add Tenant/Project Group popup window opens.
3. After entering the content, click the Save button.
4. In the confirmation popup, click the Confirm button to complete.

   Item	description
   Tenant/Project Group	Select the tenant/project group that will use the tool.
   Use status	Select whether to use the tool in this tenant/project group.
   Whether new creation is possible	Select whether to allow creating new repositories in this tenant/project group. This setting can only be configured for the tool categories listed below. SCM Repository Image Registry Code Quality Artifact Repository Helm Chart Repository Test Management Project Management Software

   Table. Additional Input Items for Supported Tenant/Project Group

Modify supported tenant/project group

To modify the supported tenant/project group, follow these steps.

1. On the Tool Details page, click the Supported Tenant or Support Information tab.
2. In the Supported Tenant or Supported Information list, select Usage status and New creation allowed to modify.

Transfer Management Tenant/Project Group

To transfer the management tenant/project group, follow the steps below.

1. On the Tool Details page, click the Supported Tenant or Supported Information tab.
2. Click the Transfer Management Tenant or Transfer Management Project Group button. The Transfer Management Tenant or Transfer Management Project Group popup window opens.
3. Select the target tenant or project group for transfer, then click the Save button.

Delete supported tenant/project group

To delete a managed tenant/project group, follow these steps.

1. On the Tool Details page, click the Supported Tenant or Supported Information tab.
2. Select the checkbox of the tenant/project group you want to delete.
3. Click the Delete button.
4. Click the Confirm button in the confirmation popup to complete.

Support K8S cluster management

The user can manage the K8S cluster where the tool will be used.

To manage the supported K8S cluster, follow these steps.

1. On the Tool Details page, click the Supported K8S Cluster tab.

Add supported K8S cluster

To add a supported K8S cluster, follow the steps below.

1. On the Tool Details page, click the Supported K8S Cluster tab.
2. On the Supported K8S Cluster page, click the Add button. The Add K8S Cluster popup window opens.
3. After entering the content, click the Save button.
4. In the confirmation popup, click the Confirm button to complete.

   Item	description
   K8S cluster	Select the K8S cluster to use with the tool.
   Use status	Select whether to use the tool in this tenant/project group.
   Whether new creation is possible	Select whether to allow creating new repositories in this tenant/project group. This setting can only be configured for the tool categories below. SCM Repository Image Registry Code Quality Artifact Repository Helm Chart Repository Test Management Project Management Software

   Table. Additional input fields for supported K8S clusters

Modify supported K8S cluster

To modify the supported K8S cluster, follow the steps below.

1. On the Tool Details page, click the Supported K8S Cluster tab.
2. In the Supported K8S Clusters list, select Usage Status and New Creation Availability to edit.

Delete supported K8S cluster

To delete the supported K8S cluster, follow these steps.

1. Click the Supported K8S Cluster tab on the Tool Details page.
2. Supported K8S clusters list, select the checkbox of the K8S cluster you want to delete.
3. Click the Delete button.
4. In the confirmation popup, click the Confirm button to complete.

Manage tool operators

To manage tool operators, follow the steps below.

1. On the Tool Details page, click the Tool Operator tab.

Add tool operator

To add a tool operator, follow these steps.

1. Tool Details page, click the Tool Operator tab.
2. Click the Add button. The Add Tool Operator popup opens.
3. Select the operator and click the Save button.
4. In the confirmation popup, click the Confirm button to complete.

Delete tool operator

To delete a tool operator, follow these steps.

1. Tool Details page, click the Tool Operator tab.
2. Select the checkbox for the item you want to delete from the tool administrator list.
3. Click the Delete button.
4. In the confirmation popup, click the Confirm button to complete.

Managing Jenkins Recommended Plugins

You can check the installed Jenkins version and whether recommended plugins are installed and their version information, and you can update and install the recommended plugins.

• Tool version: Jenkins version information
• Recommended plugins: installation status and version information

Check tool version and recommended plugin information

To check the tool version and recommended plugin information, follow these steps.

1. Tool Details page, click the Basic Information tab.
2. If there is recommended plugin information that requires installation or update, an informational popup appears, and clicking OK moves you to the Plugins tab.
3. On the Tool Details page, click the Plugin tab.
4. Check the entries for Tool Version, Recommended Plugins.

Install recommended plugins

To install the recommended plugin, follow these steps.

1. In the Recommended plugins area, select the Install button of the plugin you want to install.
2. In the Recommended Plugin Installation popup, select the OK button.
3. A popup appears indicating that the installation request has been completed, and the actual installation details can be viewed via the link in the popup.

Update recommended plugins

To update the recommended plugin, follow these steps.

1. In the Recommended plugins area, select the Update button of the plugin you want to update.
2. Select the Confirm button in the Recommended Plugin Update popup.
3. A popup appears indicating that the installation request has been completed, and the actual installation details can be viewed via the link in the popup.
4. You must restart Jenkins to apply the update you need to do so.

Delete tool

To uninstall the tool, follow these steps.

1. On the Tool page, click the tool you want to delete. You will be taken to the Tool Details page.
2. Click the Delete button.
3. In the confirmation popup, click the Confirm button to complete.

2 - App Template

App. A template is a feature provided to enable users to quickly set up a development environment.

The App. template consists of sample source code, Dockerfile, Helm chart, etc., and users can quickly set up a development environment using the App. template when creating a project.

We provide App templates for various frameworks such as Node.js, Python, Spring Boot, and users can also create and register their own App templates.

App. Getting Started with Template

App. To start template management, 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. From the left menu, click the Tools & Templates > App. Templates menu. You will be taken to the App. Templates page.

App. Add Template

Users can add their own App templates.

Source code

App. This is the source code that will be used in the template to build a sample project.

App. A usable SCM Repository must exist in the tenant or project group where the template will be registered. For instructions on registering an SCM Repository tool, see Add Tool.

Register the source code in the SCM Repository in advance. When registering an App template, the corresponding SCM Repository appears, and you should enter the path of the pre-registered source code.

Dockerfile

To register an App. Template that supports deployment target projects in the form of Kubernetes or VM (Docker), you must either add a Dockerfile to the source code when registering the source code or register a Dockerfile through 도커파일 템플릿 관리하기.

When writing a Dockerfile, the FROM clause must be fixed as FROM ${BASE_IMAGE}.

The registered ${BASE_IMAGE} value is substituted via the Velocity Template Engine as the image.repository value in the Helm chart when the deployment target is Kubernetes, and as the image path registered in Managing Supported Images when the deployment target is VM (Docker).

Dockerfile file sample

FROM ${BASE_IMAGE}

COPY *.jar app.jar
ENTRYPOINT ["java","-jar","/app.jar"]

FROM ${BASE_IMAGE}

COPY *.jar app.jar
ENTRYPOINT ["java","-jar","/app.jar"]

App. Register Template

App. To register a template, follow these steps.

1. Click the Add button on the App. Template page. You will be taken to the App. Template Add page.
2. App. Add Template On the page, select the template support type and click the Start button.
3. After entering the required information, click the Complete button.

   Item	Explanation
   type	Select the template type. Refer to App. Template Type for type-specific descriptions.
   Tenant/Project Group	Select the tenant/project group to map.

   Table. App. Add Template - Template Supported Type Selection Item

   Item	Explanation
   Deployment target	Select the deployment target supported by the template Kubernetes: when the deployment target is a cluster using Helm charts VM(Artifact): when the deployment target is a VM server using an Artifact file VM(Docker): when the deployment target is a VM server using a Docker image N/A: when there is no deployment target (ex. Android)
   Template name	App. Enter the name of the template.
   Application classification	Select the category of the application included in the template Used to classify the template.
   language	Select the programming language of the source code included in the template.
   source code	Select whether the template includes source code.
   Source code repository type	Select the location where the source code to be included in the template is stored. You can choose SCM or a compressed file (ZIP).
   Repository URL	Enter the repository URL where the template source code is located The list of SCM Repository tool available in the tenant and project group will be displayed.
   Repository branch	Enter the branch of the repository where the template source code is located.
   Individual authentication information	Enter the credentials to access the repository If you select ‘Do not use’, the credentials used when registering the tool will be used.
   Dockerfile path	Enter the Dockerfile path within the repository Used when building the Docker image.
   code quality	Select whether to use code quality.
   Explanation	App. Write a description for the template.
   Document URL	Enter the URL of the document that describes the template It will appear as a link on the template selection page when creating a project.
   Template icon	Select the icon to use in the template.
   Build output path	Specify the build output path and filename.
   Dockerfile type	Select Dockerfile type You can choose whether to use the Dockerfile file within SosoCode, or to use the information registered in Manage Dockerfile Templates. When you select the GUI template, the Dockerfile Template tab becomes active.

   Table. App. Add Template - Basic Information Input Items

App. Edit template basic information

App. To modify the template’s basic information, follow these steps.

1. On the App. Template page, click the item you want to edit. You will be taken to the App. Template Details page.
2. Click the Basic Information tab on the App. Template Details page.
3. Click the Edit button in the Basic Information tab.
4. After editing the required information, click the Save button.

Manage pipeline templates

This is the build pipeline configuration that is automatically set up when a user creates a project using the App template.

Add pipeline template

To add a pipeline template, follow these steps.

1. On the App. Template page, click the item you want to add. You will be taken to the App. Template Details page.
2. On the App. Template Details page, click the Pipeline Template tab.
3. Click the Add button on the Pipeline Template tab. You will be taken to the Add Pipeline Template page.
4. On the Add Pipeline Template page, enter the required information and click the Save button.

   Item	Explanation
   Template name	Enter the name of the pipeline template.
   Base Template (Base Template)	The default template is used for pipeline configuration when creating a project. If a default template is not registered, it is automatically set to ON, and this setting cannot be changed.
   Support Jenkins	Select the Jenkins that will support this pipeline template A list of CICD pipeline tools available in the tenant and project group is displayed. It is required to refer to the necessary information in the Tools area when configuring stages.
   environment variable	Enter environment variable information For detailed information about environment variables, refer to Configure environment variables.
   Stage	Enter information for each stage For detailed information about stages, refer to Setting up stages.

   Table. Pipeline Template Additional Input Items

Edit pipeline template

To modify the pipeline template, follow these steps.

1. On the App. Template page, click the item you want to edit. You will be taken to the App. Template Details page.
2. On the App. Template Details page, click the Pipeline Template tab.
3. Click the item you want to edit in the Pipeline Template tab. You will be taken to the Pipeline Template Details page.
4. On the Pipeline Template Details page, click the Edit button. You will be taken to the Pipeline Template Edit page.
5. On the Pipeline Template Edit page, after modifying the information, click the Save button.

Delete pipeline template

To delete a pipeline template, follow these steps.

1. Click the item you want to delete on the App. Template page. You will be taken to the App. Template Details page.
2. On the App. Template Details page, click the Pipeline Template tab.
3. Click the item you want to delete in the Pipeline Template tab. You will be taken to the Pipeline Template Details page.
4. On the Pipeline Template Details page, click the Delete button.
5. Click the Confirm button in the confirmation popup.

Managing Dockerfile Templates

App. In the Basic Information section of the template, the tab appears only when the Dockerfile Type item is GUI Template.

Modify Dockerfile template

Follow these steps to modify the Dockerfile template.

1. On the App. Template page, click the item you want to edit. You will be taken to the App. Template Details page.
2. On the App. Template Details page, click the Dockerfile Template tab.
3. Click the Edit or Create button in the Dockerfile Template tab.
4. After entering the content in the Dockerfile Template tab, click the Save button.

   Item	Explanation
   Authentication Settings	Register the authentication information for the image to be used in the FROM clause of a multi-stage build.
   Add	Add the image to be used in the FROM clause of the multi-stage build.
   Multi-stage Dockerfile	Configure the Multi-stage based on the credentials and additional items you registered.
   Dockerfile	Create a basic Dockerfile.

   Table. Dockerfile Template Modification Input Items

The FROM clause is automatically set to the image path registered in 지원 이미지 관리하기.

Manage supported tenants/project groups

The user can manage the tenant or project group where the App template will be used.

To manage supported tenants or project groups, follow these steps.

1. Click the item you want to edit on the App. Template page. You will be taken to the App. Template Details page.
2. On the App. Template Details page, click the Supported Tenant or Supported Information tab.

Add supported tenant

To add a supported tenant, follow these steps.

1. Click the item you want to edit on the App. Template page. You will be taken to the App. Template Details page.
2. On the App. Template Details page, click the Supported Tenants tab.
3. Click the Add button on the Supported Tenant tab. The Add Tenant popup window opens.
4. Add Tenant In the popup window, select the tenant you want to support, then click the Save button.

Edit supported tenant information

To modify the information of the supported tenant, follow these steps.

1. Click the item you want to edit on the App. Template page. You will be taken to the App. Template Details page.
2. On the App. Template Details page, click the Supported Tenants tab.
3. In the Supported Tenant tab, select the verification status and usage status items for the tenant you want to change, and edit them.

   Item	Explanation
   Tenant	Available tenant information.
   Verification status	Select verification status Verifying Verification complete
   Whether to use	Select usage status It can be changed to Use only when Verification status is Verified.

   Table. Supported Tenant Screen Items

Edit supported project group information

To modify the information of the supported project group, follow these steps.

1. Click the item you want to edit on the App. Template page. You will be taken to the App. Template Details page.
2. On the App. Template Details page, click the Support Information tab.
3. Click the Edit button in the Support Information tab. The App. Template Edit screen appears.
4. On the App. Template Edit screen, select the verification status and usage status items to edit them.
5. Click the Save button.

   Item	Explanation
   Project Group	Available project group information.
   Verification status	Select verification status Verifying Verification complete
   Whether to use	Select usage Verification status can be changed to Use only when it is Verification completed.

   Table. Support Information Screen Items

Transfer Management Tenant

To transfer the management tenant, follow these steps.

1. Click the item you want to edit on the App. Template page. You will be taken to the App. Template Details page.
2. On the App. Template Details page, click the Supported Tenants tab.
3. On the Support Tenant tab, click the Transfer Management Tenant button. The Transfer Management Tenant popup window opens.
4. Management Tenant Transfer In the popup window, after selecting the target tenant for transfer, click the Save button.

Delete supported tenant

To delete a supported tenant, follow these steps.

1. Click the item you want to edit on the App. Template page. You will be taken to the App. Template Details page.
2. On the App. Template Details page, click the Supported Tenants tab.
3. In the Supported Tenant tab, select the tenant you want to delete and click the Delete button.
4. In the confirmation popup, click the Confirm button.

Manage supported images

The supported image registered by the user is used in the FROM clause registered in the source code’s Dockerfile or Dockerfile template.

Add supported image

To add a supported image, follow the steps below.

1. On the App. Template page, click the item you want to edit. You will be taken to the App. Template Detail page.
2. On the App. Template Details page, click the Supported Image tab.
3. In the Supported Image tab, click the Add button. The Add Supported Image popup window opens.
4. Add supported image After entering the information in the popup window, click the Connection Test button.
5. Save button is enabled, click the Save button.
6. In the confirmation popup, click the Confirm button.

   Item	Explanation
   Enter image information	Enter the supported image and authentication information.
   Use the registrant’s authentication information	This is an option that can be selected when the chosen image registry is a tool that cannot grant permissions (e.g., SCR). If not checked, when a supported image user creates a project, the Pull permission for the image entered by the supported image user is added. If the tool cannot grant permissions, no permission granting is performed. If not checked, when a supported image user creates a project, the authentication credentials of the supported image registrant are used instead of the supported image user’s permissions.

   Table. Additional Input Fields for Supported Image

Delete supported image

To delete the support image, follow these steps.

1. On the App. Template page, click the item you want to edit. You will be taken to the App. Template Details page.
2. On the App. Template Details page, click the Supported Image tab.
3. In the Supported Images tab, select the checkbox of the item to delete and click the Delete button.
4. In the confirmation popup, click the Confirm button.

Manage supported Helm charts

The supported Helm chart registered by the user is used when creating a project using the App. template.

Add support for Helm chart

To add a supported Helm chart, follow these steps.

1. Click the item you want to edit on the App. Template page. You will be taken to the App. Template Details page.
2. App. Template Details on the page, click the Supported Helm Chart tab.
3. In the Supported Helm Chart tab, click the Edit button. The App. Template Edit screen appears.
4. App. Template Modification On the screen’s Helm Chart List, select the checkbox of the Helm chart to be used, then add it to the Selected Helm Chart List using the Add button, and click the Save button.

Modify the supported Helm chart

To modify the supported Helm chart, follow these steps.

1. On the App. Template page, click the item you want to edit. You will be taken to the App. Template Details page.
2. Click the Supported Helm Chart tab on the App. Template Details page.
3. Click the Edit button in the Supported Helm Chart tab. The App. Template Edit screen appears.
4. On the App. Template Edit screen’s Helm Chart List, select the checkboxes of the Helm charts to use, then modify the Selected Helm Chart List using the Add and Delete buttons, and click the Save button.

Delete supported Helm chart

To delete the support Helm chart, follow these steps.

1. Click the item you want to edit on the App. Template page. You will be taken to the App. Template Details page.
2. On the App. Template Details page, click the Supported Helm Chart tab.
3. Click the Edit button in the Supported Helm Chart tab. The App. Template Edit screen appears.
4. App. Template Edit on the Selected Helm Chart List screen, select the checkbox of the Helm chart to delete, then delete it using the Delete button and click the Save button.

App. Delete Template

App. To delete the template, follow these steps.

1. Click the item you want to delete on the App. Template page. Navigate to the App. Template Details page.
2. On the App. Template Details page, click the Basic Information tab.
3. Click the Delete button on the Basic Information tab.
4. In the confirmation popup, click the Confirm button.

3 - Register User-installed Jenkins Tool

Getting started with registering a user-installed Jenkins tool

Install Jenkins and plugins.

Jenkins installation

Before installing

To register Jenkins in the DevOps Console, Jenkins generally must meet the following conditions. If there are other conditions, register an SR before installation to verify.

• Use a domain for Jenkins access
• Jenkins domain is registered in DNS
• Use HTTPS (port 443) and a public certificate for Jenkins communication.

Installation

Install Jenkins on a VM or Kubernetes

Plugin Installation

Install the following plugins in Jenkins.

Jenkins configuration

Common Settings

Jenkins Administration > System

Jenkins Administration > Security

Support email format for Jenkins Username

• By default, Jenkins does not allow the @ sign or dot (.) to be used in the login username. However, since DevOps Console uses an email address as the username, we configure Jenkins to allow email addresses as usernames as well.
• Create the file /{JENKINS_HOME}/init.groovy.d/init.groovy, add the following content, and restart Jenkins.
  • (ex) /var/jenkins_home/init.groovy.d/init.groovy

hudson.security.HudsonPrivateSecurityRealm.ID_REGEX=/^[\w-\.\@\_]+$/

hudson.security.HudsonPrivateSecurityRealm.ID_REGEX=/^[\w-\.\@\_]+$/

Additional Jenkins configuration installed on Kubernetes

RBAC

Configure RBAC on Jenkins’s Service Account so that Jenkins can create Pods in Kubernetes.

# In GKE need to get RBAC permissions first with
# kubectl create clusterrolebinding cluster-admin-binding --clusterrole=cluster-admin [--user=<user-name>|--group=<group-name>]
 
---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: jenkins
 
---
kind: Role
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: jenkins
rules:
- apiGroups: [""]
  resources: ["pods"]
  verbs: ["create","delete","get","list","patch","update","watch"]
- apiGroups: [""]
  resources: ["pods/exec"]
  verbs: ["create","delete","get","list","patch","update","watch"]
- apiGroups: [""]
  resources: ["pods/log"]
  verbs: ["get","list","watch"]
- apiGroups: [""]
  resources: ["events"]
  verbs: ["watch"]
- apiGroups: [""]
  resources: ["secrets"]
  verbs: ["get"]
 
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  name: jenkins
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: Role
  name: jenkins
subjects:
- kind: ServiceAccount
  name: jenkins

# In GKE need to get RBAC permissions first with
# kubectl create clusterrolebinding cluster-admin-binding --clusterrole=cluster-admin [--user=<user-name>|--group=<group-name>]
 
---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: jenkins
 
---
kind: Role
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: jenkins
rules:
- apiGroups: [""]
  resources: ["pods"]
  verbs: ["create","delete","get","list","patch","update","watch"]
- apiGroups: [""]
  resources: ["pods/exec"]
  verbs: ["create","delete","get","list","patch","update","watch"]
- apiGroups: [""]
  resources: ["pods/log"]
  verbs: ["get","list","watch"]
- apiGroups: [""]
  resources: ["events"]
  verbs: ["watch"]
- apiGroups: [""]
  resources: ["secrets"]
  verbs: ["get"]
 
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  name: jenkins
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: Role
  name: jenkins
subjects:
- kind: ServiceAccount
  name: jenkins

Jenkins Management > Clouds

kubernetes

• Add the kubernetes cloud.
• Set up the Kubernetes cloud as follows. Use the default values for the remaining items.

kubernetes > Pod Templates

• Add a Pod Template.
• BASE-TEMPLATE is a parent template used in the DevOps Console to define values that should be shared across all Pod Templates.

Register Jenkins tool in DevOps Console

Register Firewall

Refer to the table below and register the firewall in Jenkins.

DevOps Console Tasks

• For detailed information about registering the Jenkins tool, see Add Tool
• In the tool registration step, check the plugins installed on Jenkins, and if any plugins need to be installed, a plugin installation guide page will be displayed. Download and install the plugins as instructed.

Jenkins Verification

Jenkins Management > System

Global Trusted Pipeline Libraries

• Check that cicdpaas is configured in the Library.
• If it is not configured
  • Verify the communication between DevOps Console and Jenkins.
  • DevOps Console > Management > Jenkins detail screen > Check the settings in the Global Library tab.

DevOps Console Credentials

• Test Connection Click the button to confirm that Success appears.

Add an agent (VM) to Jenkins

DevOps Console Tasks

Add Agent (VM)

Jenkins Tasks

Jenkins Management > Nodes > Agent Detail View

Verify that the Agent added in the DevOps Console has been created. Run the Agent according to the guide on the Jenkins screen and connect it to Jenkins.

Add an agent (Kubernetes) to Jenkins

Before Adding a Kubernetes Agent

Create User‑Jenkins Agent Image

• For CI/CD in Jenkins, an agent image is required.
• Create a Jenkins agent image that matches the user’s needs by using the default images provided by Jenkins.
• After creating the image, push it to the user’s image repository.

FROM jenkins/inbound-agent:latest-jdk17

USER root

# Docker CLI
RUN curl -L0 "https://download.docker.com/linux/static/stable/x86_64/docker-29.1.3.tgz" -o /tmp/docker.tgz && \
    tar --extract \
      --file /tmp/docker.tgz \
      --strip-components 1 \
      --directory /usr/local/bin/ && \
    rm /tmp/docker.tgz

COPY --from=docker/buildx-bin /buildx /usr/libexec/docker/cli-plugins/docker-buildx

# Install your build tools...
# xxx

USER jenkins

FROM jenkins/inbound-agent:latest-jdk17

USER root

# Docker CLI
RUN curl -L0 "https://download.docker.com/linux/static/stable/x86_64/docker-29.1.3.tgz" -o /tmp/docker.tgz && \
    tar --extract \
      --file /tmp/docker.tgz \
      --strip-components 1 \
      --directory /usr/local/bin/ && \
    rm /tmp/docker.tgz

COPY --from=docker/buildx-bin /buildx /usr/libexec/docker/cli-plugins/docker-buildx

# Install your build tools...
# xxx

USER jenkins

Docker‑in‑Docker Image

• In the DevOps Console, Docker in Docker is used to create Docker images in a Kubernetes environment.
• Use Docker’s provided dind (Docker‑in‑Docker) image and push it to your repository.

DevOps Console Tasks

• Add Pod Template
  • By default, one (or multiple) agents are registered. Delete the default registered agent.
• If you need to build a Docker image, select Docker in Docker.
• Enter the JNLP image URL with the Jenkins agent address of the user you created above.

Jenkins Tasks

Jenkins Management > Clouds > Kubernetes > Pod Templates

• The agent (Kubernetes) added from the DevOps Console is registered as a Pod Template.
• If Docker‑in‑Docker is selected in DevOps Console, the default image address is pre‑filled in the dind container. Replace it with the image address you pushed to your repository.