...
Executors: An executor is a slot for execution of tasks; effectively, it is a thread in the agent. The number of executors on a node defines the number of concurrent tasks that can be executed on that node at one time. In other words, this determines the number of concurrent Pipeline stages
that can execute on that node at one time. Data Migrators do not recommend running more than one Executor per Jenkins Node as this could permit the definition of Pipelines which cause to resource contention with underlying DataStage components.
...
Assigning Pipeline operations to specific Agents using Labels
In the case of the supplied Upgrade Pipeline certain Pipeline operations need to happen in specific Agents - i.e. some operations must execute on your environment’s legacy Agent, whilst others need to be assigned to a target Agent. To achieve this the MettleCI Sample Jenkins Pipeline assumes the availability of two Agent labels which you should have created and assigned:
Status |
---|
title | mettleci:datastage11.5 |
---|
|
- A Jenkins Agent hosting a MettleCI Command Line on a DataStage v11.5 Client Tier Status |
---|
title | mettleci:datastage11.7.1 |
---|
|
- A Jenkins Agent hosting a MettleCI Command Line on a DataStage v11.7.1 Client Tier You’ll see the labels used in the Pipeline definitions like this:
Code Block |
---|
stages {
stage("Some Pipeline Stage") {
agent {
label 'mettleci:datastage11.5.1'
}
environment {
ENVID = "ci"
DATASTAGE_PROJECT = "${env.IIS_BASE_PROJECT_NAME}_${env.ENVID}"
}
steps { ... } |
Note that the DevOps Pipeline only assumes the presence of a single Agent with the
Status |
---|
title | mettleci:datastage11.7.1 |
---|
|
label, as all operations can execute there.