Skip to main content

Pipeline Template

AMDP provides base code templates for building microservices. These base code templates enable basic microservice build functions in AMDP.

Pipeline Code Template List​

The Pipeline Code Template menu allows viewing the entire code template containing all procedures to build microservices into container images. The list includes the template name, supported tool type, description, and delete button.

note

Customizing pipeline code falls under consulting, so if you need to configure custom code, please proceed with the AMDP representative.

① Block Delete: Enable/disable delete actions on the screen.

  • Block Delete ON: All Delete buttons are disabled, so users cannot perform any deletion.

  • Block Delete OFF: All Delete buttons are enabled again, allowing users to delete items normally.

â‘¡ Add button: Create a new pipeline code template.

â‘¢ Delete button: Delete existing pipeline code templates. You can also delete multiple templates simultaneously using checkboxes in the first column.

â‘£ Pipeline template name: When clicking the name in the pipeline code list, system navigates to the detailed information template page.

Pipeline Code Template Creation​

Clicking ADD button leads to the pipeline code template creation screen.

  • Name: The name of the code template.
  • Description: Description to be displayed in the list.
  • Code Type: The code template supports Jenkinsfile type for Jenkins and Tekton type for Tekton. You can only specify this once during creation, and it cannot be changed after saving the code.

Depending on the chosen code type, the area below for adding the actual executable code file changes.

For the Jenkinsfile

Enter the name of the code template file you want to create in the Add File Name area and click New File to edit the Jenkins code file:

  • Description: Short description of this template file.
  • Purpose: Purpose of this template (CI/Script)
  • Compatible Framework: Framework that this template is compatible with.
  • File Content: Content of the template file. (Code editor)
  • Custom Parameters: Enter name and value to define custom parameters.

For the Tekton

Add new file name and click to button Generate new/ New file to edit the file Tekton pipelines:

  • Purpose: Purpose of this template (CI/Script)
  • Compatible Framework: Framework that this template is compatible with.
  • Description: Short description of this template file.
  • Task Structure: The task structure of the Tekton pipeline.
  • Code: The main editor area where you write Tekton pipeline definition.
  • Tekton PipelineRun Params: Enter name and value to define parameters.
  • Tekton PipelineRun Workspaces: Enter name and value to define workspaces.

Tekton task:

Once a purpose and framework are set during creation, they cannot be changed. For detailed explanations of individual fields, refer to the following code template detail view and modification screen.

Pipeline Code Template Detailed View and Modification​

To access to the Pipeline Code Template Details, clicking on the code template name displays the List of pipeline code templates screen.

Below is the screen when a Tekton type base code template is opened:

â‘  General information: specify the name, description, and type of the pipeline code template.

  • Name: Pipeline template name used to identify the template.
  • Description: Short description of the pipeline template.
  • Code Type: The pipeline type of this template.
note

The type supports Tekton and Jenkins. Once set, the type cannot be changed.

â‘¡ For Tekton type, tabs for managing Tekton pipelines and tasks are displayed separately.

â‘¢ Add file and Delete buttons: If you want to add new pipeline code, enter its name in this area and click New File to add it. Unused code files can be deleted with the Delete Current File button.

â‘£ List of pipeline code files or task files belonging to the template in vertical tabs.

⑤ Detailed content of pipeline code files or task files: specify the purpose, framework, description, code, containerization specifications (Dockerfile), additional parameters, and Tekton Workspace specifications for the pipeline code file.

note

AMDP automatically generates certain parameters, but you may need to use different values as needed. Discuss modifications with an AMDP representative, as this falls under consulting.

For Jenkins, the screen appears differently to match its characteristics.

â‘  Names and descriptions can be specified similar to Tekton. Once a code template is saved as a Jenkins type, its type cannot be changed.

â‘¡ Unlike Tekton, Jenkins uses a single code file format called Jenkinsfile, which contains all the necessary execution procedures, so the feature to add code files is located above the tabs.

â‘¢ Similar to Tekton pipelines, you can specify descriptions, purposes, compatible frameworks, containerization specifications, and additional parameters.