Related CLI Commands
The table below provides the list of service-related commands and their descriptions:
|or2-manage-service ... -s jenkins -a
||Starts the service in the specified project and region
||Describe the existing Jenkins jobs
||Creates a new Jenkins job
||Triggeres the specified Jenkins job execution
||Removes the specified Jenkins job
||Manages Jenkins plugins
|or2-audit -p project -r region -g jenkins
||Retrieves the Audit on Jenkins performance
Further on this page, you can find the examples of the commands usage for Jenkins Service manipulation.
To start the service, use the or2-manage-service command with the following parameters:
or2ms -p project -r region -s jenkins --activate -k key_name
Here, the -s parameter specifies the name of the service to manage (jenkins), and the --activate parameter
indicates that the service should be activated (to stop the service, use --deactivate). The -k (--key-name)
parameter specifies the SSH key name that will be used to run the service VM. The key is necessary for running
the service in AWS, and is not obligatory for Azure.
During the service activation, a VM is started and a Jenkins server is configured on it.
To create a Jenkins cluster, repeat the or2ms command to start Jenkins slaves. Repeat the command as many times as you need slave instances.
The Jenkins slave instances will have the same configuration as the master instance. All integrations between the master and the slaves will be performed automatically.
EPAM Orchestrator supports the following commands for Jenkins service manipulations:
To create a new Jenkins job, run the or2-create-jenkins-job (or2cjj) command specifying the -c/--config property with the Job XML config file:
or2cjj -j "new job" -p project -r region --config [path to job XML config file]
The or2cjj command verifies whether all required for the selected configuration are available. If one or several plugins are missing,
the job is not created, and the system returns an error message listing the missing plugins.
To manage Jenkins plugins, use the or2-manage-jenkins-plugins (or2mjp) command. This command is used to describe the available plugins, install or uninstall plugins.
or2mjp -p project -r region
Installing a plugin:
or2mjp -p project -r region –a install –n plugin-name
Uninstalling a plugin:
or2mjp -p project -r region –a uninstall –n plugin-name
To describe the existing Jenkins jobs, run the or2-describe-jenkins-jobs (or2djj) command:
or2djj -p project -r region
To trigger a Jenkins job, run the or2-trigger-jenkins-job (or2tjj) command:
or2tjj -p project -r region -j "job_name"
To remove a Jenkins job, run the or2-remove-jenkins-job (or2rjj) command (use the -y parameter for automatic confirmation of the action):
or2rjj -p project -r region -j "job_name"
To stop the Jenkins service and remove the Jenkins Server VM, run the following command:
or2ms -p project -r region -s jenkins --deactivate
You can connect to the Jenkins server by its DNS address and 8080 port:
You can see the Jenkins Server instance DNS in the response of the the or2-describe-services command call.
When you log in, you will get to Jenkins server info and statistics:
The service usage price is defined by the price of the Jenkins Server VM and Jenkins slave VMs, if any.
The default parameters of a Jenkins VM are:
The other significant factor is the Cloud provider and the region you use.
To estimate the price of the AWS-based infrastructure you plan to create, you can use the
AWS Simply Monthly Calculator.
To estimate prices in Azure, see the Azure Pricing page.