This is the multi-page printable view of this section. Click here to print.
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:
- Main page, click the Manage icon in the top right corner. You will be taken to the Tenant Dashboard page.
- 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 Type | Description |
|---|---|
| System Tool |
|
| Tenant Tool |
|
| ProjectGroup Tool |
|
Tool Classification
The following is a list of tools currently supported by the DevOps Console:
| Tool Classification | Tool |
|---|---|
| CICD Pipeline | Jenkins |
| SCM Repository | GitLab, GitHub, Git-based SCM |
| Image Registry | Harbor, Docker Hub, SCP Container Registry, Docker Image Registry |
| Code Quality | SonarQube |
| Artifact Repository | Nexus, Object Storage (S3 compatible) |
| Helm Chart Repository | Harbor |
| Project Management Software | JIRA |
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:
Management affiliation is a tenant.
Management affiliation is a project group.
Adding a Tool
To add a tool, follow these steps:
- On the Tools page, click the Add button. The Add Tool popup window will open.
Selecting Tool Support Type
- In the Add Tool popup window, select the tool’s support type.
- Complete the selection and click the Next button. The Basic Information input screen will appear.
| Item | Description |
|---|---|
| Type | Select the tool’s support type.
|
| Tenant/Project Group | Select which tenant or project group to map to. |
Entering Basic Information
- 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.
- See Tool Classification for classification descriptions.
- Enter the necessary information and click the Connection Test button.
- Click the Next button.
SCM Repository
| Item | Description |
|---|---|
| Tool Name | Enter a tool name for user identification. |
| Tool Classification | Select the tool classification. |
| Tool | Select the tool. |
| URL | Enter the URL address to access the tool.
|
| URL for API | Enter the Github.com API path. |
| Org Creation Possible | Select whether to allow creation of new Github Organizations in the tenant or project group. |
| New Creation Possible | Select whether to allow creation of new repositories in the tenant or project group. |
| IDP Usage | Select whether to use IDP. |
| User Account Authentication Type | Select the authentication type for tool users. |
| Admin Account Authentication Type | Select the authentication type for tool administrators. |
| Admin ID | Enter the admin ID for the tool. |
| Admin Password / Token | Enter the admin password or token for the tool. |
CICD Pipeline
| Item | Description |
|---|---|
| Tool Name | Enter a tool name for user identification. |
| Tool Classification | Select the tool classification. |
| Tool | Select the tool. |
| URL | Enter the URL address to access the tool.
|
| Mail Service | Select whether to use the email sending feature. |
| Type | Select whether to use the tool for development or operation. |
| IP | Enter the IP list.
|
| IP Range | Enter the IP range.
|
| IDP Usage | Select whether to use IDP. |
| IDP Type | If using IDP, select the IDP type (CMP IDP, other IDP). |
| User Account Authentication Type | Select the authentication type for tool users. |
| Admin Account Authentication Type | Select the authentication type for tool administrators. |
| Admin ID | Enter the admin ID for the tool. |
| Admin Password / Token | Enter the admin password or token for the tool. |
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.
- The Number of executors item in the Built-In Node must be set to 0 in the Jenkins management menu.
- Note Jenkins officially recommends avoiding build execution on the Controller Node.
Image Registry
| Item | Description |
|---|---|
| Tool Name | Enter a tool name for user identification. |
| Tool Classification | Select the tool classification. |
| Tool | Select the tool. |
| New Creation Possible | Select whether to allow creation of new repositories in the tenant or project group. |
| URL | Enter the URL address to access the tool.
|
| URL for API | Enter the Docker Hub API path. |
| Image Repository URL | Enter the URL for Docker Registry use. |
| Private SSL Certificate Usage | Select whether to use a private SSL certificate. |
| System Common Image Inclusion | Select whether to include system common images. |
| IDP Usage | Select whether to use IDP. |
| User Account Authentication Type | Select the authentication type for tool users. |
| Admin Account Authentication Type | Select the authentication type for tool administrators. |
| Admin ID | Enter the admin ID for the tool. |
| Admin Password / Token | Enter the admin password or token for the tool. |
Code Quality
| Item | Description |
|---|---|
| Tool Name | Enter a tool name for user identification. |
| Tool Classification | Select the tool classification. |
| Tool | Select the tool. |
| New Creation Possible | Select whether to allow creation of new SonarQube projects in the tenant or project group. |
| URL | Enter the URL address to access the tool.
|
| Tool Version | Enter the SonarQube version. |
| IDP Usage | Select whether to use IDP. |
| User Account Authentication Type | Select the authentication type for tool users. |
| Admin Account Authentication Type | Select the authentication type for tool administrators. |
| Admin ID | Enter the admin ID for the tool. |
| Admin Password / Token | Enter the admin password or token for the tool. |
Artifact Repository
| Item | Description |
|---|---|
| Tool Name | Enter a tool name for user identification. |
| Tool Classification | Select the tool classification. |
| Tool | Select the tool. |
| New Creation Possible | Select whether to allow creation of new Nexus repositories in the tenant or project group. |
| URL | Enter the URL address to access the tool.
|
| IDP Usage | Select whether to use IDP. |
| User Account Authentication Type | Select the authentication type for tool users. |
| Admin Account Authentication Type | Select the authentication type for tool administrators. |
| Admin ID | Enter the admin ID for the tool. |
| Admin Password / Token | Enter the admin password or token for the tool. |
Helm Chart Repository
| Item | Description |
|---|---|
| Tool Name | Enter a tool name for user identification. |
| Tool Classification | Select the tool classification. |
| Tool | Select the tool. |
| New Creation Possible | Select whether to allow creation of new repositories in the tenant or project group. |
| URL | Enter the URL address to access the tool.
|
| Private SSL Certificate Usage | Select whether to use a private SSL certificate. |
| Helm Chart Repository URL | Enter the repository URL for the tool.
|
| IDP Usage | Select whether to use IDP. |
| User Account Authentication Type | Select the authentication type for tool users. |
| Admin Account Authentication Type | Select the authentication type for tool administrators. |
| Admin ID | Enter the admin ID for the tool. |
| Admin Password / Token | Enter the admin password or token for the tool. |
Project Management Software
| Item | Description |
|---|---|
| Tool Name | Enter a tool name for user identification. |
| Tool Classification | Select the tool classification. |
| Tool | Select the tool. |
| New Creation Possible | Select whether to allow creation of new JIRA projects in the tenant or project group. |
| URL | Enter the URL address to access the tool.
|
| IDP Usage | Select whether to use IDP. |
| User Account Authentication Type | Select the authentication type for tool users. |
| Admin Account Authentication Type | Select the authentication type for tool administrators. |
| Admin ID | Enter the admin ID for the tool. |
| Admin Password / Token | Enter the admin password or token for the tool. |
Entering Additional Information
- On the Add Tool popup window, on the Basic Information input screen, click the Next button. The Additional Information input screen will appear.
- Select each item and click the Complete button.
- In the confirmation popup window, click the Confirm button to complete the tool addition.
| Item | Description |
|---|---|
| Usage | Select whether to use the tool in the tenant or project group. |
| New Creation Possible | Select whether to allow creation of new repositories in the tenant or project group.
|
Tool Details
To manage tool details, follow these steps:
- 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:
- On the Tool Details page, click the Basic Information tab.
To modify the tool’s basic information, follow these steps:
- On the Tool Details page, click the Basic Information tab.
- Click the Modify button.
- Modify the necessary information and click the Save button.
Managing Global Tools
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:
- Click the Global Tool tab on the Tool Details page.
Adding Global Tools
To add a global tool, follow these steps:
- 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.
- Click the Add button. A new row will be added to the bottom of the list.
- Enter the information in the new row and click the Save button.
- Click the Confirm button in the confirmation popup window to complete the process.
| Item | Description |
|---|---|
| Tool Type | The tool type is automatically set. |
| Name | Enter the tool name. |
| Home Path | Enter the path where the tool is installed. |
Modifying Global Tools
To modify a global tool, follow these steps:
- Click the Edit icon for the item you want to modify. The Global Tool Management popup window will open.
- Modify the content and click the Save button.
- Click the Confirm button in the confirmation popup window to complete the modification.
Deleting Global Tools
To delete a global tool, follow these steps:
- 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.
- Delete the content and click the Save button.
- Click the Confirm button in the confirmation popup window to complete the deletion.
Managing Agent (Kubernetes)
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:
- Click the Agent (Kubernetes) tab on the Tool Details page.
- Click the Information icon in the Pod Template Management list. The Pod Template Usage Guide popup window will open.
Adding Container Resource Types
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:
- Click the Agent (Kubernetes) tab on the Tool Details page.
- Click the Edit icon in the Container Resource Type Management section. The Container Resource Type Management popup window will open.
- Click the Add button and enter the content. Click the Save button.
- Click the Confirm button in the confirmation popup window to complete the process.
| Item | Description |
|---|---|
| Usage | Set the usage.
|
| Resource Type | Enter 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. |
Modifying Container Resource Types
To modify a container resource type, follow these steps:
- Click the Agent (Kubernetes) tab on the Tool Details page.
- Click the Edit icon in the Container Resource Type Management section. The Container Resource Type Management popup window will open.
- Modify the content and click the Save button.
- 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:
- Click the Agent (Kubernetes) tab on the Tool Details page.
- Click the Edit icon in the Container Resource Type Management section. The Container Resource Type Management popup window will open.
- Delete the content and click the Save button.
- Click the Confirm button in the confirmation popup window to complete the deletion.
Adding Pod Templates
To add a Pod Template, follow these steps:
- Click the Agent (Kubernetes) tab on the Tool Details page.
- Click the Add button in the Pod Template Management list. The Add Agent (Kubernetes) screen will appear.
- Enter the content and click the Save button.
- Click the Confirm button in the confirmation popup window to complete the process.
| Item | Description |
|---|---|
| Target Kubernetes | Select the target Kubernetes to add the Pod Template.
|
| Agent Name | Enter the name of the Pod Template. |
| Label | Enter the label value to call the corresponding agent in the Jenkins Pipeline Script. |
| Inherit Pod Template | Select the Pod Template to inherit the settings (environment variables, volumes, etc.).
|
| Container | Enter the information mapped to the Container Template item in Jenkins, such as name, Docker image, working directory, command, and arguments.
|
| Tool Path | Enter the information mapped to the Tool Locations item in Jenkins, such as name and home path.
|
| Supported Stage | Select the supported stage configuration.
|
If the user does not check Docker Build in the Supported Stage item,
- The corresponding
Jenkinscannot 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:
- Click the Agent (Kubernetes) tab on the Tool Details page.
- 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:
- Click the Agent (Kubernetes) tab on the Tool Details page.
- 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.
- Click the Modify button.
- Modify the content and click the Save button.
- Click the Confirm button in the confirmation popup window to complete the modification.
Deleting Pod Templates
To delete a Pod Template, follow these steps:
- Click the Agent (Kubernetes) tab on the Tool Details page.
- 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.
- Click the Delete button.
- Click the Confirm button in the confirmation popup window to complete the deletion.
Managing Agent (VM)
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:
- Click the Agent (VM) tab on the Tool Details page.
- 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:
- Click the Agent (VM) tab on the Tool Details page.
- Click the Edit icon in the Agent Connection Management section. The Agent Connection Management popup window will open.
- Enter the content and click the Save button.
Adding Agent (VM)
To add an agent (VM), follow these steps:
- Click the Agent (VM) tab on the Tool Details page.
- Click the Add button in the Agent Connection Management section. The Add Agent (VM) screen will appear.
- Enter the content and click the Save button.
- Click the Confirm button in the confirmation popup window to complete the process.
| Item | Description |
|---|---|
| Target OS | Enter the OS information of the VM. |
| Agent Name | Enter the name of the VM. |
| Remote Root Directory | Enter the directory path. |
| Label | Enter the label value to call the corresponding agent in the Jenkins Pipeline Script. |
| Tool Path | Enter the information mapped to the Tool Locations item in Jenkins, such as name and home path.
|
| Supported Stage | Select the supported stage configuration.
|
If the user does not check Docker Build in the Supported Stage item,
- The corresponding
Jenkinscannot 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:
- Click the Agent (VM) tab on the Tool Details page.
- Click the agent you want to view in the Node Management list. The Agent (VM) Details screen will appear.
- Click the Information icon in the Jenkins - Agent Connection Information section.
- The Agent Connection Guide popup window will open.
Connecting Agent (VM)
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:
- Click the Agent (VM) tab on the Tool Details page.
- Click the agent you want to connect in the Node Management list. The Agent (VM) Details screen will appear.
- Refer to
jnlpUrlandsecret. - Click the Information icon in the Jenkins - Agent Connection Information section. The Agent Connection Guide popup window will open.
- Click the Download Agent File button to download the
agent.jarfile.- The
agent.jarversion may cause issues with execution. - You can also download it directly from your
Jenkins({JENKINS_URL}/jnlpJars/agent.jar).
- The
- Connect to the VM server where you want to deploy and create a directory.
- Copy the downloaded
agent.jarfile to the created directory. - Run the following command in the created directory path:
java -jar agent.jar -jnlpUrl {jnlpUrl} -secret {secret}java -jar agent.jar -jnlpUrl {jnlpUrl} -secret {secret}Modifying Agent (VM)
To modify an agent (VM), follow these steps:
- Click the Agent (VM) tab on the Tool Details page.
- Click the agent you want to modify in the Node Management list. The Agent (VM) Details screen will appear.
- Click the Modify button.
- Modify the content and click the Save button.
- Click the Confirm button in the confirmation popup window to complete the modification.
Deleting Agent (VM)
To delete an agent (VM), follow these steps:
- Click the Agent (VM) tab on the Tool Details page.
- Click the agent you want to delete in the Node Management list. The Agent (VM) Details screen will appear.
- Click the Delete button.
- 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:
- Tool Details page, click the Global Library tab.
Adding Global Libraries
To add a global library, follow these steps:
- Tool Details page, click the Global Library tab.
- Click the Add button. The Add Global Library screen appears.
- Enter the contents and click the Save button.
- In the confirmation popup, click the Confirm button to complete.
| Item | Description |
|---|---|
| Library Name | Enter the name of the library. |
| Type | Fixed as SCM and cannot be changed. |
| Library URL | Enter the Git repository URL where the library exists. |
| Default Version | Enter the branch name or tag of the Git repository where the library exists. |
| ID | Enter the ID for pulling the library. |
| Password | Enter the password for pulling the library. |
Viewing Global Library Details
To view the details of a global library, follow these steps:
- Tool Details page, click the Global Library tab.
- In the Global Library list, click the item you want to view in detail. The Global Library Details screen appears.
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:
- Tool Details page, click the Global Library tab.
- In the Global Library list, click the item you want to view in detail. The Global Library Details screen appears.
- Click the Modify button.
- Modify the contents and click the Save button.
- In the confirmation popup, click the Confirm button to complete.
Deleting Global Libraries
To delete a global library, follow these steps:
- Tool Details page, click the Global Library tab.
- In the Global Library list, click the item you want to delete. The Global Library Details screen appears.
- Click the Delete button.
- In the confirmation popup, click the Confirm button to complete.
Managing Supported Tenants/Project Groups
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:
- Tool Details page, click the Supported Tenants or Supported Information tab.
Adding Supported Tenants/Project Groups
To add a supported tenant or project group, follow these steps:
- Tool Details page, click the Supported Tenants or Supported Information tab.
- Click the Add button. The Add Tenant/Project Group popup window opens.
- Enter the contents and click the Save button.
- In the confirmation popup, click the Confirm button to complete.
| Item | Description |
|---|---|
| Tenant/Project Group | Select the tenant/project group that can use the tool. |
| Usage | Select whether to use the tool in the tenant/project group. |
| New Creation Possible | Select whether to allow new repository creation in the tenant/project group. This setting is only available for the following tool categories:
|
Modifying Supported Tenants/Project Groups
To modify a supported tenant/project group, follow these steps:
- Tool Details page, click the Supported Tenants or Supported Information tab.
- 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:
- Tool Details page, click the Supported Tenants or Supported Information tab.
- Click the Transfer Management Tenant or Transfer Management Project Group button. The Transfer Management Tenant or Transfer Management Project Group popup window opens.
- 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:
- Tool Details page, click the Supported Tenants or Supported Information tab.
- Select the checkbox of the tenant/project group you want to delete.
- Click the Delete button.
- In the confirmation popup, click the Confirm button to complete.
Managing Supported K8S Clusters
Users can manage the K8S clusters that can use the tool.
To manage supported K8S clusters, follow these steps:
- Tool Details page, click the Supported K8S Clusters tab.
Adding Supported K8S Clusters
To add a supported K8S cluster, follow these steps:
- Tool Details page, click the Supported K8S Clusters tab.
- Click the Add button. The Add K8S Cluster popup window opens.
- Enter the contents and click the Save button.
- In the confirmation popup, click the Confirm button to complete.
| Item | Description |
|---|---|
| K8S Cluster | Select the K8S cluster that can use the tool. |
| Usage | Select whether to use the tool in the tenant/project group. |
| New Creation Possible | Select whether to allow new repository creation in the tenant/project group. This setting is only available for the following tool categories:
|
Modifying Supported K8S Clusters
To modify a supported K8S cluster, follow these steps:
- Tool Details page, click the Supported K8S Clusters tab.
- 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:
- Tool Details page, click the Supported K8S Clusters tab.
- Select the checkbox of the K8S cluster you want to delete.
- Click the Delete button.
- In the confirmation popup, click the Confirm button to complete.
Managing Tool Operators
To manage tool operators, follow these steps:
- Tool Details page, click the Tool Operator tab.
Adding Tool Operators
To add a tool operator, follow these steps:
- Tool Details page, click the Tool Operator tab.
- Click the Add button. The Add Tool Operator popup window opens.
- Select the operator and click the Save button.
- In the confirmation popup, click the Confirm button to complete.
Deleting Tool Operators
To delete a tool operator, follow these steps:
- Tool Details page, click the Tool Operator tab.
- Select the checkbox of the operator you want to delete.
- Click the Delete button.
- In the confirmation popup, click the Confirm button to complete.
Managing Jenkins Recommended Plugins
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
Checking Tool Version and Recommended Plugins Information
To view the tool version and required plugin information, follow these steps:
- Click Tool(CICD Pipeline) on the Tool Management page.
- 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.
- On the Tool Details page, click the Plugins tab.
- View the Tool Version and Recommended Plugins items.
Installing Recommended Plugins
Follow this procedure to install recommended plugins.
- On the Plugins page, Click Install button which you want to install plugin in Recommended Plugins area.
- Install Recommended Plugin popup is occured, and click Confirm button.
- Then popup appears message that installation request has been completed, and you can check the actual installation through the link in the popup.
Updating Recommended Plugins
Follow this procedure to update recommended plugins.
- On the Plugins page, Click Update button which you want to install plugin in Recommended Plugins area.
- Update Recommended Plugin popup is occured, and click Confirm button.
- Then popup appears message that update request has been completed, and you can check the actual installation through the link in the popup.
- You must restart your Jenkins to apply the update.
Deleting Tools
To delete a tool, follow these steps:
- Tool page, click the tool you want to delete. The Tool Details page opens.
- Click the Delete button.
- 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 Type | Description |
|---|---|
| System Template |
|
| Tenant Template |
|
| ProjectGroup Template |
|
Getting Started with App Template
To start managing App Templates, follow these steps:
- Main page, click the Manage icon at the top right. Move to the Tenant Dashboard page.
- 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
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
FROM ${BASE_IMAGE}
COPY *.jar app.jar
ENTRYPOINT ["java","-jar","/app.jar"]FROM ${BASE_IMAGE}
COPY *.jar app.jar
ENTRYPOINT ["java","-jar","/app.jar"]Registering App Template
To register an App Template, follow these steps:
- App Template page, click the Add button. Move to the Add App Template page.
- Add App Template page, select the template support type and click the Start button.
- Enter the necessary information and click the Complete button.
| Item | Description |
|---|---|
| Type | Select the type of template.
|
| Tenant/Project Group | Select the tenant or project group to map. |
| Item | Description |
|---|---|
| Deployment Target | Select the deployment target supported by the template.
|
| Template Name | Enter the name of the App Template. |
| Application Classification | Select the classification of the application included in the template.
|
| Language | Select the development 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 is stored. SCM or ZIP file selection is possible. |
| Repository URL | Enter the URL of the repository where the template source code is located.
|
| Repository Branch | Enter the branch of the repository where the template source code is located. |
| Individual Authentication | Enter authentication information to access the repository.
|
| Dockerfile Path | Enter the path to the Dockerfile in the repository.
|
| Code Quality | Select whether to use code quality. |
| Description | Write a description of the App Template. |
| Document URL | Enter the URL of the document that explains the template.
|
| Template Icon | Select an icon to use for the template. |
| Build Result Path | Specify the build result path and file name. |
| Dockerfile Type | Select the Dockerfile type.
|
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.
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:
- App Template page, click the item you want to modify. Move to the App Template Details page.
- App Template Details page, click the Basic Information tab.
- Basic Information tab, click the Modify button.
- Modify the necessary information and click the Save button.
Managing Pipeline Templates
Pipeline templates are settings for building pipelines that are automatically configured when a user creates a project using an App Template.
Adding Pipeline Templates
To add a pipeline template, follow these steps:
- App Template page, click the item you want to add. Move to the App Template Details page.
- App Template Details page, click the Pipeline Template tab.
- Pipeline Template tab, click the Add button. Move to the Add Pipeline Template page.
- Add Pipeline Template page, enter the necessary information and click the Save button.
| Item | Description |
|---|---|
| Template Name | Enter the name of the pipeline template. |
| Default Template |
|
| Supported Jenkins | Select the Jenkins that supports this pipeline template.
|
| Environment Variable | Enter environment variable information.
|
| Stage | Enter each stage information.
|
Jenkins environment variables, refer to the official website.Modifying Pipeline Templates
To modify a pipeline template, follow these steps:
- App Template page, click the item you want to modify. Move to the App Template Details page.
- App Template Details page, click the Pipeline Template tab.
- Pipeline Template tab, click the item you want to modify. Move to the Pipeline Template Details page.
- Pipeline Template Details page, click the Modify button. Move to the Modify Pipeline Template page.
- Modify Pipeline Template page, modify the information and click the Save button.
Deleting Pipeline Templates
To delete a pipeline template, follow these steps:
- App Template page, click the item you want to delete. Move to the App Template Details page.
- App Template Details page, click the Pipeline Template tab.
- Pipeline Template tab, click the item you want to delete. Move to the Pipeline Template Details page.
- Pipeline Template Details page, click the Delete button.
- 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:
- App Template page, click the item you want to modify. Move to the App Template Details page.
- App Template Details page, click the Dockerfile Template tab.
- Dockerfile Template tab, click the Modify or Create button.
- Dockerfile Template tab, enter the contents and click the Save button.
| Item | Description |
|---|---|
| Authentication Information Setting | Register authentication information for the image used in the FROM clause of the multi-stage build. |
| Add | Add an image used in the FROM clause of the multi-stage build. |
| Multi-stage Dockerfile | Configure the multi-stage build based on the registered information. |
| Dockerfile | Configure the basic Dockerfile. |
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.
Managing Supported Tenants/Project Groups
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:
- App Template page, click the item you want to modify. Move to the App Template Details page.
- App Template Details page, click the Supported Tenants or Supported Information tab.
Adding Supported Tenants
To add supported tenants, follow these steps:
- App Template page, click the item you want to modify. Move to the App Template Details page.
- App Template Details page, click the Supported Tenants tab.
- Supported Tenants tab, click the Add button. The Add Tenant popup will appear.
- 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:
- App Template page, click the item you want to modify. Move to the App Template Details page.
- App Template Details page, click the Supported Tenants tab.
- Supported Tenants tab, select the tenant to modify and select the Verification and Usage items to modify.
| Item | Description |
|---|---|
| Tenant | Information about the available tenant. |
| Verification | Select the verification.
|
| Usage | Select the usage.
|
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:
- 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.
- Support Information tab, click the Modify button. The App Template Modification screen appears.
- App Template Modification screen, select and modify the Verification and Usage items.
- Click the Save button.
| Item | Description |
|---|---|
| Project Group | Information about the available project group. |
| Verification | Select the verification.
|
| Usage | Select the usage.
|
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:
- App Template page, click the item you want to modify. Move to the App Template Details page.
- App Template Details page, click the Support Tenant tab.
- Support Tenant tab, click the Transfer Management Tenant button. The Transfer Management Tenant popup window opens.
- 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:
- App Template page, click the item you want to modify. Move to the App Template Details page.
- App Template Details page, click the Support Tenant tab.
- Support Tenant tab, select the tenant to delete and click the Delete button.
- Click the Confirm button in the confirmation popup window.
Managing Support Images
The Support Image registered by the user is used in the Dockerfile or Dockerfile template of the source code.
Adding Support Images
To add a support image, follow these steps:
- App Template page, click the item you want to modify. Move to the App Template Details page.
- App Template Details page, click the Support Image tab.
- Support Image tab, click the Add button. The Add Support Image popup window opens.
- Add Support Image popup window, enter the information and click the Connection Test button.
- When the Save button is activated, click the Save button.
- Click the Confirm button in the confirmation popup window.
| Item | Description |
|---|---|
| Image Information Input | Enter the support image and authentication information. |
| Use Registrar’s Authentication Information | An option that can be selected when the selected image storage tool cannot grant permissions (e.g., SCR).
|
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:
- App Template page, click the item you want to modify. Move to the App Template Details page.
- App Template Details page, click the Support Image tab.
- Support Image tab, select the checkbox of the item to delete and click the Delete button.
- Click the Confirm button in the confirmation popup window.
Managing Support Helm Charts
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:
- App Template page, click the item you want to modify. Move to the App Template Details page.
- App Template Details page, click the Support Helm Chart tab.
- Support Helm Chart tab, click the Modify button. The App Template Modification screen appears.
- 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:
- App Template page, click the item you want to modify. Move to the App Template Details page.
- App Template Details page, click the Support Helm Chart tab.
- Support Helm Chart tab, click the Modify button. The App Template Modification screen appears.
- 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:
- App Template page, click the item you want to modify. Move to the App Template Details page.
- App Template Details page, click the Support Helm Chart tab.
- Support Helm Chart tab, click the Modify button. The App Template Modification screen appears.
- 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:
- App Template page, click the item you want to delete. Move to the App Template Details page.
- App Template Details page, click the Basic Information tab.
- Basic Information tab, click the Delete button.
- Click the Confirm button in the confirmation popup window.
3 - Register user-installed Jenkins tool
- 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 ID | Name |
|---|---|
| apache-httpcomponents-client-4-api | Apache HttpComponents Client 4.x API |
| credentials | Credentials |
| credentials-binding | Credentials Binding |
| github | GitHub |
| jobConfigHistory | Job Configuration History |
| kubernetes | Kubernetes |
| mask-passwords | Mask Passwords |
| maven-plugin | Maven Integration |
| matrix-auth | Matrix Authorization Strategy |
| metrics | Metrics |
| pipeline-stage-view | Pipeline: Stage View |
| pipeline-utility-steps | Pipeline Utility Steps |
| script-security | Script Security |
| ssh-steps | SSH Pipeline Steps |
| workflow-aggregator | Pipeline |
| workflow-step-api | Pipeline: Step API |
Jenkins Settings
Common Settings
Jenkins Management > System
| Item | Value | Description |
|---|---|---|
| # of executors | 0 | Set 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 |
Jenkins Management > Security
| Item | Value | Description |
|---|---|---|
| Authorization | Project-based Matrix Authorization Strategy | |
| Authenticated Users | Overall > Read | |
| <ADMIN_USER> | Overall > Administer | Add admin account using Add user |
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.groovyCreate the file, enter the following contents, and restart Jenkins.- (ex)
/var/jenkins_home/init.groovy.d/init.groovy
- (ex)
hudson.security.HudsonPrivateSecurityRealm.ID_REGEX=/^[\w-\.\@\_]+$/hudson.security.HudsonPrivateSecurityRealm.ID_REGEX=/^[\w-\.\@\_]+$/Additional Jenkins configuration installed on Kubernetes
RBAC
Set 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: jenkinsJenkins Management > Clouds
kubernetes
- kubernetes add the cloud.
- kubernetes set the cloud as follows. Use the default values for the remaining items.
| Item | Value | Description |
|---|---|---|
| Cloud name | kubernetes | |
| Type | Kubernetes selection | |
| Kubernetes URL | https://kubernetes.default | Create a Pod (Agent) in the cluster where Jenkins is running |
| Disable https certificate | Check | |
| Kubernetes Namespace | (example) jenkins | Enter the Namespace where the Jenkins Controller is running, a Pod (Agent) will be created in that Namespace |
| WebSocket | check | |
| Jenkins URL | (example) http://{JENKINS_SERVICE_NAME}:{PORT}/jenkins |
|
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.
| Item | Value | Description |
|---|---|---|
| Name | BASE-TEMPLATE | |
| Image Pull Secret | {IMAGE_PULL_SECRET} Enter name | Create a Secret in the Namespace so that the Pod (Agent) image can be pulled, and enter its name |
Register Jenkins tool in DevOps Console
Register firewall
Refer to the table below and register the firewall in Jenkins.
| Origin | Destination | Destination Port |
|---|---|---|
| User Install Jenkins | DevOps Console Web | 443 |
| DevOps Console Source IP | User-installed Jenkins web | 443 |
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.
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 jenkinsFROM 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 jenkinsDocker 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.