The page has been translated by Gen AI.

Task

A task is the smallest executable unit that composes a workflow (or release), and each task can perform its designated operation.
A workflow (or release) consists of one or more tasks.

You can add and edit tasks from Release Management, Workflow Management.

Task List

The tasks provided in release management are as follows.

item
Explanation
JenkinsYou can run it by integrating with a Jenkins pipeline that belongs to the DevOps Console project or a Jenkins job that is separate from the DevOps Console project.
UserYou can register tasks that users perform manually, rather than integrating with a specific tool.
Blue/Green switchYou can integrate with Blue/Green deployments that belong to the DevOps Console project.
Internal approvalYou can approve through a USER belonging to the DevOps Console project group.
Helm releaseYou can integrate with Helm releases belonging to the DevOps Console project.
Image repository replicationYou can replicate the image to another repository.
SCM repository releaseRelease using the SCM repository’s release feature.
Create a Git branchYou can copy a specific branch of a repository belonging to the DevOps Console project and create a new branch.
JIRA releaseYou can release or unrelease a specific version in a JIRA project.
VM deploymentThis task can deploy a VM deployment group that is in the Build Completed state, or roll back to a previous version.
Table. Project Creation Basic Information Input Items

Common task items

You can add and edit tasks in workload (or release) management. When you select a task, the Task Edit screen appears, and the Task Edit screen is composed as follows.

ItemExplanation
Task namePlease enter the task name.
Task typePlease select the task type.
Auto-runSelect whether to run automatically after the preceding task is completed.
  • ON: The task starts automatically when the preceding task is completed.
  • OFF: The task owner clicks Start to begin the task.
Conditional executionSelect whether to allow the current task to run based on the status of the preceding task (success/failure/skip).
  • If the preceding task’s execution condition is met: the current task can proceed (start/complete).
  • If the preceding task’s execution condition is not met: the current task cannot proceed and will automatically become skip state.
Conditional execution item
  1. It is displayed when conditional execution is ON.
  2. Select the preceding task and check the appropriate option among on success/on failure/skip as the execution condition.
  3. Click the Add button to add a preceding task execution condition.
  4. Each condition is combined with AND to determine satisfaction or failure.
person in chargeSearch for and enter the personnel who will perform the task among the members of the project group.
  • The assignee can be searched among the project group members.
Assign yourself as the person in chargeClick to set the current task’s assignee to yourself.
Receive email upon completionSearch for and enter the recipient who will receive an email when the task is completed.
  • Email recipients can be searched among project group members.
DeleteDelete the current task.
ApplyApply the current task settings to the workflow.
Table. Task Common Items

Jenkins task

This is a task that can run a build pipeline added to the project or a Jenkins Job not registered in the DevOps Console.

ItemExplanation
Jenkins TypeSelect Jenkins Type
  • Project: Executes the build pipeline added to the project.
  • User Input: The user directly enters a Jenkins job not registered in the DevOps Console and runs it.
ProjectPlease select the project to run the pipeline.
Jenkins URLSelect the URL of the Jenkins tool registered for the chosen project.
JobSelect a job from the selected Jenkins URL.
Jobs that the current user has permission to run are displayed in the list.
ParameterEnter the parameters required to run the build pipeline
  • If a parameter is needed when building a Job, a screen will appear where you can view and edit the parameter.
  • You can enter a value directly or select an environment variable to use. For environment variables, refer to 환경변수 수정하기.
Jenkins Job URLEnter the URL of a Jenkins Job that is not registered in the DevOps Console.
Jenkins ID
Jenkins Password or Token
  1. Enter the ID and Password or Token to use for running the Jenkins job.
  2. After entering, click the Connection Test button to verify that the entered Jenkins Job URL connects properly.
  3. If a parameter is required when building the job, the parameter will be displayed; check and modify the required parameter.
Table. Jenkins task items

User Task

This task registers cases where the user has work that must be performed manually.

Itemdescription
Estimated timePlease enter the estimated time required for the User task.
ExplanationEnter the tasks that the responsible person must perform according to the manual.
Table. User task items

Blue/Green transition task

This is a task that can be integrated with the project’s Blue/Green deployment.

ItemExplanation
ProjectSelect the project to perform the blue-green transition.
Blue‑green listSelect the bluegreen you want to run in the task from the list of bluegreens in the selected project.
Table. Blue/Green transition task items

If the Blue/Green switch task is performed during a release, you can carry out the following actions.

ItemExplanation
Check operational statusClick the Check operation status button to open the Blue/Green operation status check popup.
ConversionCheck the status of operation/operation standby and click the Switch button.
Operation and operation standby will be switched.
CompletedCheck the blue/green transition result and click the Complete button to complete the blue/green task.
If there is a problem with the transition, you can click the Check operation status button to revert to the previous state.
Table. Possible task items in Blue/Green transition

Internal approval task

This task enables approval by a USER who belongs to the project group.

Item
Explanation
Include JIRA version issuesSelect whether to include JIRA Version issues in the approval content.
When proceeding with a release, select the JIRA Version set in the project group; the list of all issues corresponding to that Version will be automatically added to the approval text.
JIRA ProjectSelect a JIRA Project.
JIRA Project you can select from the JIRA Projects that have been registered.
Approval line templateSelect the approval line you added in Approval Template Settings and add approvers in bulk.
ApproverSearch for the approver and add them.
You can search for members of the project group and add them.
Approver ListModify the approver list by changing the approval type, adjusting the order, or deleting entries.
Approval content templateSelect the approval content added from Manage Approval Content and add a title and description.
Approval contentEnter the approval title and approval content.
Table. Internal Approval Task Items

When the internal approval task runs in a release, you can perform the following actions.

  • Approver: Can approve or reject the approval.
    • Approval: Click the Approve button. In the Approve confirmation popup, enter the approval comments and click the Confirm button to approve the document.
    • Reject Approval: Click the Reject button. In the Reject confirmation popup, enter your approval comments and click the Confirm button to reject the approval.
  • Other roles: You can check the approval status.

Helm release task

This is a task that can be linked with Helm releases belonging to the project.

Item
Explanation
Auto shutdownAfter the Helm release execution is completed, select whether to automatically terminate the task.
projectSelect the project to perform the Helm release.
Helm releaseSelect the Helm release to use in the task during the project’s Kubernetes deployment.
workload, Helm release can be selected.
Information about the selected Helm release is displayed.
SET_VALUES (Helm release)It is displayed when the previously selected Helm release is Helm release.
  1. Click the View icon to check the current Helm release’s values.yaml.
  2. Click the Add button to add a key/value.
  3. Enter the key.
  4. You can either input the value directly or select an environment variable to use it.
    Refer to Modify environment variables for environment variables.
SET_VALUES (workload)If the Helm release selected earlier is a workload, display
  • Check the values used in the last deployment.
  • Enter values for tag, deploy_strategy, and repository.
Table. Helm Release Task Items

When the Helm release task runs in a release, you can view the following information on the task edit screen.

When you select Helm Release, you can view the following items.

ItemExplanation
Current statusDisplays the current Helm release status.
Runtime statusDisplays the result of the Helm release execution.
DetailsDisplays the Helm release history.
View icon can be clicked to check the Values.yaml used in the Helm release by revision.
To roll back to a previous deployment, click the Rollback button. In the confirmation popup, click the Confirm button to complete.
Table. Items displayed for Helm release type

When you select 워크로드, you can see the following items.

ItemExplanation
Runtime statusDisplays the result of the Helm release execution.
DetailsDisplays the deployment history.
To roll back to a previous deployment, click the Rollback button. In the confirmation popup, click the Confirm button to complete.
Table. Project creation basic information entry items

Image Repository Replication Task

This task can replicate an image to another repository.

Source image → (copy) Target image

Item
Explanation
TypeSelect Type
  • Project: Select the image repository added to the project as Source and Target.
  • User Direct Input: Enter an image repository not registered in the DevOps Console as Source and Target.
Source projectSelect a project with a registered source image repository.
Source image repositorySelect the image repository registered in the Source project.
Source tagEnter the Source tag.
tag can be set by entering a value directly or by selecting an environment variable. Refer to Modify environment variables for environment variables.
Target projectSelect a project where the target image repository is registered.
Target image repositorySelect the image repository registered in the Target project.
Target tagEnter the target tag.
Source HostEnter the Source Host domain name.
Source PathPlease enter the Source Path.
Source ID
Source Password
Enter the account information for the source image repository.
After entering, click the Connection Test button to verify that the connection is successful.
Target HostTarget Host Please enter the domain name.
Target PathPlease enter the target path.
Target ID
Target Password
Enter the account information for the target image repository.
After entering, click the Connection Test button to verify that the connection is successful.
Table. Image Repository Replication Task Items

SCM repository release task

This task executes a release of the SCM repository.

SCM repository releases perform release creation or tag creation depending on the SCM repository tool (GitHub, GitLab, other Git repositories).

ItemExplanation
Git TypeSelect Git Type
  • Project: Select a code repository added to the project.
  • User Input: The user enters a Git repository not registered in the DevOps Console.
projectSelect a project with a registered code repository.
SCM repositorySelect the code repository registered in the project.
SCM branchSelect a branch of the code repository.
SCM tagEnter the tags to create in the release.
Git URLEnter the Git URL.
Git ID
Git Password or Token
Enter your Git account information.
branchEnter the Git branch.
After entering, click the Connection Test button to verify that the connection is successful.
Table. SCM Repository Release Task Items

GIT branch creation task

This is a task that can copy a specific Git branch and create a new branch.

Itemdescription
Git TypeSelect Git Type
  • Project: Select a code repository added to the project.
  • User Input: The user enters a Git repository not registered in the DevOps Console.
projectSelect a project with a registered code repository.
repositorySelect the code repository registered in the project.
branchSelect the existing branch that the newly created branch will reference.
new branchEnter the name of the new branch.
Apply ProtectedSelect whether to apply the protection rule to the newly created branch.
Protection RuleWhen applying a Protection Rule, set the Merge and Push permissions.
  • Select a role that is allowed to Merge.
  • Select a role that is allowed to Push.
Git URLEnter the Git URL.
Git ID
Git Password or Token
Enter your Git account information.
branchEnter the existing branch that the newly created branch will reference.
After entering, click the Connection Test button to verify that the connection is normal.
Table. GIT branch creation task items

JIRA release task

This is a task that can set a specific version of a JIRA project to Released or Unreleased.

ItemExplanation
JIRA projectSelect a JIRA project registered in the project group.
JIRA URLYou can view the Server of the selected JIRA project. (Readonly)
JIRA VersionSelect the Version of the JIRA project
  • Only versions with the Unreleased status can be selected.
Table. JIRA Release Task Items

If a JIRA release task is in progress in the release, you can perform the following actions.

Itemdescription
statusWhen you click the Status button, the JIRA release popup opens.
State changeClick the Change Status button to change the JIRA version to Released, or change it back to Unreleased.
ConfirmConfirm click the button to complete the JIRA release.
Table. Actions that can be performed in JIRA release tasks

VM deployment task

a task that can deploy a VM deployment group in the Build Complete state or roll back to a previous version.

Itemdescription
projectPlease select a project.
deployment groupSelect a deployment group
Deployment group informationThe contents stored in the deployment group are set automatically.
Table. VM Deployment Task Items
Approval Template Settings
JIRA Project