This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Tools & Templates

1 - Tool Management

A tool refers to an application that interacts with the DevOps Console to support CI/CD functionality.

For a list of tools currently supported by the DevOps Console, refer to Tool Classification.

Getting Started with Tool Management

To start managing tools, follow these steps:

  1. Main page, click the Manage icon in the top right corner. You will be taken to the Tenant Dashboard page.
  2. In the left menu, click Tools & Templates > Tools. You will be taken to the Tools page.

Tool Types

Each tool has a different usage area depending on the tool type.

Tool TypeDescription
System Tool
  • Can be used across the entire DevOps Console.
  • Only system administrators can manage it.
  • Tenant administrators can only disable it if it is enabled for their tenant.
Tenant Tool
  • Can be used in a specific tenant.
  • Can be mapped to multiple tenants and clusters for use.
  • Only the tenant administrator of the initially registered tenant can manage it.
  • Additional registered tenants can only use it.
ProjectGroup Tool
  • Can be used in a specific project group.
  • Can be mapped to multiple project groups for use.
  • Only the owner of the project group can manage it.
Table. Tool Types

Tool Classification

The following is a list of tools currently supported by the DevOps Console:

Note
The list of supported tools may change (added/removed) according to the release schedule.
Tool ClassificationTool
CICD PipelineJenkins
SCM RepositoryGitLab, GitHub, Git-based SCM
Image RegistryHarbor, Docker Hub, SCP Container Registry, Docker Image Registry
Code QualitySonarQube
Artifact RepositoryNexus, Object Storage (S3 compatible)
Helm Chart RepositoryHarbor
Project Management SoftwareJIRA
Table. Tool Classification

Management Affiliation

The tenant or project group type selected when adding a tool indicates the management affiliation. The following icons distinguish the type of management affiliation:

  • Tenant Management Affiliation Management affiliation is a tenant.
  • Project Group Management Affiliation Management affiliation is a project group.

Adding a Tool

To add a tool, follow these steps:

  1. On the Tools page, click the Add button. The Add Tool popup window will open.

Selecting Tool Support Type

  1. In the Add Tool popup window, select the tool’s support type.
  2. Complete the selection and click the Next button. The Basic Information input screen will appear.
ItemDescription
TypeSelect the tool’s support type.
Tenant/Project GroupSelect which tenant or project group to map to.
Table. Tool Support Type Selection Items

Entering Basic Information

  1. In the Add Tool popup window, on the Basic Information input screen, select the tool classification and tool. The input screen will vary depending on the selected tool.
  2. Enter the necessary information and click the Connection Test button.
  3. Click the Next button.

SCM Repository

ItemDescription
Tool NameEnter a tool name for user identification.
Tool ClassificationSelect the tool classification.
ToolSelect the tool.
URLEnter the URL address to access the tool.
  • Duplicate URLs cannot be registered.
URL for APIEnter the Github.com API path.
Org Creation PossibleSelect whether to allow creation of new Github Organizations in the tenant or project group.
New Creation PossibleSelect whether to allow creation of new repositories in the tenant or project group.
IDP UsageSelect whether to use IDP.
User Account Authentication TypeSelect the authentication type for tool users.
Admin Account Authentication TypeSelect the authentication type for tool administrators.
Admin IDEnter the admin ID for the tool.
Admin Password / TokenEnter the admin password or token for the tool.
Table. SCM Repository Input Items

CICD Pipeline

ItemDescription
Tool NameEnter a tool name for user identification.
Tool ClassificationSelect the tool classification.
ToolSelect the tool.
URLEnter the URL address to access the tool.
  • Duplicate URLs cannot be registered.
Mail ServiceSelect whether to use the email sending feature.
TypeSelect whether to use the tool for development or operation.
IPEnter the IP list.
IP RangeEnter the IP range.
IDP UsageSelect whether to use IDP.
IDP TypeIf using IDP, select the IDP type (CMP IDP, other IDP).
User Account Authentication TypeSelect the authentication type for tool users.
Admin Account Authentication TypeSelect the authentication type for tool administrators.
Admin IDEnter the admin ID for the tool.
Admin Password / TokenEnter the admin password or token for the tool.
Table. CICD Pipeline Input Items
Caution

If the Number of executors item in the Built-In Node of Jenkins system settings is set to 1 or more, tools may not be added due to potential security issues.

Image Registry

ItemDescription
Tool NameEnter a tool name for user identification.
Tool ClassificationSelect the tool classification.
ToolSelect the tool.
New Creation PossibleSelect whether to allow creation of new repositories in the tenant or project group.
URLEnter the URL address to access the tool.
  • Duplicate URLs cannot be registered.
URL for APIEnter the Docker Hub API path.
Image Repository URLEnter the URL for Docker Registry use.
Private SSL Certificate UsageSelect whether to use a private SSL certificate.
System Common Image InclusionSelect whether to include system common images.
IDP UsageSelect whether to use IDP.
User Account Authentication TypeSelect the authentication type for tool users.
Admin Account Authentication TypeSelect the authentication type for tool administrators.
Admin IDEnter the admin ID for the tool.
Admin Password / TokenEnter the admin password or token for the tool.
Table. Image Registry Input Items

Code Quality

ItemDescription
Tool NameEnter a tool name for user identification.
Tool ClassificationSelect the tool classification.
ToolSelect the tool.
New Creation PossibleSelect whether to allow creation of new SonarQube projects in the tenant or project group.
URLEnter the URL address to access the tool.
  • Duplicate URLs cannot be registered.
Tool VersionEnter the SonarQube version.
IDP UsageSelect whether to use IDP.
User Account Authentication TypeSelect the authentication type for tool users.
Admin Account Authentication TypeSelect the authentication type for tool administrators.
Admin IDEnter the admin ID for the tool.
Admin Password / TokenEnter the admin password or token for the tool.
Table. Code Quality Input Items

Artifact Repository

ItemDescription
Tool NameEnter a tool name for user identification.
Tool ClassificationSelect the tool classification.
ToolSelect the tool.
New Creation PossibleSelect whether to allow creation of new Nexus repositories in the tenant or project group.
URLEnter the URL address to access the tool.
  • Duplicate URLs cannot be registered.
IDP UsageSelect whether to use IDP.
User Account Authentication TypeSelect the authentication type for tool users.
Admin Account Authentication TypeSelect the authentication type for tool administrators.
Admin IDEnter the admin ID for the tool.
Admin Password / TokenEnter the admin password or token for the tool.
Table. Artifact Repository Input Items

Helm Chart Repository

ItemDescription
Tool NameEnter a tool name for user identification.
Tool ClassificationSelect the tool classification.
ToolSelect the tool.
New Creation PossibleSelect whether to allow creation of new repositories in the tenant or project group.
URLEnter the URL address to access the tool.
  • Duplicate URLs cannot be registered.
Private SSL Certificate UsageSelect whether to use a private SSL certificate.
Helm Chart Repository URLEnter the repository URL for the tool.
  • Duplicate URLs cannot be registered.
IDP UsageSelect whether to use IDP.
User Account Authentication TypeSelect the authentication type for tool users.
Admin Account Authentication TypeSelect the authentication type for tool administrators.
Admin IDEnter the admin ID for the tool.
Admin Password / TokenEnter the admin password or token for the tool.
Table. Helm Chart Repository Input Items

Project Management Software

ItemDescription
Tool NameEnter a tool name for user identification.
Tool ClassificationSelect the tool classification.
ToolSelect the tool.
New Creation PossibleSelect whether to allow creation of new JIRA projects in the tenant or project group.
URLEnter the URL address to access the tool.
  • Duplicate URLs cannot be registered.
IDP UsageSelect whether to use IDP.
User Account Authentication TypeSelect the authentication type for tool users.
Admin Account Authentication TypeSelect the authentication type for tool administrators.
Admin IDEnter the admin ID for the tool.
Admin Password / TokenEnter the admin password or token for the tool.
Table. Project Management Software Input Items

Entering Additional Information

  1. On the Add Tool popup window, on the Basic Information input screen, click the Next button. The Additional Information input screen will appear.
  2. Select each item and click the Complete button.
  3. In the confirmation popup window, click the Confirm button to complete the tool addition.
ItemDescription
UsageSelect whether to use the tool in the tenant or project group.
New Creation PossibleSelect whether to allow creation of new repositories in the tenant or project group.
  • Only available for tools with a classification of SCM Repository.
Table. Additional Information Input Items

Tool Details

To manage tool details, follow these steps:

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

Managing Tool Basic Information

To view 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 Modify button.
  3. Modify the necessary information and click the Save button.

Managing Global Tools

Note
The Global Tool tab is only visible if the tool is Jenkins.

This feature allows you to manipulate the Global Tool Configuration menu in the Jenkins web screen from the DevOps Console. The DevOps Console only supports one-way registration to Jenkins. (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 Tool can be used in the Tools section when configuring a stage.

To manage global tools, follow these steps:

  1. Click the Global Tool tab on the Tool Details page.

Adding Global Tools

To add a global tool, follow these steps:

  1. Click the Edit icon for the item you want to add in the Global Tool tab. The Global Tool Management popup window will open.
    • Required Tools are automatically set by the DevOps Console.
    • Required Tools cannot be deleted, and only the home path can be modified.
  2. Click the Add button. A new row will be added to the bottom of the list.
  3. Enter the information in the new row and click the Save button.
  4. Click the Confirm button in the confirmation popup window to complete the process.
ItemDescription
Tool TypeThe tool type is automatically set.
NameEnter the tool name.
Home PathEnter the path where the tool is installed.
Table. Global Tool Add Input Items

Modifying Global Tools

To modify a global tool, follow these steps:

  1. Click the Edit icon for the item you want to modify. The Global Tool Management popup window will open.
  2. Modify the content and click the Save button.
  3. Click the Confirm button in the confirmation popup window to complete the modification.

Deleting Global Tools

To delete a global tool, follow these steps:

  1. Click the Global Tool tab on the Tool Details page. Click the Edit icon for the item you want to delete. The Global Tool Management popup window will open.
  2. Delete the content and click the Save button.
  3. Click the Confirm button in the confirmation popup window to complete the deletion.

Managing Agent (Kubernetes)

Note
The Agent (Kubernetes) tab is only visible if the tool is Jenkins.

This feature allows you to manage the agents (slaves) used in Jenkins builds.

The Jenkins web screen’s 1) Jenkins Management > System Settings > Cloud > Pod Templates or 2) Jenkins Management > Node Management > Configure Clouds > Pod Templates menu can be manipulated from the DevOps Console.

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

To manage agents (Kubernetes), follow these steps:

  1. Click the Agent (Kubernetes) tab on the Tool Details page.
  2. Click the Information icon in the Pod Template Management list. The Pod Template Usage Guide popup window will open.

Adding Container Resource Types

Guide

Modifying the container resource type will affect the Pod Template.

  • Changing the container resource type from Not Used to Used will increase the number of Pod Templates by (container resource type number X Pod Template number).
  • Changing the container resource type from Used to Not Used will decrease the number of Pod Templates back to the original number.
  • The increased Pod Templates’ agent names, labels, etc. will be automatically generated by combining the Resource Type item entered by the user when registering the container resource type to avoid duplication.

To add a container resource type, follow these steps:

  1. Click the Agent (Kubernetes) tab on the Tool Details page.
  2. Click the Edit icon in the Container Resource Type Management section. The Container Resource Type Management popup window will open.
  3. Click the Add button and enter the content. Click the Save button.
  4. Click the Confirm button in the confirmation popup window to complete the process.
ItemDescription
UsageSet the usage.
  • To change the usage, there must be no build pipeline configured using the corresponding Jenkins tool.
Resource TypeEnter the resource name.
CPU/Memory (Request)Enter the requested resource value when configuring the Kubernetes Pod Agent.
CPU/Memory (Limit)Enter the limited resource value when configuring the Kubernetes Pod Agent.
Table. Container Resource Type Add Input Items

Modifying Container Resource Types

To modify a container resource type, follow these steps:

  1. Click the Agent (Kubernetes) tab on the Tool Details page.
  2. Click the Edit icon in the Container Resource Type Management section. The Container Resource Type Management popup window will open.
  3. Modify the content and click the Save button.
  4. Click the Confirm button in the confirmation popup window to complete the modification.

Deleting Container Resource Types

To delete a container resource type, follow these steps:

  1. Click the Agent (Kubernetes) tab on the Tool Details page.
  2. Click the Edit icon in the Container Resource Type Management section. The Container Resource Type Management popup window will open.
  3. Delete the content and click the Save button.
  4. Click the Confirm button in the confirmation popup window to complete the deletion.

Adding Pod Templates

To add a Pod Template, follow these steps:

  1. Click the Agent (Kubernetes) tab on the Tool Details page.
  2. Click the Add button in the Pod Template Management list. The Add Agent (Kubernetes) screen will appear.
  3. Enter the content and click the Save button.
  4. Click the Confirm button in the confirmation popup window to complete the process.
ItemDescription
Target KubernetesSelect the target Kubernetes to add the Pod Template.
  • Displays the actual list of Kubernetes registered in Jenkins.
Agent NameEnter the name of the Pod Template.
LabelEnter the label value to call the corresponding agent in the Jenkins Pipeline Script.
Inherit Pod TemplateSelect the Pod Template to inherit the settings (environment variables, volumes, etc.).
  • Displays the actual list of Pod Templates registered in Jenkins.
ContainerEnter the information mapped to the Container Template item in Jenkins, such as name, Docker image, working directory, command, and arguments.
  • Required container information cannot be deleted, and the name cannot be changed.
Tool PathEnter the information mapped to the Tool Locations item in Jenkins, such as name and home path.
  • Only tools added to the global tool list can be selected.
Supported StageSelect the supported stage configuration.
  • Used in the build pipeline template configuration of the DevOps Console.
  • Required stage information cannot be deselected.
Table. Add Pod Template Input Items
Note

If the user does not check Docker Build in the Supported Stage item,

  • The corresponding Jenkins cannot be used when configuring a project using the Kubernetes or VM (Docker) type App template that requires Docker Build.
  • When configuring a build pipeline using Add Build Pipeline, the Docker Build stage cannot be added.

Viewing Pod Template Details

To view the details of a Pod Template, follow these steps:

  1. Click the Agent (Kubernetes) tab on the Tool Details page.
  2. Click the View Details button for the agent you want to view in the Pod Template Management list. The Agent (Kubernetes) Details screen will appear.

Modifying Pod Templates

To modify a Pod Template, follow these steps:

  1. Click the Agent (Kubernetes) tab on the Tool Details page.
  2. Click the View Details button for the agent you want to modify in the Pod Template Management list. The Agent (Kubernetes) Details screen will appear.
  3. Click the Modify button.
  4. Modify the content and click the Save button.
  5. Click the Confirm button in the confirmation popup window to complete the modification.

Deleting Pod Templates

To delete a Pod Template, follow these steps:

  1. Click the Agent (Kubernetes) tab on the Tool Details page.
  2. Click the View Details button for the agent you want to delete in the Pod Template Management list. The Agent (Kubernetes) Details screen will appear.
  3. Click the Delete button.
  4. Click the Confirm button in the confirmation popup window to complete the deletion.

Managing Agent (VM)

Note
The Agent (VM) tab is only visible if the tool is Jenkins.

This feature allows you to manage the list of nodes available in Jenkins. The Jenkins web screen’s Jenkins Management > Node Management menu can be manipulated from the DevOps Console. The DevOps Console only supports one-way registration to Jenkins. (In other words, changes made by the user in the DevOps Console will overwrite the information in Jenkins.)

To manage agents (VM), follow these steps:

  1. Click the Agent (VM) tab on the Tool Details page.
  2. Click the Information icon in the Node Management list. The Node Usage Guide popup window will open.

Managing Agent Connections

This feature registers the tunneling port to connect the actual Jenkins and agent (VM). The tunneling port may vary depending on Jenkins.

To manage agent connections, follow these steps:

  1. Click the Agent (VM) tab on the Tool Details page.
  2. Click the Edit icon in the Agent Connection Management section. The Agent Connection Management popup window will open.
  3. Enter the content and click the Save button.

Adding Agent (VM)

To add an agent (VM), follow these steps:

  1. Click the Agent (VM) tab on the Tool Details page.
  2. Click the Add button in the Agent Connection Management section. The Add Agent (VM) screen will appear.
  3. Enter the content and click the Save button.
  4. Click the Confirm button in the confirmation popup window to complete the process.
ItemDescription
Target OSEnter the OS information of the VM.
Agent NameEnter the name of the VM.
Remote Root DirectoryEnter the directory path.
LabelEnter the label value to call the corresponding agent in the Jenkins Pipeline Script.
Tool PathEnter the information mapped to the Tool Locations item in Jenkins, such as name and home path.
  • Only tools added to the global tool list can be selected.
Supported StageSelect the supported stage configuration.
  • Used in the build pipeline template configuration of the DevOps Console.
  • Required stage information cannot be deselected.
Table. Add Agent (VM) Input Items
Note

If the user does not check Docker Build in the Supported Stage item,

  • The corresponding Jenkins cannot be used when configuring a project using the Kubernetes or VM (Docker) type App template that requires Docker Build.
  • When configuring a build pipeline using Add Build Pipeline, the Docker Build stage cannot be added.

Viewing Agent (VM) Details

To view the details of an agent (VM), follow these steps:

  1. Click the Agent (VM) tab on the Tool Details page.
  2. Click the agent you want to view in the Node Management list. The Agent (VM) Details screen will appear.
  3. Click the Information icon in the Jenkins - Agent Connection Information section.
  4. The Agent Connection Guide popup window will open.

Connecting Agent (VM)

Note
To connect the agent, Java must be installed on the VM server.

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

To connect an agent (VM), follow these steps:

  1. Click the Agent (VM) tab on the Tool Details page.
  2. Click the agent you want to connect in the Node Management list. The Agent (VM) Details screen will appear.
  3. Refer to jnlpUrl and secret.
  4. Click the Information icon in the Jenkins - Agent Connection Information section. The Agent Connection Guide popup window will open.
  5. Click the Download Agent File button to download the agent.jar file.
    • The agent.jar version may cause issues with execution.
    • You can also download it directly from your Jenkins ({JENKINS_URL}/jnlpJars/agent.jar).
  6. Connect to the VM server where you want to deploy and create a directory.
  7. Copy the downloaded agent.jar file to the created directory.
  8. Run the following command in the created directory path:
Color mode
java -jar agent.jar -jnlpUrl {jnlpUrl} -secret {secret}
java -jar agent.jar -jnlpUrl {jnlpUrl} -secret {secret}
Agent (VM) Execution Command

Modifying Agent (VM)

To modify an agent (VM), follow these steps:

  1. Click the Agent (VM) tab on the Tool Details page.
  2. Click the agent you want to modify in the Node Management list. The Agent (VM) Details screen will appear.
  3. Click the Modify button.
  4. Modify the content and click the Save button.
  5. Click the Confirm button in the confirmation popup window to complete the modification.

Deleting Agent (VM)

To delete an agent (VM), follow these steps:

  1. Click the Agent (VM) tab on the Tool Details page.
  2. Click the agent you want to delete in the Node Management list. The Agent (VM) Details screen will appear.
  3. Click the Delete button.
  4. Click the Confirm button in the confirmation popup window to complete the deletion.

Managing Global Libraries

You can manage the list of libraries available in the build pipeline. This is a feature that can be manipulated in the DevOps Console from the Jenkins Jenkins Management -> System Settings -> Global Pipeline Libraries menu. Library and connected Credential information can be found in the Jenkins Management > Manage Credentials menu. The DevOps Console only supports one-way registration to Jenkins. (In other words, the information modified by the user in the DevOps Console will overwrite the information in Jenkins.)

To manage agents (VMs), follow these steps:

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

Adding Global Libraries

Note
Libraries with Required Library set to Y cannot be modified or deleted.

To add a global library, follow these steps:

  1. Tool Details page, click the Global Library tab.
  2. Click the Add button. The Add Global Library screen appears.
  3. Enter the contents and click the Save button.
  4. In the confirmation popup, click the Confirm button to complete.
ItemDescription
Library NameEnter the name of the library.
TypeFixed as SCM and cannot be changed.
Library URLEnter the Git repository URL where the library exists.
Default VersionEnter the branch name or tag of the Git repository where the library exists.
IDEnter the ID for pulling the library.
PasswordEnter the password for pulling the library.
Table. Global Library Addition Input Items

Viewing Global Library Details

To view the details of a global library, follow these steps:

  1. 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.
Note

If the Type is SCM, SCM-related information is exposed.

  • Required library, library name, type, library URL, default version, ID

Modifying Global Libraries

To modify a global library, follow these steps:

  1. 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.
  3. Click the Modify button.
  4. Modify the contents and click the Save button.
  5. In the confirmation popup, click the Confirm button to complete.

Deleting Global Libraries

To delete a global library, follow these steps:

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

Managing Supported Tenants/Project Groups

Note

The tab name may be exposed differently depending on the tool type.

  • System Tool/Tenant Tool: Supported Tenants
  • ProjectGroup Tool: Supported Information

Users can manage the tenants or project groups that can use the tool.

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

  1. Tool Details page, click the Supported Tenants or Supported Information tab.
Note
The Primary icon is displayed for the managed tenant/project group.

Adding Supported Tenants/Project Groups

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

  1. Tool Details page, click the Supported Tenants or Supported Information tab.
  2. Click the Add button. The Add Tenant/Project Group popup window opens.
  3. Enter the contents and click the Save button.
  4. In the confirmation popup, click the Confirm button to complete.
ItemDescription
Tenant/Project GroupSelect the tenant/project group that can use the tool.
UsageSelect whether to use the tool in the tenant/project group.
New Creation PossibleSelect whether to allow new repository creation in the tenant/project group.
This setting is only available for the following tool categories:
  • SCM Repository
  • Image Registry
  • Code Quality
  • Artifact Repository
  • Helm Chart Repository
  • Test Management
  • Project Management Software
Table. Supported Tenant/Project Group Addition Input Items

Modifying Supported Tenants/Project Groups

To modify a supported tenant/project group, follow these steps:

  1. Tool Details page, click the Supported Tenants or Supported Information tab.
  2. In the Supported Tenants or Supported Information list, select the usage and new creation possibility to modify.

Transferring Management Tenants/Project Groups

To transfer the management tenant/project group, follow these steps:

  1. Tool Details page, click the Supported Tenants 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 transfer target tenant or project group and click the Save button.

Deleting Supported Tenants/Project Groups

To delete a supported tenant/project group, follow these steps:

  1. Tool Details page, click the Supported Tenants or Supported Information tab.
  2. Select the checkbox of the tenant/project group you want to delete.
  3. Click the Delete button.
  4. In the confirmation popup, click the Confirm button to complete.
Note
The primary tenant/project group cannot be deleted.

Managing Supported K8S Clusters

Users can manage the K8S clusters that can use the tool.

To manage supported K8S clusters, follow these steps:

  1. Tool Details page, click the Supported K8S Clusters tab.

Adding Supported K8S Clusters

To add a supported K8S cluster, follow these steps:

  1. Tool Details page, click the Supported K8S Clusters tab.
  2. Click the Add button. The Add K8S Cluster popup window opens.
  3. Enter the contents and click the Save button.
  4. In the confirmation popup, click the Confirm button to complete.
ItemDescription
K8S ClusterSelect the K8S cluster that can use the tool.
UsageSelect whether to use the tool in the tenant/project group.
New Creation PossibleSelect whether to allow new repository creation in the tenant/project group.
This setting is only available for the following tool categories:
  • SCM Repository
  • Image Registry
  • Code Quality
  • Artifact Repository
  • Helm Chart Repository
  • Test Management
  • Project Management Software
Table. Supported K8S Cluster Addition Input Items

Modifying Supported K8S Clusters

To modify a supported K8S cluster, follow these steps:

  1. Tool Details page, click the Supported K8S Clusters tab.
  2. In the Supported K8S Clusters list, select the usage and new creation possibility to modify.

Deleting Supported K8S Clusters

To delete a supported K8S cluster, follow these steps:

  1. Tool Details page, click the Supported K8S Clusters tab.
  2. 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.

Managing Tool Operators

To manage tool operators, follow these steps:

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

Adding Tool Operators

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 window opens.
  3. Select the operator and click the Save button.
  4. In the confirmation popup, click the Confirm button to complete.

Deleting Tool Operators

To delete a tool operator, follow these steps:

  1. Tool Details page, click the Tool Operator tab.
  2. Select the checkbox of the operator you want to delete.
  3. Click the Delete button.
  4. In the confirmation popup, click the Confirm button to complete.
Note
The Plugins tab is only visible if the tool is Jenkins.

You can view the installed Jenkins version and plugin installation status and version information.

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

To view the tool version and required plugin information, follow these steps:

  1. Click Tool(CICD Pipeline) on the Tool Management page.
  2. If tool has an information to update or install recommended plugins info, then popup is occurred and click confirm button then move to Plugins tab.
  3. On the Tool Details page, click the Plugins tab.
  4. View the Tool Version and Recommended Plugins items.

Follow this procedure to install recommended plugins.

  1. On the Plugins page, Click Install button which you want to install plugin in Recommended Plugins area.
  2. Install Recommended Plugin popup is occured, and click Confirm button.
  3. Then popup appears message that installation request has been completed, and you can check the actual installation through the link in the popup.

Follow this procedure to update recommended plugins.

  1. On the Plugins page, Click Update button which you want to install plugin in Recommended Plugins area.
  2. Update Recommended Plugin popup is occured, and click Confirm button.
  3. Then popup appears message that update request has been completed, and you can check the actual installation through the link in the popup.
  4. You must restart your Jenkins to apply the update.

Deleting Tools

Note
Tools that are in use in a project cannot be deleted.

To delete a tool, follow these steps:

  1. Tool page, click the tool you want to delete. The Tool Details page opens.
  2. Click the Delete button.
  3. In the confirmation popup, click the Confirm button to complete.

2 - App Template

App Template is a feature provided for quick development environment setup.

App Template consists of sample source code, Dockerfile, Helm Chart, and more. Users can quickly set up their development environment using App Template when creating a project.

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

App Template TypeDescription
System Template
  • A tool that can be used across the DevOps Console.
  • Only system administrators can manage it.
  • Tenant administrators can only release it when it is available in their tenant.
Tenant Template
  • A template that can be used in a specific tenant.
  • It can be mapped to multiple tenants and used.
  • The administrator of the corresponding tenant can manage it.
ProjectGroup Template
  • A template that can only be used in a specific project group.
  • It can be mapped to only one project group and used.
  • The owner of the corresponding project group can manage it.
Table. App Template Type

Getting Started with App Template

To start managing App Templates, follow these steps:

  1. Main page, click the Manage icon at the top right. Move to the Tenant Dashboard page.
  2. In the left menu, click Tools & Templates > App Template. Move to the App Template page.

Adding App Template

Users can add their own App Templates.

Source Code

Source code used to configure a sample project in the App Template.

The SCM Repository tool must be available in the tenant or project group where the App Template will be registered. Refer to Adding Tools for how to register the SCM Repository tool.

Register the source code in the SCM Repository in advance. When registering the App Template, the registered SCM Repository will appear, and you can enter the path to the source code.

Dockerfile

Note
You can manage the Dockerfile without registering it inside the source code. Refer to Managing Dockerfile Templates for more information.
For explanations and writing methods of Dockerfile, refer to the official website.

To register an App Template that supports Kubernetes or VM (Docker) deployment targets, you must add a Dockerfile to the source code or register a Dockerfile through Managing Dockerfile Templates.

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

The registered ${BASE_IMAGE} value is replaced with the image.repository value of the Helm chart for Kubernetes deployment targets or the image path registered in Managing Supported Images for VM (Docker) deployment targets.

Dockerfile sample

Color mode
FROM ${BASE_IMAGE}

COPY *.jar app.jar
ENTRYPOINT ["java","-jar","/app.jar"]
FROM ${BASE_IMAGE}

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

Registering App Template

To register an App Template, follow these steps:

  1. App Template page, click the Add button. Move to the Add App Template page.
  2. Add App Template page, select the template support type and click the Start button.
  3. Enter the necessary information and click the Complete button.
ItemDescription
TypeSelect the type of template.
Tenant/Project GroupSelect the tenant or project group to map.
Table. Add App Template - Template Support Type Selection Items
ItemDescription
Deployment TargetSelect 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 artifact files.
  • VM (Docker): When the deployment target is a VM server using Docker images.
  • N/A: When there is no deployment target (e.g., Android).
Template NameEnter the name of the App Template.
Application ClassificationSelect the classification of the application included in the template.
  • Used to classify templates.
LanguageSelect the development language of the source code included in the template.
Source CodeSelect whether the template includes source code.
Source Code Repository TypeSelect the location where the source code is stored. SCM or ZIP file selection is possible.
Repository URLEnter the URL of the repository where the template source code is located.
  • A list of SCM Repository tools available in the corresponding tenant or project group will appear.
Repository BranchEnter the branch of the repository where the template source code is located.
Individual AuthenticationEnter authentication information to access the repository.
  • If not used, the authentication information used when registering the tool will be used.
Dockerfile PathEnter the path to the Dockerfile in the repository.
  • Used for Docker image build.
Code QualitySelect whether to use code quality.
DescriptionWrite a description of the App Template.
Document URLEnter the URL of the document that explains the template.
  • It will appear as a link on the template selection page when creating a project.
Template IconSelect an icon to use for the template.
Build Result PathSpecify the build result path and file name.
Dockerfile TypeSelect the Dockerfile type.
  • You can choose to use the Dockerfile file in the source code or use the information registered in Managing Dockerfile Templates.
  • If you select the GUI template, the Dockerfile Template tab will be activated.
Table. Add App Template - Basic Information Input Items
Note

If the deployment target of the App Template is Kubernetes, the Supported Helm Chart step is added.

  • Select the Helm chart that can be used when deploying using this App Template.
  • You can select the Helm chart list by checking the checkbox and using the Add and Delete buttons in the middle.
Warning
App Templates cannot be used immediately after registration and require additional settings.
Refer to Adding Pipeline Templates and modify the usage to Yes by referring to Modifying Supported Tenant Information.

Modifying App Template Basic Information

To modify the basic information of an App Template, follow these steps:

  1. App Template page, click the item you want to modify. Move to the App Template Details page.
  2. App Template Details page, click the Basic Information tab.
  3. Basic Information tab, click the Modify button.
  4. Modify the necessary information and click the Save button.
Note
If a pipeline template is not registered, a Notification popup will appear.

Managing Pipeline Templates

Pipeline templates are settings for building pipelines that are automatically configured when a user creates a project using an App Template.

Warning
If a pipeline template is not registered, the App Template cannot be used.

Adding Pipeline Templates

To add a pipeline template, follow these steps:

  1. App Template page, click the item you want to add. Move to the App Template Details page.
  2. App Template Details page, click the Pipeline Template tab.
  3. Pipeline Template tab, click the Add button. Move to the Add Pipeline Template page.
  4. Add Pipeline Template page, enter the necessary information and click the Save button.
ItemDescription
Template NameEnter the name of the pipeline template.
Default Template
  • The default template is used for pipeline configuration when creating a project.
  • If a default template is not registered, it will be automatically set to ON and cannot be changed.
Supported JenkinsSelect the Jenkins that supports this pipeline template.
  • A list of CICD pipeline tools available in the corresponding tenant or project group will appear.
  • Required to refer to the necessary information in the Tools area when configuring the stage.
Environment VariableEnter environment variable information.
StageEnter each stage information.
Table. Add Pipeline Template Input Items
Note
For explanations and writing methods of Jenkins environment variables, refer to the official website.

Modifying Pipeline Templates

To modify a pipeline template, follow these steps:

  1. App Template page, click the item you want to modify. Move to the App Template Details page.
  2. App Template Details page, click the Pipeline Template tab.
  3. Pipeline Template tab, click the item you want to modify. Move to the Pipeline Template Details page.
  4. Pipeline Template Details page, click the Modify button. Move to the Modify Pipeline Template page.
  5. Modify Pipeline Template page, modify the information and click the Save button.

Deleting Pipeline Templates

Warning
Pipeline templates marked as Default cannot be deleted.

To delete a pipeline template, follow these steps:

  1. App Template page, click the item you want to delete. Move to the App Template Details page.
  2. App Template Details page, click the Pipeline Template tab.
  3. Pipeline Template tab, click the item you want to delete. Move to the Pipeline Template Details page.
  4. Pipeline Template Details page, click the Delete button.
  5. Click the Confirm button in the confirmation popup.

Managing Dockerfile Templates

This tab only appears when the Dockerfile Type item in the Basic Information content of the App Template is GUI Template.

Modifying Dockerfile Templates

To modify a Dockerfile template, follow these steps:

  1. App Template page, click the item you want to modify. Move to the App Template Details page.
  2. App Template Details page, click the Dockerfile Template tab.
  3. Dockerfile Template tab, click the Modify or Create button.
  4. Dockerfile Template tab, enter the contents and click the Save button.
ItemDescription
Authentication Information SettingRegister authentication information for the image used in the FROM clause of the multi-stage build.
AddAdd an image used in the FROM clause of the multi-stage build.
Multi-stage DockerfileConfigure the multi-stage build based on the registered information.
DockerfileConfigure the basic Dockerfile.
Table. Modify Dockerfile Template Input Items
Guide

You can also manage the Dockerfile without registering it through Dockerfile in the source code.

  • If you use the Dockerfile file included in the source code, the Dockerfile Type item in the Basic Information content of the App Template must be set to Code Repository File.

The FROM clause is automatically set to the image path registered in Managing Supported Images.

Note
For explanations and writing methods of Dockerfile files, refer to the official website.

Managing Supported Tenants/Project Groups

Guide

The tab name is displayed differently depending on the template type.

  • System Template/Tenant Template: Supported Tenants
  • ProjectGroup Template: Supported Information

Users can manage the tenants or project groups where the App Template can be used.

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

  1. App Template page, click the item you want to modify. Move to the App Template Details page.
  2. App Template Details page, click the Supported Tenants or Supported Information tab.
Note
The primary icon appears for the managed tenant.

Adding Supported Tenants

To add supported tenants, follow these steps:

  1. App Template page, click the item you want to modify. Move to the App Template Details page.
  2. App Template Details page, click the Supported Tenants tab.
  3. Supported Tenants tab, click the Add button. The Add Tenant popup will appear.
  4. Add Tenant popup, select the tenant to support and click the Save button.

Modifying Supported Tenant Information

To modify the information of supported tenants, follow these steps:

  1. App Template page, click the item you want to modify. Move to the App Template Details page.
  2. App Template Details page, click the Supported Tenants tab.
  3. Supported Tenants tab, select the tenant to modify and select the Verification and Usage items to modify.
ItemDescription
TenantInformation about the available tenant.
VerificationSelect the verification.
  • Verification in progress
  • Verification completed
UsageSelect the usage.
  • Verification must be Verification completed to change to Usage.
Table. Supported Tenants Screen Items
Note

If the Verification is Verification in progress, only the user who registered the App Template can use it.

  • Other users can use the App template after verification and usage processing.

Modifying Supported Project Group Information

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

  1. App Template page, click the item you want to modify. Move to the App Template Details page. App Template Details page, click the Support Information tab.
  2. Support Information tab, click the Modify button. The App Template Modification screen appears.
  3. App Template Modification screen, select and modify the Verification and Usage items.
  4. Click the Save button.
ItemDescription
Project GroupInformation about the available project group.
VerificationSelect the verification.
  • Verifying
  • Verification Complete
UsageSelect the usage.
  • Verification must be Verification Complete to change to Use.
Table. Support Information Screen Items
Note

If the verification is in progress, only the user who registered the App template can use it.

  • Other users can use the App template after verification and usage processing.

Transferring Management Tenant

To transfer the management tenant, follow these steps:

  1. App Template page, click the item you want to modify. Move to the App Template Details page.
  2. App Template Details page, click the Support Tenant tab.
  3. Support Tenant tab, click the Transfer Management Tenant button. The Transfer Management Tenant popup window opens.
  4. Transfer Management Tenant popup window, select the target tenant to transfer and click the Save button.

Deleting Support Tenant

To delete a support tenant, follow these steps:

  1. App Template page, click the item you want to modify. Move to the App Template Details page.
  2. App Template Details page, click the Support Tenant tab.
  3. Support Tenant tab, select the tenant to delete and click the Delete button.
  4. Click the Confirm button in the confirmation popup window.
Caution
Primary designated tenants cannot be deleted.

Managing Support Images

Guide
The Support Image tab only appears when the deployment target of the App template is Kubernetes or VM(Docker).

The Support Image registered by the user is used in the Dockerfile or Dockerfile template of the source code.

Adding Support Images

Guide
When adding support images, only Image Registry Tools available in the tenant and project group are listed.

To add a support image, follow these steps:

  1. App Template page, click the item you want to modify. Move to the App Template Details page.
  2. App Template Details page, click the Support Image tab.
  3. Support Image tab, click the Add button. The Add Support Image popup window opens.
  4. Add Support Image popup window, enter the information and click the Connection Test button.
  5. When the Save button is activated, click the Save button.
  6. Click the Confirm button in the confirmation popup window.
ItemDescription
Image Information InputEnter the support image and authentication information.
Use Registrar’s Authentication InformationAn option that can be selected when the selected image storage tool cannot grant permissions (e.g., SCR).
  • If not checked, the support image user will be added to the pull permission of the entered image when creating a project. If the tool cannot grant permissions, the permissions will not be granted.
  • If checked, the support image user’s authority is used instead of the support image registrar’s authentication information when creating a project.
Table. Support Image Addition Input Items
Caution

Precautions for using the registrar’s authentication information

  • Be careful when using this option, as the registrar’s authentication information may be exposed to the support image user.
  • This option should only be used when necessary, and only for image storage that provides pull-only functionality. (If checked, one image storage cannot be used for both pull and push at the same time.)
  • The registrar’s authentication information is used in the project > image storage > pull-only image. This information cannot be changed by the support image user, and if the registrar’s authentication information is re-registered in the support image, it will be changed collectively.

Deleting Support Images

To delete a support image, follow these steps:

  1. App Template page, click the item you want to modify. Move to the App Template Details page.
  2. App Template Details page, click the Support Image tab.
  3. Support Image tab, select the checkbox of the item to delete and click the Delete button.
  4. Click the Confirm button in the confirmation popup window.

Managing Support Helm Charts

Guide
The Support Helm Chart tab is only exposed when the deployment target of the App template is Kubernetes.
Refer to Adding Helm Charts for support helm chart registration.

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

Adding Support Helm Charts

To add a support helm chart, follow these steps:

  1. App Template page, click the item you want to modify. Move to the App Template Details page.
  2. App Template Details page, click the Support Helm Chart tab.
  3. Support Helm Chart tab, click the Modify button. The App Template Modification screen appears.
  4. App Template Modification screen, select the checkbox of the helm chart to use in the Helm Chart List, and click the Add button to add it to the Selected Helm Chart List, then click the Save button.

Modifying Support Helm Charts

To modify a support helm chart, follow these steps:

  1. App Template page, click the item you want to modify. Move to the App Template Details page.
  2. App Template Details page, click the Support Helm Chart tab.
  3. Support Helm Chart tab, click the Modify button. The App Template Modification screen appears.
  4. App Template Modification screen, select the checkbox of the helm chart to use in the Helm Chart List, and click the Add or Delete button to modify the Selected Helm Chart List, then click the Save button.

Deleting Support Helm Charts

To delete a support helm chart, follow these steps:

  1. App Template page, click the item you want to modify. Move to the App Template Details page.
  2. App Template Details page, click the Support Helm Chart tab.
  3. Support Helm Chart tab, click the Modify button. The App Template Modification screen appears.
  4. App Template Modification screen, select the checkbox of the helm chart to delete in the Selected Helm Chart List, and click the Delete button to delete it, then click the Save button.

Deleting App Templates

To delete an App template, follow these steps:

  1. App Template page, click the item you want to delete. Move to the App Template Details page.
  2. App Template Details page, click the Basic Information tab.
  3. Basic Information tab, click the Delete button.
  4. Click the Confirm button in the confirmation popup window.

3 - Register user-installed Jenkins tool

Reference
  • For installing and operating Jenkins, it is recommended to use the Samsung Cloud Platform Marketplace.
  • If you cannot use the marketplace or want to register a self-installed Jenkins as a tool in DevOps Console, use this document.
  • This document is a guide for registering the Jenkins tool in DevOps Console, so it briefly explains Jenkins installation and operation.

Start registering Jenkins tool for user installation

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 domain for Jenkins access
  • Jenkins domain registered in DNS
  • Jenkins communication with HTTPS (port 443), use public certificate

Installation

Install Jenkins on a VM or Kubernetes.

Plugin Installation

Install the following plugin in Jenkins.

Plugin IDName
apache-httpcomponents-client-4-apiApache HttpComponents Client 4.x API
credentialsCredentials
credentials-bindingCredentials Binding
githubGitHub
jobConfigHistoryJob Configuration History
kubernetesKubernetes
mask-passwordsMask Passwords
maven-pluginMaven Integration
matrix-authMatrix Authorization Strategy
metricsMetrics
pipeline-stage-viewPipeline: Stage View
pipeline-utility-stepsPipeline Utility Steps
script-securityScript Security
ssh-stepsSSH Pipeline Steps
workflow-aggregatorPipeline
workflow-step-apiPipeline: Step API
Table. Installed plugin list
Reference
https://plugins.jenkins.io/{Plugin ID} you can view detailed plugin information.

Jenkins Settings

Common Settings

Jenkins Management > System

ItemValueDescription
# of executors0Set to 0 to restrict direct build execution on the Controller and allow builds only on Agents
Jenkins URL(ex) https://{YOUR_DOMAIN}/jenkins/
System Admin e-mail address(ex) admin@example.com
Table. Jenkins Management > System Settings

Jenkins Management > Security

ItemValueDescription
AuthorizationProject-based Matrix Authorization Strategy
Authenticated UsersOverall > Read
<ADMIN_USER>Overall > AdministerAdd admin account using Add user
Table. Jenkins Management > Security Settings

Support email format for Jenkins Username

  • By default, Jenkins does not allow the @ symbol (.) to be used in the login Username. However, since DevOps Console uses email as the Username, we configure Jenkins to allow using email as the Username as well.
  • /{JENKINS_HOME}/init.groovy.d/init.groovy Create the file, enter the following contents, and restart Jenkins.
    • (ex) /var/jenkins_home/init.groovy.d/init.groovy
Color mode
hudson.security.HudsonPrivateSecurityRealm.ID_REGEX=/^[\w-\.\@\_]+$/
hudson.security.HudsonPrivateSecurityRealm.ID_REGEX=/^[\w-\.\@\_]+$/
Code block. init.groovy

Additional Jenkins configuration installed on Kubernetes

RBAC

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

Color mode
# 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
Code block. service-account.yml

Jenkins Management > Clouds

kubernetes

  • kubernetes add the cloud.
  • kubernetes set the cloud as follows. Use the default values for the remaining items.
ItemValueDescription
Cloud namekubernetes
TypeKubernetes selection
Kubernetes URLhttps://kubernetes.defaultCreate a Pod (Agent) in the cluster where Jenkins is running
Disable https certificateCheck
Kubernetes Namespace(example) jenkinsEnter the Namespace where the Jenkins Controller is running, a Pod (Agent) will be created in that Namespace
WebSocketcheck
Jenkins URL(example) http://{JENKINS_SERVICE_NAME}:{PORT}/jenkins
  • Jenkins URL used when calling Pod(Agent) → Pod(Controller)
  • Since it is called within the same Namespace, use the Kubernetes Service Name
Table. Jenkins Management > Clouds > kubernetes Settings

kubernetes > Pod Templates

  • Add a Pod Template.
  • BASE-TEMPLATE is a higher-level template used in the DevOps Console that sets values that must be commonly used in each Pod Template.
ItemValueDescription
NameBASE-TEMPLATE
Image Pull Secret{IMAGE_PULL_SECRET} Enter nameCreate a Secret in the Namespace so that the Pod (Agent) image can be pulled, and enter its name
Table. Jenkins Management > Clouds > kubernetes > Pod Templates Settings

Register Jenkins tool in DevOps Console

Register firewall

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

OriginDestinationDestination Port
User Install JenkinsDevOps Console Web443
DevOps Console Source IPUser-installed Jenkins web443
Table. Jenkins (Destination) Firewall List
Reference
To check the source IP of DevOps Console, click the URL ⓘ on the tool addition screen. You can check the source IP of DevOps Console in the tooltip.

DevOps Console Task

  • For detailed information related to Jenkins tool registration, please refer to Add Tool.
  • In the tool registration step, check the plugins installed in Jenkins, and if there are plugins that need to be installed, a plugin installation guide page will be displayed. Download and install the plugins as instructed.

Jenkins Check

Jenkins Management > System

Global Trusted Pipeline Libraries

  • Check if cicdpaas is set in the Library.
  • If it is not set
    • DevOps Console ↔ Jenkins Check the communication status.
    • DevOps Console > Management > Jenkins detail screen > Check the settings in the Global Library tab.

DevOps Console Credentials

  • Test Connection Click the button to verify that Success is displayed.

Add agent (VM) to Jenkins

DevOps Console Task

Check Add Agent (VM) and add the agent (VM).

Jenkins job

Jenkins Management > Nodes > Agent Detail Screen

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

Add agent (Kubernetes) to Jenkins

Before adding the agent (Kubernetes)

User Jenkins agent image creation

  • An agent image is required for CI/CD in Jenkins.
  • Use the default images provided by Jenkins to create a Jenkins agent image that fits the user.
  • After generating the image, push it to the user image repository.
Color mode
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
Code block. Dockerfile example

Docker in Docker image

  • DevOps Console uses Docker in Docker to generate Docker images in a Kubernetes environment.
  • Push the docker:dind (Docker in Docker) image provided by Docker to your repository.

DevOps Console Task

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

Jenkins job

Jenkins Management > Clouds > kubernetes > Pod Templates

  • The agent (Kubernetes) added from DevOps Console is registered as a Pod Template.
  • If you selected Docker in Docker in the DevOps Console, the dind container has the default image address entered. Change to the docker:dind image address you pushed to your user repository.