×
Find plugins

IBM Cloud DevOps1.1.12Minimum Jenkins requirement: 2.7.1ID: ibm-cloud-devops

Installs: 46
Last released: 2 days ago
Maintainers
Xunrong Li
Vijay Aggarwal
Vijay Jegaselvan
Eric Jodet
Patrick Joy

Plugin Information

Plugin ID

ibm-cloud-devops

Changes

In Latest Release
Since Latest Release

Latest Release
Latest Release Date
Required Core
Dependencies

1.1.11 (archives)
Sep 29, 2017
2.7.1
credentials (version:2.1.1)
workflow-step-api (version:1.14)

Source Code
Issue Tracking
Pull Requests
Maintainer(s)

GitHub
Open Issues
Pull Requests
Xunrong Li (id: xunrongl)
Vijay Aggarwal (id: aggarwav)
Vijay Jegaselvan (id: imvijay2007)
Eric Jodet (id: ejodet)
Patrick Joy (id: patjoy)

Usage

Installations

2017-May 10
2017-Jun 29
2017-Jul 36
2017-Aug 41
2017-Sep 46

 

Value Proposition

This plugin lets you integrate Jenkins with IBM DevOps Insights. DevOps Insights tracks your deployment risk based on the test data that you publish to it. This test data may include unit tests, code coverage, functional verification tests, SonarQube data, and scan data from IBM Application Security on Cloud.  Once you publish this data, you can add gates to your pipelines so that you can stop builds that don't meet risk policies.

You can also use DevOps Insights to analyze your code repositories, which can yield valuable information about error-prone files, commit trends, and team dynamics.

Here is a view that shows deployment risk.  This view shows all builds that are in flight for a given Microservice and their deployment risk.  

 

Here is a view that shows deployment risk associated with various microservices that are deployed in an environment.

 

Here is a view that shows deployment risk details for a specific microservice and build.  At the top, the UI provides information about last commit for the build and link to Jenkins for that specific build.

Then, the UI can show details of a specific test as well.  In some cases, it will point to the original tool for details.

 

With this information on their fingertips, devops teams know which build is deployed in which environment, the quality of each build, link to commits and automated risk analysis based on the thresholds that an admin sets.   All stakeholders can have access to this information to view how their development teams are performing.

 

You can also view trends for unit test and functional verification tests for the builds that are deployed to a certain environment.  For example, you can see test trends for builds that went to production.  If some tests have been failing for builds that went to production, you may want to take some action.  Also, if number of tests are dwindling over time, that may also be a cause for concern.

 

You can also view code coverage trends for the builds that are deployed to a certain environment.  For example, you can see code coverage trends for builds that went to production.  Ideally, you should see that code coverage improve over time for builds that went to production.  If code coverage has been going down, you may want to take action.

 

You can also view deployment frequency trends for your production, staging or other environments.  This view also shows deployment success and failures.  You can click on a point of interest and see deployment details.  If yours is an agile team, you should see the deployment frequency trends go up.

 

You can also view build frequency trends for your long running branches.  This view also also shows build success and failures.  You can click on a point of interest and see build details.  If yours is an agile team, you should see a lot of daily builds on the integration branch.  Otherwise, your team is not merging their code frequently.

 

Supported Tools and Formats

We currently support the following test formats.

Type Formats
Unit Test xUnit, Mocha, KarmaMocha
Function Tests xUnit, Mocha, KarmaMocha
Code Coverage Cobertura, lcov, Istanbul
Static Security Scan IBM Application Security on Cloud
Dynamic Security Scan IBM Application Security on Cloud
Sonarqube Sonarqube

 

Connect with Us

For a demo and technical deep dive, please connect with Vijay Aggarwal via Linked In or via email.

High Level Integration Steps

At a high level, here are the integration steps.  These steps are described later in this document.

  • Create an IBM Bluemix account
  • Create a toolchain. Learn more about toolchains here.
  • Create promotion policies
  • Install the Jenkins plugin
  • Configure your Jenkins project to publish test results to DevOps Insights, automatically evaluate build quality at gates, and track your deployment risk.  A sample Jenkins project is herehttps://github.com/xunrongli-ibm/DemoDRA

The plugin provides post-build actions to support the integration. DevOps Insights aggregates and analyzes the results from unit tests, functional tests, code coverage tools, static security code scans, dynamic security code scans to determine whether your code meets predefined policies at gates in your deployment process. If your code does not meet or exceed a policy, the deployment is halted, preventing risky changes from being released. You can use DevOps Insights as a safety net for your continuous delivery environment, a way to implement and improve quality standards over time, and a data visualization tool to help you understand your project's health.

Sample Pipelines and Code

Here are two complete pipeline examples defined as declarative Jenkinsfile and a scripted Jenkinsfile  

This git repo contains a sample nodejs application code and tests, as well as a Jenkinsfile, you can play with it by simply forking this repo and modifying the Jenkinsfile to replace all the placeholder with your actual information. (Note: if you don't have NodeJS installed in your Jenkins environment, you might have to install the node.js Jenkins plugin. If you do have NodeJS installed, you can comment out the "tools" section in the Jenkinsfile)

Creating a Bluemix account

Go to IBM Bluemix to create a free account.  It will take you only a few minutes to create an account.

Creating a toolchain

Before you can integrate DevOps Insights with a Jenkins project, you must create a toolchain and add the DevOps Insights and Jenkins tools to it. 

First, create an empty toolchain that you can add the tools to. 

  1. Go to the Create a Toolchain page

  2. Under Other Templates, click the Build your own toolchain template.

  3. Name the toolchain and click Create

Next, add the DevOps Insights and Jenkins tools to your toolchain. 

  1. On the toolchain's Overview page, click Add a tool.

  2. Click the DevOps Insights tile, and then click Create Integration.
  3. On the toolchain's Overview page, click Add a tool again.
  4. Click the Jenkins tile. 
  5. Enter the name and URL for your existing Jenkins project. 
  6. Click Create Integration. 

You now have a toolchain that lets use DevOps Insights with Jenkins. 

Creating promotion policies

Policies are sets of rules that control the gates in your delivery pipeline. If your code does not meet or exceed a policy that is enacted at a particular gate, the deployment is halted to prevent risky changes from being released.

You define policies in DevOps Insights, rather than in Jenkins.

To open the DevOps Insights policy page: 

  1. Go to the Toolchains page in Bluemix.
  2. Click on a toolchain that uses DevOps Insights. 
  3. Click DevOps Insights.
  4. Click Settings, then click Policies.

 

From here, you can define policies, add rules to them, and then add them to gates in your Jenkins projects. 

For more information, see Creating policies and rules in the Bluemix documentation. 

 

Installing the plugin

Install this plugin via the Jenkins plugin manager
 

Integrating with Jenkins Pipeline

This plugin supports both declarative or scripted formats.  It also supports Jenkins jobs.

 

Exposing required environment variables

Next, open the pipeline definition.

In the definition, add the following environment variables. These variables are required for the pipeline to integrate with DevOps Insights.

Environment variable Definition

IBM_CLOUD_DEVOPS_CREDS

or

IBM_CLOUD_DEVOPS_API_KEY

IBM_CLOUD_DEVOPS_CREDS is for Bluemix username/password credentials that you define in Jenkins by using the credentials command. For example, IBM_CLOUD_DEVOPS_CREDS = credentials('BM_CRED'). Setting the variable with this command sets two additional environment variables automatically: IBM_CLOUD_DEVOPS_CREDS_USR and IBM_CLOUD_DEVOPS_CREDS_PSW for the user name and password, respectively.

IBM_CLOUD_DEVOPS_API_KEY is for Bluemix API key that you define in Jenkins by using the credentials command. For example, IBM_CLOUD_API_KEY = credentials('API_KEY'). To create an API key in Bluemix you can follow https://console.bluemix.net/docs/iam/apikeys.html#creating-an-api-key

IBM_CLOUD_DEVOPS_ORG The Bluemix organization that your toolchain belongs to.
IBM_CLOUD_DEVOPS_APP_NAME The name of the application that your toolchain deploys.

IBM_CLOUD_DEVOPS_TOOCLHAIN_ID

Optional: The ID of your toolchain. Open the toolchain Overview and see the URL to determine the ID. The toolchain URL format is https://console.ng.bluemix.net/devops/toolchains/[YOUR_TOOLCHAIN_ID].

Tip: See the Jenkins pipeline documentation for more information about the credentials command.

Tip: If you are using the the scripted pipeline format, set your credentials with withCredentials and your environment with withEnv instead of credentials and environment, which are used in the example below. See the Jenkins documentation for more about withCredentials.

 

These environment variables and credentials are used by the IBM Cloud DevOps plugin to interact with DevOps Insights. Here is an example of setting them in the declarative pipeline format.

environment {
        IBM_CLOUD_DEVOPS_CREDS = credentials('BM_CRED')
        IBM_CLOUD_DEVOPS_ORG = 'dlatest'
        IBM_CLOUD_DEVOPS_APP_NAME = 'Weather-App'
        IBM_CLOUD_DEVOPS_TOOLCHAIN_ID = '1111111-aaaa-2222-bbbb-333333333'
        IBM_CLOUD_DEVOPS_WEBHOOK_URL = 'https://jenkins:5a55555a-a555-5555-5555-a555aa55a555:55555555-5555-5555-5555-555555555555@devops-api.ng.bluemix.net/v1/toolint/messaging/webhook/publish' //Optional
    }

Adding Cloud DevOps steps

The Cloud DevOps plugin adds four steps to Jenkins pipelines for you to use. Use these steps in your pipelines to interact with DevOps Insights.

  • publishBuildRecord, which publishes build information to DevOps Insights
  • publishTestResult, which publishes test results to DevOps Insights
  • publishDeployRecord, which publishes deployment records to DevOps Insights
  • evaluateGate, which enforces DevOps Insights policies

Add these steps to your pipeline definition wherever you need them to run. For example, you might upload test results after running a test, and then evaluate those results at a gate after they are uploaded.

Tip: by default, the version number is set to be {pipeline name}:{build number}, you can also set the custom version number in each step

Publishing build records

Publish build records with the publishBuildRecord step. This step requires four parameters. It can also accept one optional parameter.

Parameter Definition
gitBranch The name of the Git Branch that the build uses.
gitCommit The Git commit ID that the build uses.
gitRepo The URL of the Git repository.
result The result of the build stage. The value should be SUCCESS or FAIL.
buildNumber
Optional: Set value to any string - this represents version number

Here are the parameters in an example command:

publishBuildRecord gitBranch: "${GIT_MASTER}", gitCommit: "${GIT_COMMIT}", gitRepo: "https://github.com/username/reponame", result:"SUCCESS" 

Tip: Jenkins Pipeline does not expose Git information as environment variables. You can get the Git commit ID by using the command sh(returnStdout: true, script: 'git rev-parse HEAD').trim().

 

Publishing test results

 

Publish build records with the publishTestResult step. This step requires two parameters. It can also accept one optional parameter.

 

Parameter Definition
type The type of test result. The value of this must be unittest for unit tests, fvt for functional verification tests, code for code coverage tests, staticsecurityscan for static security scan result, dynmaicsecurityscan for dynamic security scan,
fileLocation The test result file's location.
environment
The environment name that your test runs on, only required for fvt (functional verification tests)
buildNumber
Optional: Set value to any string - this represents version number

 

 

Here are the parameters in example commands. The first command publishes Mocha unit test results, and the second command publishes code coverage test results.

publishTestResult type:'unittest', fileLocation: './mochatest.json'
publishTestResult type:'code', fileLocation: './tests/coverage/reports/coverage-summary.json'
publishTestResult type:'fvt', fileLocation: './mochafvt.json', environment: 'STAGING'
publishTestResult type:'staticsecurityscan', fileLocation: './static-result.xml'
publishTestResult type:'dynamicsecurityscan', fileLocation: './dynamic-result.xml'

 

 

Publishing SonarQube results

After you configure a SonarQube scanner and server by following the instructions in the SonarQube docs, you can publish scan results to DevOps Insights.

To configure your Jenkins Pipeline to accept these results, add the following three required parameters and one optional parameter to it:

 

Parameter Definition
SQHostURL The host portion of your SonarQube scanner's URL. Get this from from your SonarQube server.
SQAuthToken
Your SonarQube API authentication token. Get this from your SonarQube server.
SQProjectKey
The project key of the SonarQube project you wish to scan.
buildNumber
Optional: Set value to any string - this represents version number

 

Here are the SonarQube parameters used in a sample stage:

stage ('SonarQube analysis') {
    steps {
        script {
            def scannerHome = tool 'Default SQ Scanner';
            withSonarQubeEnv('Default SQ Server') {
               
                env.SQ_HOSTNAME = SONAR_HOST_URL;
                env.SQ_AUTHENTICATION_TOKEN = SONAR_AUTH_TOKEN;
                env.SQ_PROJECT_KEY = "My Project Key";
                
                run SonarQube scan ...
            }
        }
    }
}
stage ("SonarQube Quality Gate") {
     steps {
        ...
     }
     post {
        always {
            publishSQResults SQHostURL: "${SQ_HOSTNAME}", SQAuthToken: "${SQ_AUTHENTICATION_TOKEN}", SQProjectKey:"${SQ_PROJECT_KEY}"
        }
     }
}


Publishing deployment records

 

Publish deployment records with the publishDeployRecord step. This step requires two parameters. It can also accept two optional parameter.

 

Parameter Definition
environment The environment that you deploy your app to. For example, "DEV" or "STAGING" or any other value
result The result of the build stage. The value should be SUCCESS or FAIL.
appUrl Optional: The URL used to access your application.
buildNumber
Optional: Set value to any string - this represents version number

 

 

Here are the parameters in example commands. The first command publishes the deployment record for a staging environment; the second command publishes the deployment record for a production environment.

publishDeployRecord environment: "STAGING", appUrl: "http://staging-Weather-App.mybluemix.net", result:"SUCCESS"
publishDeployRecord environment: "PRODUCTION", appUrl: "http://Weather-App.mybluemix.net", result:"SUCCESS"

 

Adding gates

 

Add gates to your pipeline by using the evaluateGate command. Gates enforce DevOps Insights policies, which set test requirements for build promotion.

 

This step requires one parameters. It can also accept two optional parameter.

 

Parameter Definition
policy The name of the policy that the gate implements. The policy's name is defined in DevOps Insights.
forceDecision
Optional: Whether or not the pipeline stops depending on the gate's decision. Set this parameter to true to stop the pipeline from running if the gate fails. Set it to false to allow the pipeline to continue after a gate failure. By default, the value is false.
buildNumber
Optional: Set value to any string - this represents version number

 

 

Here are the parameters in an example command. In this command, the pipeline will continue running regardless of the gate's decision.

evaluateGate policy: 'Weather App Policy', forceDecision: 'true'

 

Communicating with toolchains

 

Send pipeline status to Bluemix toolchains by using the notifyOTC command. To learn more about integrating Jenkins with toolchains, see Notifying tool chains section below. 

This step requires two parameters and can take an additional optional one.

 

Parameter Definition
stageName The current pipeline stage's name.
status The current pipeline stage's status. Using SUCCESSFAILURE, or ABORTED will automatically trigger color highlighting in Slack.
webhookUrl Optional: The webhook URL that is shown on your toolchain's Jenkins tile. If you include this parameter, its value overrides that of the IBM_CLOUD_DEVOPS_WEBHOOKURL environment variable.

 

 

Here are examples of using the notifyOTC step in both declarative and scripted pipeline definitions:

 

notifyOTC stageName: "Deploy", status: "SUCCESS"

 

 

Integrating with freeform Jenkins projects

Configuring Jenkins jobs for the Deployment Risk dashboard

After the plugin is installed, you can integrate DevOps Insights into your Jenkins project.

Follow these steps to use Deployment Risk's gates and dashboard with your project.

  1. Open the configuration of any jobs that you have, such as build, test, or deployment.

  2. Add a post-build action for the corresponding type:

    • For build jobs, use Publish build information to IBM Cloud DevOps.

    • For test jobs, use Publish test result to IBM Cloud DevOps.

    • For SonarQube jobs, use Publish SonarQube test result to IBM Cloud DevOps.
    • For deployment jobs, use Publish deployment information to IBM Cloud DevOps.

  3. Complete the required fields. These will vary depending on job type.

    • From the Credentials list, select your Bluemix ID and password. If they are not saved in Jenkins, click Add to add and save them. Test your connection with Bluemix by clicking Test Connection.

    • In the Build Job Name field, specify your build job's name exactly as it is in Jenkins. If the build occurs with the test job, leave this field empty. If the build job occurs outside of Jenkins, select the Builds are being done outside of Jenkins check box and specify the build number and build URL.

    • For the environment, if the tests are running in build stage, select only the build environment. If the tests are running in the deployment stage, select the deploy environment and specify the environment name. Two values are supported: STAGING and PRODUCTION.

    • For the Result File Location field, specify the result file's location. If the test doesn't generate a result file, leave this field empty. The plugin uploads a default result file that is based on the status of current test job.

    • For the SonarQube hostname and SonarQube authentication token fields, specify the hostname and token that are configured on your SonarQube Server. For the SonarQube project key field, specify the project key of the SonarQube project that you wish to scan. 

    These images show example configurations:

Publish build information

Publish test result

Publish SonarQube test result

Publish deployment information


4. If you want to use DevOps Insights policy gates to control a downstream deployment job, add a post-build action, IBM Cloud DevOps Gate. Choose a policy and specify the scope of the test results. To allow the policy gates to prevent downstream deployments, select the Fail the build based on the policy rules check box. The following image shows an example configuration:

 

5. Run your Jenkins Build job.

6. View the Deployment Risk dashboard by going to IBM Bluemix DevOps, selecting your toolchain, and clicking DevOps Insights.

 

The Deployment Risk dashboard relies on the presence of a gate after a staging deployment job. If you want to use the dashboard, make sure that you have a gate after you deploy to the staging environment, but before you deploy to a production environment.

 

Notifying toolchains

You can configure your Jenkins jobs to send notifications to tools integrated to your toolchain (e.g., Slack, PagerDuty), and use traceability to track code deployments through tags, labels, and comments in your Git repository (repo).

 

Both Freestyle projects and Pipeline are supported.

Prerequisites

Create a toolchain

Refer to Bluemix documentation in order to create a tool chain  that will integrate your Jenkins server to other tools such as Github, Insights, Slack and PagerDuty. 

Jenkins Webhook URL

  1. On your tool chain main page, click the 3 dots in top top right corner of the Jenkins tile, and select configure.
  2. Take note - copy / paste it in a notepad - of the Generated toolchain webhook URL. Webhook URL uses a format like:
    https://jenkins:c3cd97bc-b987-43bd-8020-c14bd1b1366a:8996de45-380a-40b2-a099-65a6eeb9a466@devops-api.ng.bluemix.net/v1/toolint/messaging/webhook/publish

Add bluemix credentials to Jenkins

This configuration step is common to both Freestyle or Pipeline projects.

  1. On the Manage Jenkins page, select Manage Credentials
  2. Scope: global
  3. Username: your bluemix user id
  4. Password: corresponding password
  5. ID: IBM_CLOUD_DEVOPS_CREDS
  6. (optional) Description: Bluemix creds
  7. Save your changes

These credentials will be used in Freestyle or Pipeline jobs using the credentials ID.

 

Freestyle job

  1. Create a new Freestyle project
  2. Select "This project is parameterized".
  3. Add the String following parameters:

    Name Default Value
    IBM_CLOUD_DEVOPS_ORG the bluemix org where your application is deployed
    IBM_CLOUD_DEVOPS_SPACE the bluemix space where your application is deployed
    IBM_CLOUD_DEVOPS_APP_NAME the name of your application as deployed to bluemix
    IBM_CLOUD_DEVOPS_WEBHOOK_URL the Jenkins webhook URLof your toolchain

  4. Source Code Management: select Git, and enter the URL and branch of the Git repository as configured in your toolchain.


  5. Build triggers: select Poll SCM in order to start job automatically after a Git commit. Enter your schedule options.


  6. Build Environment
    - Select Use secret text(s) or file(s)
    - Add Username and password (separated)
    - Username Variable: IBM_CLOUD_DEVOPS_CREDS_USR
    - Password Variable: IBM_CLOUD_DEVOPS_CREDS_PSW
    - Credentials: select the bluemix specific credentials you added to Jenkins server 


  7.  Build step is not detailed here, as the script deploying your application to bluemix might be specific to your environment.
     Below is a simple sample Shell script example that pushes your application to bluemix. 

    cf api https://api.ng.bluemix.net
    cf login -u $IBM_CLOUD_DEVOPS_CREDS_USR -p $IBM_CLOUD_DEVOPS_CREDS_PSW -o $IBM_CLOUD_DEVOPS_ORG -s $IBM_CLOUD_DEVOPS_SPACE
    cf push $IBM_CLOUD_DEVOPS_APP_NAME -n $IBM_CLOUD_DEVOPS_APP_NAME
  8. Post-build action: add the Notify OTC post-build action.
  9. Select the options matching your needs:
    - Notify Slack on Job started, completed or finalized events,
    - Notify PagerDuty on Job faliures only
    - Select Track deployment of code changes to enable traceability to track code deployments through tags, labels, and comments in your Git repository.


  10. Save your changes.
  11. You may test your Freestyle job by either:
    - Jenkins: select "Build with parameters" and launch a build.
    - Git: commit some changes and wait for SCM polling (if enabled) to pick up the changes and launch a build.

 

Pipeline

  1. Create a new Pipeline.
  2. Deployment script is not detailed here. To use IBM Cloud DevOps with the Jenkins pipeline project, you can follow the declarative or scripted jenkinsfile.

Publish the status of your pipeline stages to your Bluemix Toolchain

Configure your Jenkins pipelines to send notifications to tools integrated to your Bluemix Toolchain (e.g. Slack, PagerDuty).

  • Ensure you added the 5 required environment variables to your script, as detailed here.

    environment {
    	IBM_CLOUD_DEVOPS_CREDS = credentials('IBM_CLOUD_DEVOPS_CREDS')
    	IBM_CLOUD_DEVOPS_ORG = 'dlatest'
    	IBM_CLOUD_DEVOPS_APP_NAME = 'Weather-V1'
    	IBM_CLOUD_DEVOPS_TOOLCHAIN_ID = '1320cec1-daaa-4b63-bf06-7001364865d2'       
    	IBM_CLOUD_DEVOPS_WEBHOOK_URL =
    'https://jenkins:5a55555a-a555-5555-5555-a555aa55a555:55555555-5555-5555-5555-555555555555@devops-api.ng.bluemix.net/v1/toolint/messaging/webhook/publish'
    }
  • Use the notifyOTC command
  • (required) stageName - the name of the current pipeline stage.
  • (required) status - the completion status of the current pipeline stage. ('SUCCESS', 'FAILURE', and 'ABORTED' will be augmented with color)
  • (optional) webhookUrl - the webhook obtained from the Jenkins card on your toolchain.
  • Declarative Pipeline Example:

    stage('Deploy') {
        steps {
          ...
        }
        post {
            success {
                notifyOTC stageName: "Deploy", status: "SUCCESS"
            }
            failure {
                notifyOTC stageName: "Deploy", status: "FAILURE"
            }
        }
    }

Track deployment of code changes

Configure your Jenkins pipelines to send deployable mapping messages to your Bluemix Toolchain,
to track code deployments through tags, labels, and comments in your Git repository.

Use this notification only for status 'SUCCESS'. Any other status will be discarded.

  • Add a new environment variable to your script:
    IBM_CLOUD_DEVOPS_SPACE: the bluemix space where your application is deployed

    environment {
    	IBM_CLOUD_DEVOPS_CREDS = credentials('IBM_CLOUD_DEVOPS_CREDS')
    	IBM_CLOUD_DEVOPS_ORG = 'dlatest'
     	IBM_CLOUD_DEVOPS_SPACE= 'production'
    	IBM_CLOUD_DEVOPS_APP_NAME = 'Weather-V1'
    	IBM_CLOUD_DEVOPS_TOOLCHAIN_ID = '1320cec1-daaa-4b63-bf06-7001364865d2'       
    	IBM_CLOUD_DEVOPS_WEBHOOK_URL =
    'https://jenkins:5a55555a-a555-5555-5555-a555aa55a555:55555555-5555-5555-5555-555555555555@devops-api.ng.bluemix.net/v1/toolint/messaging/webhook/publish'
    }
  • Use the sendDeployableMessage command
  • (required) status - the completion status of the current pipeline stage: 'SUCCESS'
  • (optional) webhookUrl - the webhook obtained from the Jenkins card on your toolchain.
  • Declarative Pipeline Example:

    stage('Deploy') {
        steps {
          ...
        }
        post {
            success {
                notifyOTC stageName: "Deploy", status: "SUCCESS"
    			sendDeployableMessage status: "SUCCESS"
            }
            failure {
                notifyOTC stageName: "Deploy", status: "FAILURE"
            }
        }
    }



Change Log

Version 1.0 (May 16th, 2017)

  • First release.

Version 1.0.1 (May 17th, 2017)

  • Updated description.

Version 1.0.2 (May 25th, 2017)

  • Fixed URL encoding issue

Version 1.0.3 (June 2nd, 2017)

  • Fixed URL encoding issue for policy dropdown list
  • Minor text fix in error message

Version 1.1.0 (June 08, 2017)

  • Added Notifying toolchains section

Version 1.1.2 (July 17, 2017)

  • Support custom build number 

Version 1.1.3 (July 19, 2017)

  • Change minimum required Jenkins version

Version 1.1.4 (July 24, 2017)

  • Change environment settings to be one single global configuration for all steps

Version 1.1.5 (July 28, 2017)

  • Throw warnings instead of errors when fails to get Jenkins root url

Version 1.1.6 (Aug 10, 2017)

  • Show missing required environment variables in error logs
  • Fix upload SonarQube result

Version 1.1.7 (Sep 6, 2017)

  • Support log in using Bluemix API Key in the pipeline 
  • Support lcov format for code coverage results

Version 1.1.8 (Sep 13, 2017)

  • Support environment variables for application name, org name in freestyle jobs

Version 1.1.10 (Sep 19, 2017)

  • fix bug on uploading SonarQube result

Version 1.1.11 (Sep 29, 2017)

  • Support Non-ASCII characters as Jenkins job name

Version 1.1.12 (Oct 19, 2017)

  • Support upload security scan results

 

ArchivesGet past versions
Labels
This plugin has no labels