Jenkins is an open source continuous integration tool written in Java. It provides continuous integration (CI) services for software development, primarily in the Java programming language. It is a server-based system running in a servlet container such as Apache Tomcat. It supports SCM tools including Git, CVS, Subversion, Mercurial, Perforce and Clearcase, and can execute Apache Ant and Apache Maven-based projects, as well as arbitrary shell scripts and Windows batch commands. For more information, refer to the Jenkins site.
The Jenkins plugin provides an integration with a Jenkins CI server, allowing a CloudBees CD/RO user the ability to perform several operations on a Jenkins job.
Plugin Version 2.4.1.2023092966
Revised on August 07, 2023
Updated Perl version required
This plugin uses an updated version of Perl and requires CloudBees CD/RO agent version 10.3 or later.
For all parameter descriptions below, required parameters are shown in bold italics. |
Plugin configurations
Plugin configurations are sets of parameters that can be applied across some, or all, of the plugin procedures. They can reduce the repetition of common values, create predefined parameter sets, and securely store credentials. Each configuration is given a unique name that is entered in the designated parameter for the plugin procedures that use them.
Creating plugin configurations
To create plugin configurations in CloudBees CD/RO, complete the following steps:
-
Navigate to
. -
Select Add plugin configuration to create a new configuration.
-
In the New Configuration window, specify a Name for the configuration.
-
Select the Project that the configuration belongs to.
-
Optionally, add a Description for the configuration.
-
Select the appropriate Plugin for the configuration.
-
Configure the parameters per the descriptions below.
If your Jenkins instance has CSRF protection enabled, no additional setup is required. EC-Jenkins applies the CSRF token to request by itself, if necessary. |
Updated Perl version required
This plugin is using an updated version of Perl, cb-perl shell (instead of old ec-perl). This means that it needs CloudBees CD agent version 10.3+ in order to work.
Plugin configuration parameters
Parameter | Description |
---|---|
Configuration Name |
Provide a unique name for the configuration. |
Server URL |
Hostname or a full address of Jenkins server. For example:
|
Folder/View/Team Location: |
A path to |
User Name |
Provide a valid user in your Jenkins server. |
Password |
Either a password or a token. Please read the note below for token based authentication. |
Test Connection? |
Check if connection should be established during config creation to validate credentials. |
HTTP Proxy |
An HTTP proxy that should be used for connections. |
Proxy Authorization |
Username and password used to connect to HTTP proxy. |
Token based authentication
In addition to password based authentication, this plugin supports token based Authentication provided by one of the following mechanisms.
In both the cases above pass the corresponding Token in the password parameter.
Plugin procedures
Collect Reporting Data
Collects reporting data from Jenkins and sends it to CloudBees CD/RO reporting server.
By default, following fields are mapped to the report:
Build report:
Parameter from Jenkins or plugin | Row in build report |
---|---|
CloudBees CD project |
projectName |
url |
sourceUrl |
pluginConfiguration |
Plugin configuration name |
buildNumber |
number |
startTime |
timestamp from Jenkins converted to date |
endTime |
timestamp + duration converted to date |
duration |
duration |
buildStatus |
result |
timestamp |
timestamp from Jenkins converted to date |
releaseName |
Jenkins job name |
releaseProjectName |
Jenkins job name |
Who launched the build |
launchedBy |
Quality report:
Parameter from Jenkins or plugin | Row in quality report |
---|---|
Url of test report, constructed from procedure parameters and Jenkins url |
sourceUrl |
pluginConfiguration |
Plugin configuration name |
buildNumber |
number |
category |
Test category from plugin parameters |
releaseName |
Jenkins job name |
releaseProjectName |
Jenkins job name |
Procedure parameters:
Parameter | Description | ||
---|---|---|---|
Configuration name |
The name of the configuration that contains the information required to connect to Jenkins. |
||
Retrieve test results also |
The test results for the builds are stored as quality report data type. |
||
Copy Jenkins Builds Labels as Tags |
If selected, the build labels are copied as tags on the build payload. The tags are in CloudBees CD/RO if they do not already exist. |
||
Preview mode |
Special CollectReportingData procedure mode. This mode is designed to help you with report configurations. If this mode is enabled, no reports are sent and no metadata is set; high verbosity is enabled instead. In this mode, you can configure mappings, transformation set before enabling automatic reporting. In this mode each object, retrieved from Jenkins is displayed, transformation, mapping and final payload are displayed also. |
||
Job name |
Name of the Jenkins job to build report. |
||
Test report location |
Location of the test report. Applicable only for quality reports. Defaults to /testReport. |
||
Test category |
Test category. Applicable only for quality reports. For example: junit. |
||
Field mapping |
Allows user to place custom fields to payload, or modify payload values. Examples: "MyApplication":build.releaseName - map value "MyApplication" to build report releaseName field. For quality reports: "MyApplication":quality.releaseName lastBuiltRevision.SHA1:build.myLastRevision - map SHA1 field from lastBuiltRevision object to myLastRevision. lastBuiltRevision.branch[0].SHA1:quality.myLastRevision - map SHA1 field from first element of branch array of lastBuiltRevision object to myLastRevision. |
||
Transform script |
Allows user to provide perl script for payload customization. This
method is invoked by plugin with 2 parameters. 1st parameter is
context object, 2nd is payload object. Since EC-Jenkins sends two
types of reports, payload is a hash reference with build and
payload sections. Method should be named transform, and should return
payload object. In this example, the
|
||
Metadata propertysheet path |
Property sheet where run metadata are
stored. Optional field. If omitted,
|
||
Results count on initial retrieval |
Count of old builds to retrieve from server. If omitted it is set to 10. |
||
Base URL for drill-down |
Base URL for the Jenkins. If empty, it is set to:
Parameter Jenkins_URL should be configured in Jenkins server, at:
|
||
Debug |
If selected, the debug level is set to "Debug". The summary logs are written with the higher verbosity. |

DownloadArtifacts
Downloads artifacts from Jenkins.
Parameter | Description |
---|---|
Configuration name |
The name of the configuration that contains the information required to connect to Jenkins. (Required) |
Job Name |
Name of the job. |
Build number. |
Jenkins build number. If not specified, the latest build is used. |
Target directory |
Target directory. If omitted, the workspace directory is used. |
Artifacts to download |
Provide a pattern for artifacts to download. |
Job Action
Performs several actions according to the user-provided parameters
Parameter | Description |
---|---|
Configuration name |
The name of the configuration that contains the information required to connect to Jenkins. (Required) |
Action |
Desired action to perform. (Required) |
Job Name |
Name of the job. (Required) |
Build Number |
Build number. (Only visible when the "stop" action is selected) (Required) |
New Job’s Name |
Provide a new name for the job. (Only visible when the "rename" action is selected). (Required) |
Parameters |
An option list of parameters in the form param1=value1,param2=value2 |

GetArtifactList
Retrieves list of artifacts that only were archived during Jenkins build. That is, this procedure does not return an artifact if it was built, but not archived. To archive artifact please configure your project to use "Archive Artifacts" Post-Build action in Jenkins.
Parameter | Description |
---|---|
Configuration Name |
Name of the configuration that contains Jenkins authentication information. |
Job Name |
Name of the Jenkins job. |
Build Number |
Build number. If a build number is not provided,
|
Result Property |
Property name used to store the artifact list. |
Result Format |
Format to store results, JSON or property sheet. |
Get Build Details
Get all information of Jenkins build.
Parameter | Description |
---|---|
Configuration name |
The name of the configuration that contains the information required to connect to Jenkins. |
Job Name |
Name of the job. |
Build Number |
Specific build name to look at. (If not provided, the build number is the last one). |
Need to Create the Report? |
If selected, the Report step of this procedure runs. Default is to run the Report step. |
Result (output property path) |
Property name used to store the result of the http response. |
Output
After the job runs, you can view the results on the Job Details page in CloudBees CD/RO. The status of the page was checked successfully.

Output Parameter | Description |
---|---|
jenkinsbuildurl |
URL to HTML report with Jenkins build information |
jenkinsjoburl |
URL to the Jenkins job |
jenkinsbuildnumber |
Jenkins job build number |
jenkinsapiresponse |
A response from Jenkins APIs in JSON format. |
Get Build Duration
Get the duration of the last job’s build
Parameter | Description |
---|---|
Configuration name |
The name of the configuration that contains the information required to connect to Jenkins. (Required) |
Job Name |
Name of the job. (Required) |
Build Number |
Specific build name to look at. (If not provided, the build number is the last one). |
Time Unit |
Time unit of the output. |
Result (output property path) |
Property name used to store the result of the http response. |

Get Build Log
Get the last full log of a job’s build.
Parameter | Description |
---|---|
Configuration name |
The name of the configuration that contains the information required to connect to Jenkins. (Required) |
Job Name |
Name of the job. (Required) |
Build Number |
Specific build name to look at. (If not provided, the build number is the last one). |
Result (output property path) |
Property name used to store the result of the http response. |

Get Build Parameters
Get the parameters of a Jenkins job’s build.
Parameter | Description |
---|---|
Configuration name |
The name of the configuration that contains the information required to connect to Jenkins. (Required) |
Job Name |
Name of the job. (Required) |
Build Number |
Specific build name to look at. (If not provided, the build number is the last one). |
Result (output property path) |
Property name used to store the result of the http response. |
Get Build Status
Get the status of a Jenkins job’s build. If the build was aborted or
fails, this procedure sets the jobStep
outcome property as 'error'.
Parameter | Description |
---|---|
Configuration name |
The name of the configuration that contains the information required to connect to Jenkins. (Required) |
Job Name |
Name of the job. (Required) |
Build Number |
Specific build name to look at. (If not provided, the build number is the last one). |
Result (output property path) |
Property name used to store the result of the http response. |

GetChangeLog
Get the changelog from Jenkins build. If there are changesets with different SCM types, additional properties with commits for every SCM are saved.
Parameter | Description |
---|---|
Configuration Name |
The name of the configuration that contains the information required to connect to Jenkins. |
Job Name |
Name of the job. |
Build Number |
Specific build name to look at. (If not provided, the build number is the last successful one). |
Result (output property path) |
PropertySheet name used to store the changelog. If it does not exist, it is created. If left empty, '/myJobStep/changelog' is used. |
Run and Monitor Build
Launch a build and show the output as it runs. If the procedure is aborted, the Jenkins build is stopped.
Parameter | Description | ||
---|---|---|---|
Configuration name |
The name of the configuration that contains the information required to connect to Jenkins. |
||
Job Name |
Name of the job. |
||
Parameters |
Parameters in either a comma-separated list of key-value pairs (
|
||
Is Parameters content in JSON format? |
Select if you provided JSON content in the Parameters field.
|
||
Need to Create the Report? |
If selected, the Report step of this procedure runs. Default is to run the Report step. |
||
Enable Parallel Mode? |
Enable this mode if you have a need to run more than one instance of this procedure in parallel (for example as a Group task in a pipeline). |

Output Parameter | Description |
---|---|
jenkinsbuildurl |
URL to HTML report with Jenkins build information |
jenkinsjoburl |
URL to the Jenkins job |
jenkinsbuildnumber |
Jenkins job build number |
Parallel Mode
If Parallel Mode has been enabled, you need to make sure that:
-
Your Jenkins job is parametrized.
-
Your parametrized job has efJobStepId parameter.
If Enable Parallel Mode is selected and the Jenkins Build Job is not parametrized with the efJobStepId parameter, the procedure fails. To get more details about this behavior and why it was done in this way, refer to Known issues. |
Run and Wait
Launch a build and wait for it to finish. No postp
matcher is included.
If the procedure is aborted, the Jenkins build is stopped.
Parameter | Description | ||
---|---|---|---|
Configuration name |
Name of the configuration that contains Jenkins authentication information. |
||
Job Name |
Name of the job. |
||
Parameters |
Parameters in either a comma-separated list of key-value pairs (
|
||
Is Parameters content in JSON format? |
Select if you provided JSON content in the Parameters field.
|
||
Need to Create the Report? |
If selected, the Report step of this procedure runs. Default is to run the Report step. |
||
Enable Parallel Mode? |
Enable this mode if you have a need to run more than one instance of this procedure in parallel (for example as a Group task in a pipeline). |
Output Parameter | Description |
---|---|
jenkinsbuildurl |
URL to HTML report with Jenkins build information |
jenkinsjoburl |
URL to the Jenkins job |
jenkinsbuildnumber |
Jenkins job build number |
Parallel Mode
If Parallel Mode has been enabled, you need to make sure that:
-
Your Jenkins job is parametrized.
-
Your parametrized job has efJobStepId parameter.
If Enable Parallel Mode is selected, and the Jenkins Build Job is not parametrized with the efJobStepId parameter, the procedure fails. To get more details about this behavior and why it was done in this way, refer to Known issues. |
Show Build Process (real-time)
Show information about a build while it is taking place (real-time)
Parameter | Description |
---|---|
Configuration name |
The name of the configuration that contains the information required to connect to Jenkins. (Required) |
Job Name |
Name of the job. (Required) |
Build Number |
Specific build name to look at. (If not provided, the build number is the last one). |
Result (output property path) |
Property name used to store the result of the http response. |

Server Status Report
Creates a report with the status of a Jenkins server
Parameter | Description |
---|---|
Configuration name |
The name of the configuration that contains the information required to connect to Jenkins. (Required) |
Job Name |
Name of the job. (Required) |
Build Number |
Specific build name to look at. (If not provided, the build number is the last one). |
Result (output property path) |
Property name used to store the result of the http response. |

StopBuild
Stops running Jenkins Build.
Parameter | Description |
---|---|
Configuration Name |
Name of the configuration that contains Jenkins authentication information. |
Job Name |
Name of Jenkins job to stop. |
Build Number. |
Number of running Jenkins build to stop. |
Wait For Result |
If enabled, the procedure is waiting for the Jenkins build stop. Otherwise, the just stop request is issued. Default is to wait for Jenkins build to be stopped. |
GetJobDefinition
Gets Jenkins job definition in XML format.
CreateJobFromXML
Creates a Jenkins job using an XML definition of the job. A job definition could be obtained using GetJobDefinition procedure.
Parameters
Parameter | Description |
---|---|
Configuration Name |
Name of the configuration that contains the Jenkins authentication information. |
Job Name |
Name of the job to be created. Provide the job name, such as |
Job Location |
Location of the job within folder structure.
For example, to create |
XML Content |
XML Content of Jenkins job. |
Overwrite? |
Configures whether to overwrite existing job. If disabled and the job exists, the procedure fails. Default is not to overwrite an existing job. |
Create Folders Structure? |
Configures whether to create folders structure. If disabled and Job Location value does not exist, the procedure fails. Otherwise, the new folders are created. By default, directory structures are not created. |
Examples and use cases
Run end to end
We are going to see a complete run of the Jenkins job’s build execution from CloudBees CD/RO.
-
Configure the plugin to be able to connect to our Jenkins server; you can do so by clicking on the configure link in the plugin manager page.
-
Create a new CloudBees CD/RO project and name it "jenkins".
-
Create a procedure inside the project we just created and name it Jenkins Build
-
In the Jenkins procedure, create two parameters: configuration_name and job_name.
-
Our first step is going to be starting a build from CloudBees CD/RO, for that purpose we need to create a new step from the Jenkins - Execute job action step picker.
-
Once a Jenkins job’s build has been executed, we are going to monitor in real time our build.
To achieve this, you must create a new step from the step picker named Jenkins - Show Build Process.
-
Create a simple command step with cb-perl shell and write sleep 10 to make sure we have enough time for the next step.
-
Now we need to know the build statistics by creating 3 more steps: get log, get status and get duration.
-
Finally, after the last step generate a report of the builds on the Jenkins server by creating the last step from the step picker named Jenkins - Server Status Report.
At this point your procedure should appear like this:
-
Now it’s time to run the procedure, in my case I have a Jenkins job named Sample build, but feel free to specify your own.
-
After running the procedure, you should be able to see something like:
-
Properties generated during the build are available under the "Properties" tab:
-
-
If you want to see the report generated, just select the circled link.
Configure parallel builds in CloudBees CD/RO using Enable Parallel Mode
-
Create a configuration for EC-Jenkins:
-
Create a new pipeline using the CloudBees CD/RO UI.
-
Now, go to the Jenkins UI and create a job and add a parameter efJobStepId required for RunAndMonitorBuild procedure:
Please, note, that this parameter is set by plugin, you don’t need to configure it in your procedure parameters form.
-
Define three tasks in the pipeline stage:
-
Group tasks using CloudBees CD/RO UI to make them run in parallel. For that select them and select the group icon:
-
Run the pipeline.
-
Get Run Pipeline Results:
-
Confirm on Jenkins side that we have exactly 3 build runs:
Multibranch pipelines jobs
When working with the complex job structure, the Job Name parameter has to be specified in a URI-compatible way, but the plugin handles the multibranch pipeline job names and transforms them automatically. Here are some examples of the job names in Jenkins and how they have to be specified in the Job Name parameter:
Jenkins job case | Job Name value |
---|---|
Regular Job |
|
RegularJob |
RegularJob |
JobWith/symbol |
JobWith%2Fsymbol |
JobNameWith space |
JobNameWith%20space |
Multibranch pipeline jobs |
|
Specific branch of a project |
Project/branch |
Specific branch of a project |
Project/job/branch |
Specific branch with a '/' in a project |
Project/branchNamePart1/branchNamePart2 |
Specific branch with a '/' in a project |
Project/job/branchNamePart1%2FbranchNamePart2 |
Nested Jobs |
|
JobLevel2 in JobLevel1 |
JobLevel1/job/JobLevel2 |
JobLevel3 in JobLevel2 in JobLevel1 |
JobLevel1/job/JobLevel2/job/JobLevel3 |
Known issues
Jenkins does not provide a way to get the build number of a remotely invoked build synchronously. Hence, the logic used to decipher the build number after its invocation may not work accurately in situations, where in there are concurrent invocations of the same build. This means that the monitoring of a Build from CloudBees CD/RO in such situations may not be accurate. The following issues with Jenkins are provided as a reference to highlight the challenges with different approaches to query the build number.
Release notes
EC-Jenkins 2.4.1
-
Fixed an issue where Monitor step of RunAndMonitorBuild was running for a very long time.
-
Improved Queue ID handling for RunAndMonitorBuild and RunAndWait procedures.
EC-Jenkins 2.4.0
-
Added support to the RunAndMonitorBuild and RunAndWait procedures Parameters field to escape commas (
,
) and equals (=
) used with input. -
Improved the RunAndMonitorBuild and RunAndWait procedures to support JSON build parameters by implementing a new "Is Parameters content in JSON format?" option.
EC-Jenkins 2.3.1
-
RunAndMonitorBuild and RunAndWait procedures were improved to send parameters for parametrized builds within a request body to support parameter values of any length.
EC-Jenkins 2.2.2
-
Old configurations are deprecated and disabled. Starting from EC-Jenkins 2.2.2, the Platform UI does not allow you to create new plugin configurations. Selecting the Create Configuration link in the Platform UI now redirects to Configure Plugin of the new CloudBees CD/RO UI.
-
Test Connection feature of plugin configurations has been fixed for SSL Bump proxy configurations.
EC-Jenkins 2.2.0
-
A new Check Connection Resource field has been added to the plugin configuration. This field allows specifying a particular resource to execute Check Connection logic.
EC-Jenkins 2.1.0
-
A retry mechanism has been added to the RunAndWait and RunAndMonitorBuild procedures to mitigate possible network-related environmental issues.
-
An issue where some images were missing in the report generated by ServerStatusReport has been fixed.
-
All API calls in the plugin now use a tree parameter to follow best practices: /d/kb-217375688.
EC-Jenkins 2.0.2
-
The issue when the RunAndWait procedure did not abort the Jenkins build after a pipeline was aborted has been fixed.
EC-Jenkins 2.0.0
-
Upgraded from perl-5.8 to perl-5.32. No backward compatibility with releases prior 10.3. Starting from this release new agent is required to run this plugin’s procedures.
-
Removed excessive parameter Auth Type.
EC-Jenkins 1.20.0
-
The following procedures: Get Build Details, Run And Wait, Run and Monitor Build were improved, and report generation now could be disabled in the parameter form using the Need to Create the Report? checkbox.
EC-Jenkins 1.19.2
-
Fixed a warning in the Get Build Details procedure.
-
Fixed a warning in the Report step of Run and Monitor Build and Run And Wait procedures.
-
Plugin documentation has been updated to include an examples of Multibranch Pipeline job names.
EC-Jenkins 1.19.1
-
An issue when in some setups get build details procedure has been failing during the Report step has been fixed.
-
Updated plugin documentation.
EC-Jenkins 1.19.0
-
External credential management support has been added.
-
Fixed a bug when checking the connection during config creation when the Folder/View/Team Location field was set to folder and returning a 403 error.
EC-Jenkins 1.18.3
-
Fixed a bug when the URL was not properly escaped sometimes during the CollectReportingData procedure.
EC-Jenkins 1.18.0
-
New checkbox Depend On Jenkins Build Result? has been added to Run And Wait procedure.
-
Auth Type parameter has been added to the plugin configuration. From now plugin supports Basic and Bearer Token auth.
-
Debug Level parameter has been added to plugin configuration.
-
Collect Reporting Data procedure has been improved to have better support for Multibranch Pipeline.
-
Data source setup for Jenkins has been improved to have better support for Multibranch Pipeline.
EC-Jenkins 1.17.3
-
Resolved an issue when the Report step was failing due to duplicate location in some cases.
EC-Jenkins 1.17.2
-
Fixed a bug in CollectReportingData procedure when it was not possible to retrieve build commit data if the target Jenkins job is a Template Job.
-
Deprecated usage of depth parameter in API calls has been removed.
-
Renamed to CloudBees CD/RO.
EC-Jenkins 1.17.1
-
Parameter Job Name has been marked as required in the parameter form for the JobAction procedure.
EC-Jenkins 1.17.0
-
Integration with CloudBees CI has been improved. Following procedures have improved build report now:
-
GetBuildDetails
-
RunAndMonitorBuild
-
GetAndWait
-
-
Added a new Folder/View/Team Location field to the Plugin Configuration.
-
The UI for the JobAction procedure has been improved for better user experience in CloudBees CD/RO.
-
Minor bug fixes and improvements.
EC-Jenkins 1.16.0
-
Support for new format of the build changeset was added to the following procedures:
-
GetChangeLog
-
CollectReportingData
-
EC-Jenkins 1.15.1
-
When ReleaseCommandCenter DataSource is removed, the CollectReportingData schedule is deleted too.
-
Job for the successful CreateConfiguration and EditConfiguration run is now preserved.
EC-Jenkins 1.15.0
-
Plugin now can check connection with new data when editing plugin configuration.
-
Enhanced Multibranch Pipeline Project job names support for all procedures.
-
New output parameters were added to these procedures:
-
RunAndWait
-
RunAndMonitor
-
-
Link to the Jenkins build is now shown in the pipeline summary for these procedures:
-
RunAndWait
-
RunAndMonitor
-
-
Procedure summaries are now shown in a pipeline run.
EC-Jenkins 1.13.2
-
Configurations can be created by users with an @ sign in a name.
-
A new Enable Parallel Mode checkbox has been added to the RunAndMonitorBuild and RunAndWait procedures to give the ability to monitor concurrent parametrized Jenkins jobs.
EC-Jenkins 1.13.1
-
Fixed the issue with lost output parameters for CloudBees CD/RO v9.0: upon upgrade or clean installation of v9.0 output parameters were not created for the plugin’s procedures.
-
Fixed an issue when mappings was not updated properly after DOIS Datasource modification.
EC-Jenkins 1.11.0
CollectReportingData procedure:
-
Added tags support. Tags from Jenkins builds can be saved as tags in CloudBees CD/RO.
-
Added support of SVN repositories in Jenkins.
-
Datetime fields now in ISO 8601 format in UTC timezone.
-
Added an SCM branch field, that can be used for SVN repositories. For Git, the branch is detected automatically.
-
Updated default field mapping.
-
FIX: Procedure will not fail now if SCM data is not present.
-
FIX: Fixed situation when test report is sometimes not present.
-
Deprecated procedure ImportArtifacts ha been removed.
-
Deprecated Port field in plugin configuration has been removed.
EC-Jenkins 1.10.0
-
Plugin uptake for certain CloudBees CD/RO 8.4 features. Changes include adding an icon for Dashboards and ability to create configurations inline.
-
CollectReportingData procedure has been improved to send reports for DevOps Foresight Center.
-
Support for HTTP Proxy has been provided. Customers who use HTTP proxy can specify Proxy Information (Host, Port and Credentials at the configuration level) and all procedures use the Proxy as second credentials for authentication.
EC-Jenkins 1.9.2
-
Plugin uptake for all the following features which are available with CloudBees CD/RO versions beginning 8.3.
-
Rendering of Procedure Parameters entirely based on configured form XMLs and ability to manage plugin configurations inline as part of a process step or pipeline stage task.
-
Setting output parameter
jenkinsbuildurl
as part of plugin procedures
-
EC-Jenkins 1.9.1
-
Fixed an issue when required parameters count were different in pipeline context for GetBuildDetails, GetBuildParameters and GetArtifactList.
EC-Jenkins 1.9.0
-
StopBuild procedure has been added.
-
GetArtifactList procedure has been added.
-
ImportArtifacts procedure has been marked as deprecated and is removed.
-
Fixed an issue when GetBuildDuration were returning incorrect value instead of error when Jenkins job does not exist.
-
Various bugfixes and improvements.
EC-Jenkins 1.8.4
-
Minor bugfixes and improvements.
-
Added drill-down support for release command center.
EC-Jenkins 1.8.3
-
GetBuildParameters procedure has been added.
-
GetBuildDetails procedure has been added.
-
Test Connection flag has been added to configuration form.
EC-Jenkins 1.8.2
-
CollectReportingData procedure has been added.
-
GetBuildDetails procedure has been added.
-
DownloadArtifact procedure has been added.
-
Port field from plugin configuration is deprecated now and is removed in the next release. Port should be specified in the Server URL instead.
-
Fixed a bug when it was impossible to use Execute Job Action procedure in pipeline and application context.
-
Fixed a bug when it was impossible to run Jenkins Pipelines using the Execute Job Action procedure.