Pipeline Node (Agent)¶

An Agent defines the execution environment for an entire pipeline or a specific stage. It must be declared at the top of the configuration file or within each stage.

This document describes how to extend a Jenkins Agent running in Kubernetes using the Kubernetes plugin for Jenkins.

Introduction to Kubernetes Pod Templates¶

The Kubernetes plugin runs a special container, jnlp, within the Jenkins Agent Pod. This container facilitates communication between the Jenkins Controller and the Jenkins Agent. Additional containers must be defined to execute pipeline steps, and you can switch between them using the container command.

Use the built-in Label¶

The Workbench declares labels using the podTemplate feature and provides built-in SDKs for users.

SDKs¶

The runtime supports both Docker and Podman, but the operating system varies:

Built-in Command-Line Tools¶

Using Built-in Labels¶

• You can use the go podTemplate in a Jenkinsfile like this:

  pipeline {
    agent {
      node {
        label 'go'
      }
    }
  
    stages {
      stage('go') {
        steps {
          container('go') {
            sh 'go version'
          }
        }
      }
    }
  }
  

• Alternatively, in the Pipeline Editor, you can select an Agent of type node with the label go.

  

Custom podTemplate¶

If you have specific build environment requirements, refer to Creating a Custom Image for implementation details.

Comments