Jenkins plugin

17 minute readExtensibilityDeveloper productivity

Jenkins is an open source continuous integration tool written in Java. It provides continuous integration 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 CVS, Subversion, Git, Mercurial, Perforce and Clearcase, and can execute Apache Ant and Apache Maven based projects as well as arbitrary shell scripts and Windows batch commands.

More information can be found at https://www.jenkins.io/.

The EC-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.2.0.2022072731

Revised on July 27, 2022

Integrated version

This plugin was tested against Jenkins version 2.222.3

In the CloudBees CD/RO UI, open the main menu and select Admin Plugins to open the Plugin Manager.
For all parameter descriptions below, required parameters are shown in bold italics.

Setting up the plugin configuration

Plugin configurations are created by going to the CloudBees CD/RO Administration tab, then to the Plugins sub-tab. On the right side of the line for the specific plugin, there is a Configure option that opens the Configuration page.

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 ec-perl). This means that it needs CloudBees CD/RO agent version 10.3+ in order to work.

Plugin configuration parameters

ParameterDescription

Configuration Name

Provide a unique name for the configuration.

Server URL

Hostname or a full address of Jenkins server. For example: http://localhost:8080

Folder/View/Team Location:

A path to team/folder/view of a Jenkins of the CloudBees CI instance. For example, if the Server URL is set to https://yourinstance.cloudbees.com, and your team location is https://yourinstance.cloudbees.com/your-cool-team, you need to set /your-cool-team or your-cool-team as the value for this field. If you have a folder, and your folder location is https://yourinstance.cloudbees.com/job/your-cool-folder, you need to set job/your-cool-folder as the value for this field.

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.

  • Jenkins API Tokens as in here

  • GitHub Personal Access Tokens based on the GitHub OAuth plugin as in here

In both the cases above pass the corresponding Token in the password parameter.

Configuration form

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 pluginRow 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 pluginRow 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:

ParameterDescription

Configuration name

The name of the configuration that contains the information required to connect to Jenkins.

Retrieve test results also

The tests 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 customer with report configuration. If this mode is enabled, no reports are sent and no metadata is set. High verbosity is enabled instead. In that mode, user can configure mappings, transformation before 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-2.2.0.2022072731 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 myTimestamp field is added to build and quality payload objects:

sub transform {
    my ($context, $payload) = @_;
    $payload->{build}->{myTimestamp} = $context->one();
    $payload->{quality}->{myTimestamp} = $context->two();
    return $payload;
}
sub one {
    my ($context) = @_;
    return time();
}
ElectricCommander module can be imported and used in transform script as usual. This example shows how to access to ElectricCommander API, read and write custom properties:
use ElectricCommander;
my $ec = ElectricCommander->new();

sub transform {
    my ($context, $payload) = @_;

    # Set property to job
    $ec->setProperty('/myJob/build_document_id', $payload->{build}->{documentId});

    # Get property from project and add to payload
    my $projectName = $ec->getProperty('/myJob/projectName')->findvalue('//value');
    my $prop = $ec->getProperty("/projects/$projectName/my_custom_property")->findvalue('//value')->string_value;

    $payload->{build}->{my_custom_property} = $prop;

    return $payload;
}

Metadata propertysheet path

Property sheet where run metadata are stored. Optional field. If omitted, /mySchedule/EC-Jenkins-%JobName%-%Report Object Type% is used for schedule contest. For all other contexts root is /myProject.

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:

%Jenkins_URL%/job/%Job name%

Parameter Jenkins_URL should be configured in Jenkins server, at:

http(s)://jenkins:[port]/configure

Debug

If selected, the debug level is set to "Debug". The summary logs are written with the higher verbosity.

DownloadArtifacts

Downloads artifacts from Jenkins.

ParameterDescription

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.

Parameter form

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.

In the DownloadArtifacts step, click the Log button to see the diagnostic information:

Job Action

Performs several actions according to the user-provided parameters

ParameterDescription

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.

ParameterDescription

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, lastBuild is used.

Result Property

Property name used to store the artifact list.

Result Format

Format to store results, JSON or property sheet.

Parameter form

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.

In the GetArtifactList step, click the Property tab to see an artifact list:

Get Build Details

Get all information of Jenkins build.

ParameterDescription

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.

Parameter form

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 ParameterDescription

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

ParameterDescription

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.

ParameterDescription

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.

ParameterDescription

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.

Parameter form

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.

In the GetBuildParameters step, click the Log button to see the diagnostic information:

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'.

ParameterDescription

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.

ParameterDescription

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.

Parameter form

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.

In the GetChangeLog step, click the Log button to see the diagnostic information:

Run and Monitor Build

Launch a build and show the output as it runs. If the procedure is aborted, the Jenkins build is stopped.

ParameterDescription

Configuration name

The name of the configuration that contains the information required to connect to Jenkins.

Job Name

Name of the job.

Parameters

An option list of parameters in the form param1=value1,param2=value2

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 ParameterDescription

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.

ParameterDescription

Configuration name

Name of the configuration that contains Jenkins authentication information.

Job Name

Name of the job.

Parameters

An option list of parameters in the form param1=value1,param2=value2

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 ParameterDescription

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)

ParameterDescription

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

ParameterDescription

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.

ParameterDescription

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.

Parameter form

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.

In the StopBuild step, click the Log button to see the diagnostic information:

Examples and use cases

Run end to end

We are going to see a Run end to end Jenkins job’s build execution from CloudBees CD/RO.

  1. 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.

    configurations
  2. Create a new CloudBees CD/RO project and name it "jenkins".

  3. Create a procedure inside the project we just created and name it Jenkins Build

  4. In the Jenkins procedure, create two parameters: configuration_name and job_name.

    parameter1
    parameter2
  5. 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.

    run
  6. 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.

    show progress
  7. Create a simple command step with cb-perl shell and write sleep 10 to make sure we have enough time for the next step.

    sleep
  8. Now we need to know the build statistics by creating 3 more steps: get log, get status and get duration.

    log
    status
    duration
  9. 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.

    report

    At this point your procedure should appear like this:

    + image::cloudbees-common-sda::cd-plugins/ec-jenkins/examples/jenkins-build-procedure-10.png[complete procedure,role="screenshot"]

  10. 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.

    filling parameters
  11. After running the procedure, you should be able to see something like:

    green build

    Properties generated during the build are available under the Properties tab:

    properties
  12. If you want to see the report generated, just click on the circled link

    jenkins build procedure 14
    report

Configure parallel builds in CloudBees CD/RO using Enable Parallel Mode

  1. Create a configuration for EC-Jenkins:

  2. Create a new pipeline using the CloudBees CD/RO UI.

  3. 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.

  4. Define three tasks in the pipeline stage:

  5. Group tasks using CloudBees CD/RO UI to make them run in parallel. For that select them and select the group icon:

  6. Run the pipeline.

  7. Get Run Pipeline Results:

    run pipeline results
  8. 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 caseJob 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.2.0

  • The new field in the plugin configuration, "Check Connection Resource," has been added. 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.1

  • Added session validation.

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.21.1

  • Fixed support for the new configurations created with the UI.

EC-Jenkins 1.21.0

  • The support of a new configurations has been added.

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.2

  • The documentation has been migrated to the main documentation site.

EC-Jenkins 1.18.1

  • Fixed a bug when check connection was returning incorrect result.

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.2

  • Fixed minor UI issues with the EditConfiguration form.

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.14.1

  • Changed author to "CloudBees".

EC-Jenkins 1.14.0

  • Added notes about Jenkins API Tokens and Jenkins OAuth.

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.13.0

  • Added SVN repository based builds support for the GetChangeLog procedure.

EC-Jenkins 1.12.0

  • Support of Release Command Center 9.0 has been added.

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.

EC-Jenkins 1.7.3

  • Fixed issue with configurations being cached for IE.

EC-Jenkins 1.7.2

  • Renamed ElectricCommander to ElectricFlow.

EC-Jenkins 1.7.1

  • Fix formatting issues in help documentation

  • Fix bug where credentials were not being attached for all steps in the RunAndWait procedure.

  • Fix bug with https connection.

EC-Jenkins 1.6.1

  • The Get Status procedure now fails when the Jenkins build fails.

EC-Jenkins 1.5.0

  • The Build and Monitor Build procedure was added.

EC-Jenkins 1.3.0

  • The Import artifacts procedure was added.

EC-Jenkins 1.2.0

  • Additional postp matchers were added.

EC-Jenkins 1.1.0

  • Builds with args is now possible.

EC-Jenkins 1.0.0

  • Procedures:

    • Get Build Status

    • Get Build Log

    • Get Build Duration

    • Show Build Process (real-time)

    • Job Action

    • Server Status Report