1
0
mirror of https://github.com/SAP/jenkins-library.git synced 2025-12-01 23:02:43 +02:00
Files
sap-jenkins-library/documentation/docs/steps/dockerExecute.md
Oliver Nocon 7a961ef38e seleniumExecuteTests - add step to run Selenium tests (#318)
It comes with an extension to executeDocker and executeDockerOnKubernetes to run sidecar containers.

This helps to execute Selenium tests using two Docker images:

1. Execution runtime for tests (e.g. node image)
2. Selenium instance which holds Selenium server + browser

* add documentation & some name cleanup
* include PR feedback
* add step documentation to structure
2018-10-04 17:06:42 +02:00

4.5 KiB

dockerExecute

Description

Executes a closure inside a docker container with the specified docker image. The workspace is mounted into the docker image. Proxy environment variables defined on the Jenkins machine are also available in the Docker container.

Parameters

parameter mandatory default possible values
script yes
containerPortMappings no
dockerEnvVars no [:]
dockerImage no ''
dockerName no
dockerOptions no ''
dockerVolumeBind no [:]
dockerWorkspace no
jenkinsKubernetes no [jnlpAgent:s4sdk/jenkins-agent-k8s:latest]
sidecarEnvVars no
sidecarImage no
sidecarName no
sidecarOptions no
sidecarVolumeBind no
sidecarWorkspace no
  • script defines the global script environment of the Jenkinsfile run. Typically this is passed to this parameter. This allows the function to access the commonPipelineEnvironment for storing the measured duration.
  • containerPortMappings: Map which defines per docker image the port mappings, like containerPortMappings: ['selenium/standalone-chrome': [[name: 'selPort', containerPort: 4444, hostPort: 4444]]]
  • dockerEnvVars: Environment variables to set in the container, e.g. [http_proxy:'proxy:8080']
  • dockerImage: Name of the docker image that should be used. If empty, Docker is not used and the command is executed directly on the Jenkins system.
  • dockerName: only relevant for Kubernetes case: Name of the container launching dockerImage
  • dockerOptions Docker options to be set when starting the container. It can be a list or a string.
  • dockerVolumeBind Volumes that should be mounted into the container.
  • dockerWorkspace: only relevant for Kubernetes case: specifies a dedicated user home directory for the container which will be passed as value for environment variable HOME
  • sidecarEnvVars defines environment variables for the sidecar container, similar to dockerEnvVars
  • sidecarImage: Name of the docker image of the sidecar container. Do not provide this value if no sidecar container is required.
  • sidecarName: as dockerName for the sidecar container
  • sidecarOptions: as dockerOptions for the sidecar container
  • sidecarVolumeBind: as dockerVolumeBind for the sidecar container
  • sidecarWorkspace: as dockerWorkspace for the sidecar container

Kubernetes support

If the Jenkins is setup on a Kubernetes cluster, then you can execute the closure inside a container of a pod by setting an environment variable ON_K8S to true. However, it will ignore containerPortMappings, dockerOptions and dockerVolumeBind values.

Step configuration

We recommend to define values of step parameters via config.yml file.

In following sections the configuration is possible:

parameter general step stage
script
containerPortMappings X X
dockerEnvVars X X
dockerImage X X
dockerName X X
dockerOptions X X
dockerVolumeBind X X
dockerWorkspace X X
jenkinsKubernetes X
sidecarEnvVars X X
sidecarImage X X
sidecarName X X
sidecarOptions X X
sidecarVolumeBind X X
sidecarWorkspace X X

Return value

none

Side effects

none

Exceptions

none

Example 1: Run closure inside a docker container

dockerExecute(dockerImage: 'maven:3.5-jdk-7'){
    sh "mvn clean install"
}

Example 2: Run closure inside a container in a kubernetes pod

# set environment variable
export ON_K8S=true"
dockerExecute(script: this, dockerImage: 'maven:3.5-jdk-7'){
    sh "mvn clean install"
}

In the above example, the dockerEcecute step will internally invoke dockerExecuteOnKubernetes step and execute the closure inside a pod.

Example 3: Run closure inside a container which is attached to a sidecar container (as for example used in seleniumExecuteTests:

dockerExecute(
        script: script,
        containerPortMappings: [containerPortMappings:'selenium/standalone-chrome':[containerPort: 4444, hostPort: 4444]],
        dockerImage: 'node:8-stretch',
        dockerName: 'node',
        dockerWorkspace: '/home/node',
        sidecarImage: 'selenium/standalone-chrome',
        sidecarName: 'selenium',
) {
    git url: 'https://github.wdf.sap.corp/XXXXX/WebDriverIOTest.git'
    sh '''npm install
          node index.js
    '''
}