{"_id":"grunt-idra3","_rev":"218-0282ab1079b3419a4f8455d6efb44446","name":"grunt-idra3","time":{"modified":"2022-06-18T15:12:39.940Z","created":"2016-03-03T15:35:29.610Z","0.0.1":"2016-03-03T15:35:29.610Z","0.0.2":"2016-03-03T16:53:59.663Z","0.0.3":"2016-03-03T23:26:48.394Z","0.0.4":"2016-03-09T16:23:49.967Z","0.0.5":"2016-03-14T20:46:57.345Z","0.0.6":"2016-03-14T21:25:19.066Z","0.0.7":"2016-03-15T20:25:45.301Z","0.0.8":"2016-03-15T21:41:09.428Z","0.0.9":"2016-03-16T16:57:02.603Z","0.0.10":"2016-03-18T15:40:28.353Z","0.0.11":"2016-03-22T14:43:56.125Z","0.0.12":"2016-03-22T16:07:18.975Z","0.0.13":"2016-03-23T16:23:48.209Z","0.0.14":"2016-04-06T16:46:44.814Z","0.0.15":"2016-04-12T19:35:18.431Z","0.0.16":"2016-04-12T21:45:20.118Z","0.0.17":"2016-04-13T20:14:55.719Z","0.0.18":"2016-04-18T16:41:36.373Z","0.0.19":"2016-04-18T19:49:20.967Z","0.0.20":"2016-04-19T16:41:52.557Z","0.0.21":"2016-04-19T22:49:45.797Z","0.0.22":"2016-04-21T17:08:11.119Z","0.0.23":"2016-04-22T19:31:44.918Z","0.0.24":"2016-04-28T19:02:22.289Z","0.0.25":"2016-05-04T15:00:36.337Z","0.0.26":"2016-05-04T16:47:50.092Z","0.0.27":"2016-05-04T20:07:29.321Z","0.0.28":"2016-05-04T21:56:41.630Z","0.0.29":"2016-05-05T19:23:10.937Z","0.0.30":"2016-05-06T19:13:30.056Z","0.0.31":"2016-05-16T19:52:07.429Z","0.0.32":"2016-05-20T16:37:01.672Z","0.0.33":"2016-05-23T21:50:20.146Z","0.0.34":"2016-05-24T17:07:31.078Z","0.0.35":"2016-05-26T17:20:42.575Z","0.0.36":"2016-05-26T17:42:37.348Z","0.0.37":"2016-05-26T18:50:57.096Z","0.0.38":"2016-06-09T15:27:29.027Z","0.0.39":"2016-10-17T23:12:51.550Z","0.0.40":"2016-10-17T23:44:02.263Z","0.0.41":"2016-10-20T17:04:27.115Z","0.0.42":"2016-10-31T17:03:33.877Z","0.0.43":"2016-11-04T21:42:49.775Z","0.0.44":"2017-01-30T21:08:17.436Z","0.0.45":"2017-01-31T17:16:02.344Z","0.0.46":"2017-02-02T16:19:07.867Z","0.0.47":"2017-02-02T17:09:04.585Z","0.0.48":"2017-02-04T18:00:14.112Z","0.0.49":"2017-02-06T15:57:37.660Z","0.0.50":"2017-02-06T17:17:03.336Z","0.0.51":"2017-02-10T22:15:41.992Z","0.0.52":"2017-02-10T22:35:31.197Z","0.0.53":"2017-02-13T15:40:58.563Z","0.0.54":"2017-02-22T21:42:26.153Z","0.0.55":"2017-02-23T16:16:27.087Z","0.0.56":"2017-03-03T21:16:22.116Z","0.0.57":"2017-03-07T20:45:58.095Z","0.0.58":"2017-05-10T18:05:37.739Z","0.0.59":"2017-05-31T21:18:20.981Z","0.0.60":"2017-06-28T21:58:53.353Z","0.0.61":"2017-06-29T19:10:26.242Z","0.0.62":"2017-07-25T21:50:47.071Z","0.0.63":"2017-07-25T23:01:35.276Z","0.0.64":"2017-07-26T15:01:15.098Z","0.0.65":"2017-07-26T15:26:32.618Z","0.0.66":"2017-07-26T16:54:02.202Z","0.0.67":"2017-07-26T17:59:19.124Z","0.0.68":"2017-07-27T16:09:47.445Z","0.0.69":"2017-07-27T18:28:51.541Z","0.0.70":"2017-07-27T20:20:38.661Z","0.0.71":"2017-07-27T22:51:49.310Z","0.0.72":"2017-07-28T17:36:03.648Z","0.0.73":"2017-07-28T21:59:29.724Z","0.0.74":"2017-07-31T16:53:32.671Z","0.0.75":"2017-08-01T18:55:34.933Z","0.0.76":"2017-08-03T16:00:11.540Z","0.0.77":"2017-08-03T18:34:05.911Z","0.0.78":"2017-08-04T16:36:29.471Z","0.0.79":"2017-08-04T19:44:10.342Z","0.0.80":"2017-08-09T19:57:13.557Z","0.0.81":"2017-08-25T16:36:38.125Z","0.0.82":"2017-09-05T16:40:55.191Z","0.0.83":"2017-09-08T17:35:36.662Z","0.0.84":"2017-09-13T16:14:11.076Z","0.0.85":"2017-09-18T21:33:34.374Z","0.0.86":"2017-10-09T17:24:21.973Z","0.0.87":"2017-10-24T17:47:02.662Z","0.0.88":"2017-10-24T22:41:47.415Z","0.1.0":"2017-11-08T22:50:10.252Z","0.1.1":"2017-11-08T23:05:10.687Z","0.1.2":"2017-11-13T23:09:27.814Z","0.1.3":"2017-11-17T22:19:11.112Z","0.1.4":"2017-12-19T19:01:17.030Z","0.1.5":"2018-01-16T13:22:58.209Z","0.1.6":"2018-01-16T13:45:13.074Z","0.1.7":"2018-01-17T15:47:13.319Z","0.1.8":"2018-01-25T20:52:31.214Z","0.1.9":"2018-01-25T23:59:26.781Z","0.1.10":"2018-01-26T01:30:31.262Z","0.1.11":"2018-01-29T20:47:24.064Z","0.1.12":"2018-01-30T14:04:26.739Z","0.1.13":"2018-02-13T00:40:08.620Z","0.1.14":"2018-02-23T21:22:32.224Z","0.1.15":"2018-02-27T18:32:39.806Z","0.1.16":"2018-04-10T20:25:41.905Z","0.1.17":"2018-04-12T15:59:17.894Z","0.1.18":"2018-04-12T23:17:09.032Z","0.1.19":"2018-04-18T20:59:29.759Z","0.1.20":"2018-05-03T19:00:39.089Z","0.1.21":"2018-06-08T17:15:06.383Z","0.1.22":"2018-06-08T19:07:25.011Z","0.1.23":"2018-06-20T20:30:37.949Z","0.1.24":"2018-06-21T16:41:27.947Z","0.1.25":"2018-07-13T21:44:21.354Z","0.1.26":"2018-08-03T19:50:13.569Z","0.1.27":"2018-08-07T21:59:24.462Z","0.1.28":"2018-08-14T18:27:05.617Z","0.1.29":"2018-08-14T20:13:53.843Z","0.1.30":"2018-08-21T19:59:25.529Z","0.1.31":"2018-09-17T21:33:09.321Z","0.1.34":"2018-09-27T15:47:12.642Z","0.1.35":"2018-09-27T15:59:32.370Z","0.1.36":"2018-10-27T21:11:05.150Z","0.1.37":"2018-10-27T21:35:32.831Z","0.1.38":"2019-01-09T16:42:56.017Z","0.1.39":"2019-01-09T23:02:05.638Z","0.1.40":"2019-02-21T21:31:57.001Z","0.1.41":"2019-03-11T15:41:24.781Z","0.1.42":"2019-03-12T19:21:11.016Z","0.1.43":"2019-03-21T21:03:05.609Z","0.1.45":"2019-03-21T22:56:04.237Z","0.1.46":"2019-04-12T21:53:57.937Z","0.1.47":"2019-04-29T22:25:04.349Z","0.1.48":"2019-04-30T21:31:32.470Z","0.1.49":"2019-04-30T23:19:07.775Z","0.1.50":"2019-05-01T20:36:30.400Z","0.1.51":"2019-06-11T17:51:25.206Z","0.1.52":"2019-06-16T20:13:52.908Z","0.1.53":"2019-06-19T22:02:13.427Z","0.1.54":"2019-06-20T19:47:03.865Z","0.1.55":"2019-06-24T18:02:53.885Z","0.1.57":"2019-09-23T16:32:29.488Z","0.1.58":"2020-09-09T18:07:15.931Z","0.1.59":"2020-09-24T20:27:54.833Z"},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"dist-tags":{"latest":"0.1.59","dev":"0.1.59"},"description":"Grunt Plugin for IBM DevOps Insights","readme":"# idra\n\n> Command Line utility for integrating with IBM® DevOps Insights\n\nTo install this utility\n```\nnpm install -g grunt-idra3\n```\n\n# Table of Contents\n1. [Concepts](#concepts)\n2. [Getting Started](#getting-started)\n 1. [Scenarios](#scenarios)\n 2. [Prerequisites](#prerequisites)\n 3. [Environment Variables](#environment-variables)\n 4. [Enabling Debug Logs](#enabling-debug-logs)\n 5. [Using the CLI](#using-the-cli)\n3. [Upload Build Records](#upload-build-records)\n4. [Upload Test Results](#upload-test-results)\n 1. [Upload SonarQube Results](#upload-sonarqube-results)\n5. [Upload Deployment Records](#upload-deployment-records)\n6. [Making decisions about build quality using gate policies](#making-decisions-about-build-quality-using-gate-policies)\n\n## Concepts\nIBM® DevOps Insights is a tool that provides insights into your DevOps projects. Use it to learn how compliant your team is with DevOps and developer practices, to manage risk in your codebase, and to automatically enforce quality standards in continuous delivery projects.\n\nUnderstanding of the following concepts will help in faster adoption of IBM® DevOps Insights for your projects.\n\n##### Toolchain\nToolchains are part of [IBM® DevOps Continuous Delivery](https://console.bluemix.net/docs/services/ContinuousDelivery/cd_overview.html#cd_overview). Toolchains provide an integrated set of tools to build, deploy and manage your apps. You can create toolchains that include IBM Cloud services, open source tools, and third party tools that make development and operations repeatable and easier to manage. It is required that the IBM DevOps Insights should be added as one of the tool to your toolchain.\n\n##### Integrating your build tool with IBM DevOps Insights\nThis means instrumenting your build tool with this CLI or DevOps Insights Jenkins plugin to send build, test and deployment records to IBM DevOps Insights.\n\n##### Build record\nIBM DevOps Insights needs to know when a build is complete. This record contains application name, branch, build id, reference to git repo and other fields. This CLI and Jenkins plugin has a command to publish the build record to DevOps Insights.\n\n##### Test record\nIBM DevOps Insights needs to know about the tests performed during the build process. It is necessary that the tests should generate some kind of JSON or XML based file. Here are the list of supported [format](supported-test-formats). The generated test file is published as a test record. Along with the test file this record contains application name, build id, type of tests and other fields. It is required that the application name and build id in the test record matches the one used in the build record for a given build. This CLI and Jenkins plugin has a command to publish test record to DevOps Insights.\n\n##### Deployment records\nIBM DevOps Insights needs to know about the deployments made during the deployment process. This record contains the application name, build id, environment name, status of the deployment and other fields. It is required that the application name and build id in the deployment record matches the one used in the build record for a given build. This CLI and Jenkins plugin has a command to publish a deployment to DevOps Insights.\n\n##### Build Id (or Number)\nThis is an arbitrary length string uniquely identifying each build. This id is used to tie the build, test and deployment records together so it is important to publish those records with the same id for a given build.\n\n##### Policy\nA policy is set of rules specified by the user that collectively defines what is considered a good set of test records for a given application build. Typically, one rule is added for each test record published to DevOps Insights. The policy rules are evaluated by the gate.\n\n##### Branch\nThis is the name of the branch in the source control system.\n\n##### Environment\nThis is the name of environment to which deployments are made during the build process.\n\n##### Data set\nThis is an arbitrary string that identifies the type of tests performed during the build process. Besides the standard names such as \"unit test\", \"fvt\". The tool allows the user to define a custom name.\n\n## Getting Started\n\nUse this utility to integrate IBM® DevOps Insights with Travis CI, Concourse, IBM Urban Code Deploy, IBM Continuous Delivery Pipelines and other CI/CD tools. If you are using Jenkins, use this [Jenkins plugin](https://plugins.jenkins.io/ibm-cloud-devops) instead.\n\nUsing this utility, you can\n - Publish build records, test records and deploy records to IBM® DevOps Insights \n - Make go/no-go decisions about a build's quality by using a Gate policy\n\nFor samples of dashboards in IBM® DevOps Insights, see [Value Proposition](https://plugins.jenkins.io/ibm-cloud-devops).\n\nFor more information about IBM DevOps Insights, see [the official documentation](https://console.bluemix.net/docs/services/DevOpsInsights).\n\n### Scenarios\nThis document covers two scenarios:\n1. You are integrating DevOps Insights with IBM Continuous Delivery tool.\n2. You are integrating DevOps Insights with other CI/CD tools (e.g., Travis CI, Concourse, IBM Urban Code Deploy, others)\n\n### Prerequisites\n\nTo use the CLI, you need to do the following. These steps should take about 10 minutes.\n\n1. A valid IBM Cloud account. If you don't have one, [register here](https://console.bluemix.net/registration).\n\n2. Once you have an account, you can create an API Key. Log in to [IBM Cloud](https://console.bluemix.net). Click on **Manage**->**Security**->**Platform API Key**. On that screen, create an API Key.\n\n3. An IBM Continuous Delivery toolchain. To create a toolchain:\n - Go to https://console.bluemix.net/devops\n - Click on **Create a Toolchain** button and then select **Build Your Own Toolchain** template. \n - In the next screen, click **Create**.\n - From the URL displayed in the browser, make note of your toolchain id. For example, if your URL is https://console.bluemix.net/devops/toolchains/05572df3-01dc-441b-911d-b2202fe33f96, the toolchain id is the long string after **toolchains/**\n - You can always navigate to your toolchain by [clicking here](https://console.bluemix.net/devops)\n\n4. Add DevOps Insights tool to your toolchain\n - Go to your toolchain\n - Click on **Add a Tool** button\n - Select DevOps Insights tool and click **Create Integration** button\n\n5. Your CI/CD tool must have Node.js® 4.x or greater.\n\n### Environment Variables\n\nIf you are using Travis, Concourse or any CI/CD tool other than the IBM Continuous Delivery pipeline, then set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|TOOLCHAIN_ID| **Required.** The toolchain's GUID |\n|IBM_CLOUD_API_KEY| **Required.** The Bluemix user's Api key|\n|BUILD_NUMBER| **Required.** Any string that identifies the build. You also have the option of specifying build number using the `--buildnumber` parameter, in which case this environment variable is not required. |\n|LOGICAL_APP_NAME| **Required.** The application's name. You also have the option of specifying application's name using the `--logicalappname` parameter, in which case this environment variable must not be set. It is an error to set both the environment variable and the parameter.|\n\nIf you are using IBM Continuous Delivery pipeline, you need to set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|IBM_CLOUD_API_KEY| **Required** The Bluemix user's Api key|\n|BUILD_PREFIX| **Required.** Any string. For example, the Git branch name. If the `--buildnumber` parameter is used to pass a build number then this environment variable is not required.|\n|LOGICAL_APP_NAME| **Required.** The application's name. You also have the option of specifying application's name using the `--logicalappname` parameter, in which case this environment variable must not be set. It is an error to set both the environment variable and the parameter.|\n|PATH|**Required.** In order to have required version of Node.js in your path, set the PATH variable before invoking the utility: `export PATH=/opt/IBM/node-v4.2/bin:$PATH`|\n\nIf you are using IBM Continuous Delivery pipeline and if you want to publish Insights data to another toolchain, then set the following environment variables. \n\n|Name|Description|\n|-----|-----|\n|TOOLCHAIN_ID| **Required.** The target toolchain's GUID. If the target toolchain is owned by different user then provide the target toolchain owner's Bluemix Api key in the `IBM_CLOUD_API_KEY` variable.|\n\n\nIf you are using IBM UrbanCode Deploy, DevOps Insights relies on the previous set of variables, and this one:\n\n|Name|Description|\n|-----|-----|\n|UCD_REQUEST_ID| This maps to the ${p:request.id} property value. |\n\n### Enabling Debug logs\nIf you want to enable debug logs for the DevOps Insights CLI, set the `IDRA_DEBUG` environment variable to `true`. This works in all environments.\n\n|Name|Description|\n|-----|-----|\n|IDRA_DEBUG| When this value is `true`, the DevOps Insights CLI's debugging mode is enabled. By default, the value is `false`. |\n\n\n### Using the CLI\n\nSet [environment details](#environment-details) as described above. Ensure that Node.js 4.2 or higher is avaialble in your CI/CD tool.\n\nTo install this utility, use `npm install -g grunt-idra3`\n\nThen you can invoke the CLI with the `idra` command. You can run the CLI in any pipeline job's command script. For example, this command uploads functional verification test results to DevOps Insights:\n\n```\n# Upload test results\nidra --publishtestresult --filelocation=\"results.json\" --type=fvt\n```\n\n\n## Upload Build Records\nUse the `--publishbuildrecord` command (alias `-b`) to upload build records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishbuildrecord --branch= --repositoryurl= --commitid= --status= --logicalappname= --buildnumber= [--joburl=] [--buildnumber=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--branch`|`-B` | **Required.** The repository branch on which the build is being performed. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--repositoryurl`|`-R` | **Required.** The url of the git repository. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--commitid`|`-C` | **Required.** The git commit id. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--status`|`-S` | **Required.** The build status. This value must be either `pass` or `fail`. |\n|`--logicalappname`|`-L` | _Optional_. The application's name. If this parameter is specified, environment variable **LOGICAL_APP_NAME** must not be set. |\n|`--buildnumber`|`-N` | _Optional_. Any string that identifies the build. This option overrides the value provided by **BUILD_NUMBER** or **BUILD_PREFIX** environment variables. |\n|`--joburl`|`-J` | _Optional_. The URL to the job's build logs. |\n\n\n\n### An example command\n\nIn this an example, the command uploads a build record from a pipeline job.\n\n```shell\nidra --publishbuildrecord --branch=master --repositoryurl=\"https://github.com/oic/dlms.git\" --commitid=dff7884b9168168d91cb9e5aec78e93db0fa80d9 --status=pass --logicalappname=appname --buildnumber=release:17\n```\n\n## Upload Test Results\n\nUse the `--publishtestresult` command (alias `-p`) to upload results from these test types to DevOps Insights:\n\n* Unit tests\n* Code coverage tests\n* Functional verification tests (FVT)\n* Static security scans from IBM Application Security on Cloud\n* Dynamic app scans from IBM Application Security on Cloud\n* [SonarQube results](#upload-sonarqube-results)\n* [Vulnerability Advisor](https://cloud.ibm.com/docs/services/va)\n\n\n### Command syntax and options\n\n```shell\nidra --publishtestresult --filelocation= --type= --logicalappname= --buildnumber= [--drilldownurl=] [--env=] [--token=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--filelocation`| `-F` |**Required.** The location of the test results that you want to upload. This can be a single file, an entire directory, or multiple files that match a wildcard expression.|\n|`--type`| `-T` |**Required.** The type of test results that you want to upload. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, `sonarqube` for SonarQube scans, and `vulnerabilityadvisor` for Vulnerability Advisor scans. In addition to these types you can also use a custom quality data set tag to upload test results of different type.|\n|`--logicalappname`|`-L` | _Optional_. The application's name. If this parameter is specified, environment variable **LOGICAL_APP_NAME** must not be set. |\n|`--buildnumber`|`-N` | _Optional_. Any string that identifies the build. This option overrides the value provided by **BUILD_NUMBER** or **BUILD_PREFIX** environment variables. |\n|`--drilldownurl`| `-U` |_Optional._ A URL where more information about the test results can be found. If this URL is invalid, the option is ignored. |\n|`--env`| `-E` |_Optional._ The environment name to associate with the test results. This option is ignored for unit tests, code coverage tests, and static security scans. |\n|`--token`| `-K` |_Optional_. This is a SonarQube token. This flag is valid only if the type specified is `sonarqube`. It is used by the CLI to pull additional information from the SonarQube server. |\n\n### An example command\n\nIn this example, the command uploads all JSON-formatted FVT results from a directory to DevOps Insights. Additionally, a test tool is declared, a test result URL is given, and a logical staging environment is provided. Specifying an environment is especially important when you want your results to be analyzed alongside other activities that take place in that same environment.\n\n```shell\nidra --publishtestresult --filelocation=\"tests/fvt/*.json\" --type=fvt --logicalappname=appname --buildnumber=release:17 -drilldownurl=\"https://example.com/testinfo\" --env=\"staging\"\n```\n\n### Supported Test Formats\n|Type of Test|tag|Supported Formats|\n|-----|-----|-----|\n|Unit Test|`unittest`|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Test Case|`fvt`|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Code Coverage|`code`|Cobertura (xml), lcov, Istanbul, JaCoCo|\n|SonarQube|`sonarqube`|SonarQube|\n|Static Security Scan|`staticsecurityscan`|IBM Application Security on Cloud|\n|Dynamic Security Scan|`dynamicsecurityscan`|IBM Application Security on Cloud|\n|Vulnerability Advisor|`vulnerabilityadvisor`|JSON output of the command [ibmcloud cr va](https://cloud.ibm.com/docs/cli?topic=container-registry-cli-plugin-containerregcli#bx_cr_va)|\n|Custom Data Sets - Tests|Custom Tag*|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Custom Data Sets - Code Coverage|Custom Tag*|Cobertura (xml), lcov, Istanbul, JaCoCo|\n\nFor golang [gocov](https://github.com/axw/gocov/) users, please convert to Cobertura using [gocov XML(Cobertura) export](https://github.com/yaoyaozong/gocov-xml)\n\n\\* For custom tags create a quality data set by using the user interface. Navigate to your toolchain, click on DevOps Insights card. Navigate to quality dashboard. Click on the Kebab menu which is to the top-right of the quality dashboard. Click on **Configure Quality Data Sets**\n\n### Upload SonarQube Results\nTo upload data from SonarQube, you must provide the SonarQube server token using `--token`. Your SonarQube server is not required to be accessible from your CI/CD tool.\n\nAfter you run a scan using SonarQube, you can upload SonarQube results by running this command.\n\n```\nidra --publishtestresult --filelocation=.scannerwork/report-task.txt --type=sonarqube --token=234234434\n```\n\nIn the above command, report-task.txt is a file generated during the SonarQube scan.\n\nIf this command fails for some reason, you can enable logs by setting IDRA_DEBUG environment variable to true.\n\nIf you are using self-signed certificates for SonarQube server, you will need to set `export NODE_TLS_REJECT_UNAUTHORIZED=0`\n\n## Upload Deployment Records\nUse the `--publishdeployrecord` command (alias `-d`) to upload deployment records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishdeployrecord --env= --status= --joburl= --logicalappname= --buildnumber= [--appurl=] [--deployableid=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--env`|`-E` | **Required.** The environment where the pipeline job deployed the app. |\n|`--status`|`-S` | **Required.** The deployment status. This value must be either `pass` or `fail`. |\n|`--joburl`|`-J` | **Required.** The URL to the job's deployment logs. |\n|`--logicalappname`|`-L` | _Optional_. The application's name. If this parameter is specified, environment variable **LOGICAL_APP_NAME** must not be set. |\n|`--buildnumber`|`-N` | _Optional_. Any string that identifies the build. This option overrides the value provided by **BUILD_NUMBER** or **BUILD_PREFIX** environment variables. |\n|`--appurl`|`-A` | _Optional._ The URL where the deployed app is running. |\n|`--deployableid`| `-I` | _Optional._ The deployed app's application ID. You can get the ID by running the Cloud Foundry CLI's `cf env` command. The application ID is listed under `VCAP_APPLICATION`. |\n\n### An example command\n\nIn this an example, the command uploads a deployment record from a pipeline job. The deployment is to the \"staging\" environment. The deployment is successful and the app is running at a specified URL.\n\n```shell\nidra --publishdeployrecord --env=\"staging\" --status=pass --joburl=\"https://app.staging.example.com\" --logicalappname=appname --buildnumber=release:17\n```\n\n## Making decisions about build quality using gate policies\n\nTo use this feature, create a quality policy by using the user interface. Navigate to your toolchain, click on **DevOps Insights** card. Then on the left menu, click on **Policies**.\n\nUse the `--evaluategate` command (alias `-g`) to request a gate decision for a DevOps Insights policy in your pipeline. If the policy is satisfied, the pipeline continues running. If not, and you use the `--forcedecision` flag, the pipeline stops running.\n\n### Command syntax and options\n\n```shell\nidra --evaluategate --policy= --logicalappname= --buildnumber= [--forcedecision] [--type=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--policy`|`-P` | **Required.** The name of the policy that the gate uses to make its decision. |\n|`--logicalappname`|`-L` | _Optional_. The application's name. If this parameter is specified, environment variable **LOGICAL_APP_NAME** must not be set. |\n|`--buildnumber`|`-N` | _Optional_. Any string that identifies the build. This option overrides the value provided by **BUILD_NUMBER** or **BUILD_PREFIX** environment variables. |\n|`--forcedecision`|`-D` | _Optional._ Set the value to `true` to cause the process to exit with an error code, if the policy evaluation fails. The value defaults to `false` if this option is not specified. |\n|`--type`|`-E` | _Optional_. A rule type to consider. If you include this option, only rules of this type are considered in the decision-making process. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, and `sonarqube` for SonarQube scans. |\n\n### An example command\n\n```shell\nidra --evaluategate --policy=\"somepolicy\" --logicalappname=appname --buildnumber=release:17\n```\n\n## Release History\n\n_(Nothing yet)_\n","versions":{"0.0.2":{"name":"grunt-idra3","version":"0.0.2","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^0.4.5","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.4.5"},"dependencies":{"extend":"^3.0.0","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","yamljs":"^0.2.6"},"_id":"grunt-idra3@0.0.2","_shasum":"eff37552bcbc8fd88045163df58c25f2ce928abb","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.1","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"eff37552bcbc8fd88045163df58c25f2ce928abb","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.2.tgz","integrity":"sha512-mDN3/BXgd11exVIGqAPIUQ5ibbL9YD8z6qHQlVC+IS74v0TTMGGuW/65FwT2IliDmagKHLzWB9aHcKpafE/TVQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIBmddBaKQb5gesmYpfZWM/TS3BDMPzncG8TBLkACpTD6AiAKpkH66zvRv4hOmAfYFipRVwA3g2O2V31G7EY3WPIqxg=="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-13-west.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.2.tgz_1457024038445_0.6225892608053982"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.3":{"name":"grunt-idra3","version":"0.0.3","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^0.4.5","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.4.5"},"dependencies":{"extend":"^3.0.0","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","yamljs":"^0.2.6"},"_id":"grunt-idra3@0.0.3","_shasum":"7bbb7791d7bea02d532ca07a2c436f8ceb2f8826","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.1","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"7bbb7791d7bea02d532ca07a2c436f8ceb2f8826","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.3.tgz","integrity":"sha512-6DVGSO1CsjUsW2hjfQ5qTHwGL6dNLWVBfyADrF3B3GA7e6EJ5Cn5+6HqfDXJBaTREAclavAbTSvy40w98ox8IA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQC2516m8G4Aw6NY1pzLcbHL4D9uDTgK6wWx8xFEUqN7mAIgUx3XyFk883zyOWTwYsp0tOFkDNVCjV9COA8X3TZXQ3E="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-13-west.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.3.tgz_1457047605334_0.8544070080388337"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.4":{"name":"grunt-idra3","version":"0.0.4","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^0.4.5","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.4.5"},"dependencies":{"extend":"^3.0.0","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","yamljs":"^0.2.6"},"_id":"grunt-idra3@0.0.4","_shasum":"ea9434c25f94a291b0e3c0dbe75bbb121c8e3b1c","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.1","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"ea9434c25f94a291b0e3c0dbe75bbb121c8e3b1c","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.4.tgz","integrity":"sha512-VsNbaw+/2hdWoMsoLO21aPX0yl3kg3YmgTTklMQhuLfMNDsY6+WbfbmYA38Ch8MZc3efLPvcNRAY6D2bXXe+YA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIC2wT8FNtVtIYCj5yEDRLvVi1Uxng3sQTNSChgRiXH2jAiBi9zrjb/e+lGqLvMGXx2yoBYSrYAUB4r9KcuH/+0HaJQ=="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-12-west.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.4.tgz_1457540627589_0.9524175599217415"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.5":{"name":"grunt-idra3","version":"0.0.5","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^0.4.5","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.4.5"},"dependencies":{"extend":"^3.0.0","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","yamljs":"^0.2.6"},"_id":"grunt-idra3@0.0.5","_shasum":"2dad02255569e0b8504098cbb0f81c814ea28949","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.1","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"2dad02255569e0b8504098cbb0f81c814ea28949","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.5.tgz","integrity":"sha512-sbMTKe9HUZJWJFYmrG7YCrlu7nqpcpvK9ODZYrtgU/xvf0Oi4T3QnCTExxFfxmdosk4RneVfOSRsU4lCEqX1oA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCID7kNkg6xyE5xZ3AnAZCcAyIXvuwCM7WRbgjmqIvofsYAiBASMGx5Ir9zDNozeTJCTr6y2hJQtQpYMVjQHU2jt9hEA=="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-13-west.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.5.tgz_1457988414889_0.8557868213392794"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.6":{"name":"grunt-idra3","version":"0.0.6","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^0.4.5","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.4.5"},"dependencies":{"extend":"^3.0.0","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","yamljs":"^0.2.6"},"_id":"grunt-idra3@0.0.6","_shasum":"f041a6f4f4b22e643904f3de8160172e95f38957","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.1","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"f041a6f4f4b22e643904f3de8160172e95f38957","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.6.tgz","integrity":"sha512-0p1L9hggNC4zNUAm3ILPjvcxQ0vl9AOzPQ7QZJYCR9udw0jky964VGbUHnA99DcEHWeOnkCF4AWnMzNskWM6pA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCOo6HENP1bPnLlVC+T541xptpGYLPhVcMUeHTln05xygIgMLx30evuQSspKv1W5zake5lb7OjaB9ymdaor2oYdHkA="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-12-west.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.6.tgz_1457990716455_0.3556029163300991"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.7":{"name":"grunt-idra3","version":"0.0.7","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^0.4.5","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.4.5"},"dependencies":{"extend":"^3.0.0","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","yamljs":"^0.2.6"},"_id":"grunt-idra3@0.0.7","_shasum":"64a837741b81a11a7360b3900df004e1c62341b0","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.1","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"64a837741b81a11a7360b3900df004e1c62341b0","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.7.tgz","integrity":"sha512-WpPxhGemkX861o7ErSHqnm4fny4w4Aj5GKA35mVozvbn80ufPAb+Zn7rCy+u8BPjJ5jpIsA4vnKhd+uRp1Ju2A==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIB/hftu/jb+S/4jpoDk72Sna+FbmsUqlXdx2QCydc7q6AiBHilfUm+hjN9azQ/YNHvYs+Jr2PUOwMakSWng5vKXC7w=="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-12-west.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.7.tgz_1458073542909_0.5678433384746313"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.8":{"name":"grunt-idra3","version":"0.0.8","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^0.4.5","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.4.5"},"dependencies":{"extend":"^3.0.0","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","yamljs":"^0.2.6"},"_id":"grunt-idra3@0.0.8","_shasum":"12a9c7869c216efad504cd619a5b05e84c17a09d","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.1","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"12a9c7869c216efad504cd619a5b05e84c17a09d","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.8.tgz","integrity":"sha512-6+kGca58AnkgvRIb+/YzCmv5Jzsi8gpIITDnVNR4qYcKrQG7i4G44TR6V1fsFboD+G0rsMzckO4hEvgg8XSOxg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIHX5UnFFSvGZRZXlH08YEAAmj44sJPt/iuQIsmGoprzFAiEA/qCKyiPsO43YFlqbtAOaR6DpVtV3S/02vbWL3lrSRjU="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-12-west.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.8.tgz_1458078067026_0.12393467570655048"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.9":{"name":"grunt-idra3","version":"0.0.9","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^0.4.5","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.4.5"},"dependencies":{"extend":"^3.0.0","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","yamljs":"^0.2.6"},"_id":"grunt-idra3@0.0.9","_shasum":"9022e4d7e40b88bc1b997b037449cc2950141ed2","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.1","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"9022e4d7e40b88bc1b997b037449cc2950141ed2","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.9.tgz","integrity":"sha512-HQdQoRbNGXXAPr3F+9vT9trDl8zLgmp0EAvogkgfdwGuDZyfEYbAe1SnGKl+kt/hV1YBZvdNjZI79u5CApNiVw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCeVXhdgrOng5CIV43J5GOwSmi1+cJduUkEXToMYEK2KgIgAi/7Gbow3kn5i6eEAidTrYH+irTXJOg3VIXail+JQys="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-13-west.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.9.tgz_1458147420192_0.9247559367213398"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.10":{"name":"grunt-idra3","version":"0.0.10","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^0.4.5","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.4.5"},"dependencies":{"extend":"^3.0.0","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","yamljs":"^0.2.6"},"_id":"grunt-idra3@0.0.10","_shasum":"c0b0935372445ac9b741b031b6e6611b943dd612","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.1","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"c0b0935372445ac9b741b031b6e6611b943dd612","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.10.tgz","integrity":"sha512-aK8SkYu+dBnzLdskjoOjdm1aS5SSsypj4F4MP2IhDgPplI8p6Mh5P8XgDwWOiSoSBIYv6dNb+1eiGxuoQdgOSw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDoXUMYJam+2VXAokNzAaMlT+Nl3tpKU5omLXJpG8nquwIgfhuFFn7VsvxUHzD2h51iAHsJhKdrqYVPEec34rdsaiA="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-12-west.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.10.tgz_1458315626149_0.8940781292039901"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.11":{"name":"grunt-idra3","version":"0.0.11","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^0.4.5","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.4.5"},"dependencies":{"extend":"^3.0.0","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","yamljs":"^0.2.6"},"_id":"grunt-idra3@0.0.11","_shasum":"a990c7923516f2a3a976fd388ddf17777f8e37ac","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.1","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"a990c7923516f2a3a976fd388ddf17777f8e37ac","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.11.tgz","integrity":"sha512-ghF9e1BFQsFvT0C1o7fjGPC67hZDI6EEKK2ZMvNr/Qtkjnp7D5XjAfGUuMLXkjjIphXpOn91VghFVXHjRVp1Jg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCODLg+3t87cQDZHb05uFje4gyJIkbKeqxyJDwhnxIekgIhAMJ8DRrTzRBdL+BpvjKKdiPDRKuFjLGPGngulOeeg/Ai"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-13-west.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.11.tgz_1458657833827_0.4915827428922057"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.12":{"name":"grunt-idra3","version":"0.0.12","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^0.4.5","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.4.5"},"dependencies":{"extend":"^3.0.0","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","yamljs":"^0.2.6"},"_id":"grunt-idra3@0.0.12","_shasum":"943db761fa8f3b65317af6c99fc5ead18d366aee","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.1","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"943db761fa8f3b65317af6c99fc5ead18d366aee","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.12.tgz","integrity":"sha512-TTq5hH23hTvREI/tER+t+nL6UhT56qQ/SJJk10bNpqdTRvysugi4p5Qt0sJ1uUsO/msHSrpcE2Bxp+4ua7z3xw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIH+LxsiO8zMZfL6Htzqw+5ZugLlOZDi9W/eJKBW5lJodAiEA0paw/7llYM13XrynQpNEfqf9RTF3llyDpQSgYxWsUJs="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-13-west.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.12.tgz_1458662836842_0.4811802583280951"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.13":{"name":"grunt-idra3","version":"0.0.13","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^0.4.5","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.4.5"},"dependencies":{"extend":"^3.0.0","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","yamljs":"^0.2.6"},"_id":"grunt-idra3@0.0.13","_shasum":"81c0d8f555ebaa8fc6d4dbffa36e0304f3c8f565","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.1","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"81c0d8f555ebaa8fc6d4dbffa36e0304f3c8f565","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.13.tgz","integrity":"sha512-EXNsmXId7mUxQYLS90QiJaBGGBSt3gywgeNQo8RGXQc2a2yhCbwtV38fIv90qNTVb8y3LIpclGnktTLetUw13w==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCNj6PELQh4Gb1EWz5XrmsjWKpG7MTTGV5P7OTzUrm52QIhAPzPiz2fC3+YB01bL2mQRVtW4woK8s4EfmS9AymUUQ/g"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-12-west.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.13.tgz_1458750225726_0.023135494673624635"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.14":{"name":"grunt-idra3","version":"0.0.14","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^0.4.5","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.4.5"},"dependencies":{"extend":"^3.0.0","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","yamljs":"^0.2.6"},"_id":"grunt-idra3@0.0.14","_shasum":"6298e8f2fd9e30f6d08acb8b530c539276723660","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.1","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"6298e8f2fd9e30f6d08acb8b530c539276723660","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.14.tgz","integrity":"sha512-1DqT7sVV/dtLFUbDS/kPMnM72RuuS1oCVVXnM7Gtu0FDUq2GDxQV/hiA31jcH2cZusIb5TPj1EnuNp+snXD6XA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDOH4KMf7Cs2WgMbjuNKDEGGpJNDHUyzb6qPFtCXG3s/AIgXxQ2B5t9arFDS02rrHJzHibIHrMnLhDKgZwlrSO3Yus="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-12-west.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.14.tgz_1459961202253_0.22000297531485558"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.15":{"name":"grunt-idra3","version":"0.0.15","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^0.4.5","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.4.5"},"dependencies":{"extend":"^3.0.0","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","yamljs":"^0.2.6"},"_id":"grunt-idra3@0.0.15","_shasum":"1a45ae273fc021a09c324a960fe9d64f5e4311fa","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.1","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"1a45ae273fc021a09c324a960fe9d64f5e4311fa","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.15.tgz","integrity":"sha512-7m9FX0hfaOA/FP8apq1HamQIv8/hEwNETLPdBrBBrsUp9qL0F2az0mEFSKZa2D+tFMrMQjma8tWbxbZVRvHUHw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDF+Ph4cb//kQIDIxCZ2qZ6/udqLtCj/4tbKWRXg7ocQgIhAJeiS3QwZDQbq6FVFjXqlgEP7cGxMrqynK/scoHg5T8Z"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-16-east.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.15.tgz_1460489716875_0.28960252669639885"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.16":{"name":"grunt-idra3","version":"0.0.16","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^0.4.5","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.4.5"},"dependencies":{"extend":"^3.0.0","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","yamljs":"^0.2.6"},"_id":"grunt-idra3@0.0.16","_shasum":"ec02c98babedc04074dae02c3d17584d81e95df0","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.1","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"ec02c98babedc04074dae02c3d17584d81e95df0","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.16.tgz","integrity":"sha512-qWIw1KZ3Qi0hVIZ6ZNir+NQZ1Q6c7zrl4eVsX1110OguDI7zsErzPSzVmj+Rhr3pEPH90fEvS0G51zk3vAm9Lw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDkwt0QJWgV5fczDwMDryRAuqKpkQVslxVHlmWHCSnuYAIhALArPKaAdgbj7oxrupJqIjaaq99d+Vrs2FgUtlMP/V51"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-12-west.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.16.tgz_1460497519611_0.46756103774532676"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.17":{"name":"grunt-idra3","version":"0.0.17","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^0.4.5","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.4.5"},"dependencies":{"extend":"^3.0.0","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","yamljs":"^0.2.6"},"_id":"grunt-idra3@0.0.17","_shasum":"7e4122798152836a0601d3c94756928b7e5e4c9f","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.1","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"7e4122798152836a0601d3c94756928b7e5e4c9f","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.17.tgz","integrity":"sha512-elFUkuR6TkFTtBdzrwYIVTaX0ZT5XygCzJQQtlBn+IyoCeWQpN9sGiK+SDn9vaBQh+H8yZ36iRP4ybTnLPmx6Q==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQC4cllL9GClOo/l+3bMDQXNF3X1c/NuRswsZHQEBdyS1gIgd9xFnQ67yPOIbWfmcjBkzidalfxgGtEio1IfihxL/UQ="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-12-west.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.17.tgz_1460578493273_0.39205642486922443"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.18":{"name":"grunt-idra3","version":"0.0.18","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^0.4.5","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.4.5"},"dependencies":{"extend":"^3.0.0","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","yamljs":"^0.2.6"},"_id":"grunt-idra3@0.0.18","_shasum":"20767a8f95fe70aefa42fe339852a86041d16f54","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.1","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"20767a8f95fe70aefa42fe339852a86041d16f54","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.18.tgz","integrity":"sha512-8O6r7IrTk81mpZqJMJVfIRBR2+vhgRMHt8e4gs/0PGDeopjm9g2Ft9ko2TE1TMTQ6DUL8DnFeAWjvyFiK9X57Q==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIGPM5wV2By8fyHWzw6U8j3dTv6GxsF3BKl9CmU9NZ0tYAiAEI4NC7zxhd2dvSkzojQUN0n9rxTK3VZsNYn+Ii0SxPw=="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-16-east.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.18.tgz_1460997695006_0.32555561955086887"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.19":{"name":"grunt-idra3","version":"0.0.19","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^0.4.5","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.4.5"},"dependencies":{"extend":"^3.0.0","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","yamljs":"^0.2.6"},"_id":"grunt-idra3@0.0.19","_shasum":"48395240f0a2abae04224feb8bfb78176fbd6a50","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.1","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"48395240f0a2abae04224feb8bfb78176fbd6a50","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.19.tgz","integrity":"sha512-psd7goHzHkmTlDM0Eh2TqD4fZetKKwpjmfCfEpx+m/HaonbC+rUomUdmOuIXG14Eg4nd9oa7X0C/OqOZj3zUgA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCKERCFN9kKaBkb0JFyMDP2hLa2lofStad/LP50W1W5EgIgQHshOeKJlMoYOWrlViwT6MsVZsTLUUIP0ConwudDU4I="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-12-west.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.19.tgz_1461008958343_0.5336473067291081"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.20":{"name":"grunt-idra3","version":"0.0.20","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^0.4.5","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.4.5"},"dependencies":{"extend":"^3.0.0","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","yamljs":"^0.2.6"},"_id":"grunt-idra3@0.0.20","_shasum":"3b216f19ab41960f3dde26af07600494caeadafc","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.1","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"3b216f19ab41960f3dde26af07600494caeadafc","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.20.tgz","integrity":"sha512-DSUud8odskYMo4x1GsicB13taqK8YJzdFdoapcBt9h7hMyccALTk8OojyUv5GcW7/Rg8h+LoC8ohZloL+1ZSLA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIA7DlaPGFqTXG7PrkYN9u6xuUK5gklAqpXus8HdV2LYAAiEAk3dqcol+InqEB3CXqugoXpZSb+7nG2LkJ0/vv/xwqvw="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-16-east.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.20.tgz_1461084111125_0.7138387409504503"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.21":{"name":"grunt-idra3","version":"0.0.21","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^0.4.5","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.4.5"},"dependencies":{"extend":"^3.0.0","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","yamljs":"^0.2.6"},"_id":"grunt-idra3@0.0.21","_shasum":"b23ae83a055100261b8725fa60f92a67e1d6d87e","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.1","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"b23ae83a055100261b8725fa60f92a67e1d6d87e","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.21.tgz","integrity":"sha512-3Y80kpBzwjh0sLRJMT2x2539TqQ4zdASovVRE2aPZ7IO61cKrG2T8ImSwvVT8Gn8ET3NUCgGjUZwVkalxTDnVg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIDLX3LREcmahTaqCDGfWAKWoxi4Kex5xXE2GxEU2AfAWAiEA2abotZjQq6eY9I3/AvI8EGIHuhGHbx5z9gDtjEywYQU="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-16-east.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.21.tgz_1461106183096_0.9404460657387972"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.22":{"name":"grunt-idra3","version":"0.0.22","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^0.4.5","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.4.5"},"dependencies":{"extend":"^3.0.0","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","yamljs":"^0.2.6"},"_id":"grunt-idra3@0.0.22","_shasum":"85b3534a8556d617c6e9c5ac79880e9adc11bd8a","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.1","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"85b3534a8556d617c6e9c5ac79880e9adc11bd8a","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.22.tgz","integrity":"sha512-mNdomBBBDYLf/ltZTRXIByGmz/vZCR4COtULzGQpJxWYVaWcQjXmEBrXqUp46/FdWhaGUPnlxZpL+3k6/bwNfw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCHhQcDMmh4bMaSnMssvX/a+/vRVmgSJVgw2gcHOYc3fQIhANeAHpe2bo03B4XNnevyuRpLn/A8RlNqCfe8fiMRNcOc"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-12-west.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.22.tgz_1461258488699_0.031491786474362016"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.23":{"name":"grunt-idra3","version":"0.0.23","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"extend":"^3.0.0","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9"},"_id":"grunt-idra3@0.0.23","_shasum":"a350496db1c32208134cc771130b131553fc0aec","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.1","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"a350496db1c32208134cc771130b131553fc0aec","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.23.tgz","integrity":"sha512-9u2YgRUam3k6gm33ognML/YCwSYeIFDMZ3yZ2Ftv5J/gau9gKFV/otP0Xe+Y55vUDbZANLKRMfK9zMjeQc7q9w==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIBFwqsfZCGBoGjpF+bo0R3ggIaonnDVx9AOmnZ2nvCqMAiEA9N0kxbxCn+8wZNnHHY2OKGzH8xGeVFfSD8m46COtDgA="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-16-east.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.23.tgz_1461353501907_0.4012516192160547"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.24":{"name":"grunt-idra3","version":"0.0.24","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"extend":"^3.0.0","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9"},"_id":"grunt-idra3@0.0.24","_shasum":"3affd07dfa5810a6cec7651a92f0333e35031bef","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.1","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"3affd07dfa5810a6cec7651a92f0333e35031bef","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.24.tgz","integrity":"sha512-hujSgvS12pYyZiudsxSGk/oVYQiFj5cvckUJcw9KvaZMTeieCnjPh1pDeZovN6rf3sxZXRjw+d2K435X8K45sg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDcdrI38/9TNkuQAfIGggWpUNLM1A9Xl0uNifaGvJ1eWgIgaDygJOpMxDeQe1M07v2iCHz4um/55dKPpgIO7MnGX3A="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-16-east.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.24.tgz_1461870141101_0.8960596073884517"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.25":{"name":"grunt-idra3","version":"0.0.25","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"extend":"^3.0.0","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9"},"_id":"grunt-idra3@0.0.25","_shasum":"7c6d82774c0ccf532ce15be5634e03d45f16b122","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.1","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"7c6d82774c0ccf532ce15be5634e03d45f16b122","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.25.tgz","integrity":"sha512-MBv4hZaRcFLEMT0lGedQ6QacIGVz9yqqyVCEyT0tmTg7SquLxGBDr9ocDd+DH0ovqRAEsEs0IAWzhwi+R0chQg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIEPlQ2A5DNt5sWY/dlhTGTujzYYeIhi5Boh70BfmDfuNAiEA8A+u4WAdq5KtrpTTRN42IxiCCnorVqMx6JJsDFaiC28="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-16-east.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.25.tgz_1462374034962_0.7186775815207511"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.26":{"name":"grunt-idra3","version":"0.0.26","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"extend":"^3.0.0","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9"},"_id":"grunt-idra3@0.0.26","_shasum":"2779e371039eebd6218b88aa5a5b683c2154645e","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.1","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"2779e371039eebd6218b88aa5a5b683c2154645e","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.26.tgz","integrity":"sha512-6lIC/No4WzyM+zDt6HdNvPDPaaPLNjX226gM4OR5CR+GBTQ00lLK7joqHO4BrCyll2hjqsP0R3xvvmhwDHVJ0Q==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIF+r0lutpkNhV9G+DeP3vVVLFXx9I3NwojyhceK+X/XMAiBiO8LhpsTh5EZj/3wA3TRwKHag7YrCAvQIe2nQbhEV/g=="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-16-east.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.26.tgz_1462380468780_0.8502088009845465"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.27":{"name":"grunt-idra3","version":"0.0.27","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"extend":"^3.0.0","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9"},"_id":"grunt-idra3@0.0.27","_shasum":"0f73c2a488d04d8bd9c63b0e6f2234d57ed3080d","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.1","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"0f73c2a488d04d8bd9c63b0e6f2234d57ed3080d","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.27.tgz","integrity":"sha512-97TLccmQerrlXy7DAoOajGLaeIviAFxPC1QBlmDeN2pxfFtqhULknS8aE3ZbP0BoxOObX3+ciwZ4kSMSsV9Hwg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIHD3dGomVFlIOZ5MrSKwa/ehtfM1tvc49X7C86cCwZRoAiB+wmzC0P7NnFYJyoEuABpNlYuRpOIwYaLldLF0YJPJBA=="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-12-west.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.27.tgz_1462392446654_0.08609159081242979"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.28":{"name":"grunt-idra3","version":"0.0.28","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"extend":"^3.0.0","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9"},"_id":"grunt-idra3@0.0.28","_shasum":"841da2387b6ee267d45a96b34b82d362739ae18b","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.1","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"841da2387b6ee267d45a96b34b82d362739ae18b","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.28.tgz","integrity":"sha512-GXktPHmRO3htDWn2PZvgAu4eMpszhnVEb2QpM2/oTsIi9jVjIkwq7/5fswE/XTwzJERpBrUYlo5L7/RBGYNoUA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCgmLo64T3OUWZcSesE6V6jnnHYwQsoByYFafmr3B2e2AIgQfw6Ss73vSpdPZjDaDskaaKS13AU31ZgpEyAKilHrOQ="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-16-east.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.28.tgz_1462398999025_0.31662170542404056"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.29":{"name":"grunt-idra3","version":"0.0.29","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"extend":"^3.0.0","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9"},"_id":"grunt-idra3@0.0.29","_shasum":"1481c1467cc4ec6e36f8783074da086323bb20ef","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.1","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"1481c1467cc4ec6e36f8783074da086323bb20ef","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.29.tgz","integrity":"sha512-Zh9tMV2Ymeg5B7gKEEfB9TR7a3R6czDR+PfgZGo8yk1jNyIHvl9e4su/j++k4je83Sx5EqHwm8M+1BVx7xZSOw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDl8W6D4dKWM+BoC1ymM75C0wrDkaKTQ8+P6NaGic6sywIgK95UBImoWoNV5/Po8dLTraxbAUPhGZtz/WtiuTmzreo="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-12-west.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.29.tgz_1462476188264_0.9143682504072785"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.30":{"name":"grunt-idra3","version":"0.0.30","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"extend":"^3.0.0","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9"},"_id":"grunt-idra3@0.0.30","_shasum":"16d76f377ca20e59b9bc1f025c59662754f092e8","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.1","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"16d76f377ca20e59b9bc1f025c59662754f092e8","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.30.tgz","integrity":"sha512-Muw7lpJwG0v2fGx+W1ApVepKHBQz6+f5x3fNq/38tNLSnBRh6oUvTzVh4aVdd4Kxnp63U7sEnKK84+G0EOfKBw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIAkZZLq5j0Owv8czxuAtY7AqY9TDi9WByDpROdjcCLLOAiAyRRmJYqFVtQz+K2u+wIywd9Bl6I6O2V9+3Tm0cSkhiA=="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-16-east.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.30.tgz_1462562008297_0.020620520692318678"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.31":{"name":"grunt-idra3","version":"0.0.31","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"extend":"^3.0.0","mime":"*","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.31","_shasum":"4b99f415556810d0e74fa449ef2e7adf550c5fca","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.1","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"4b99f415556810d0e74fa449ef2e7adf550c5fca","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.31.tgz","integrity":"sha512-ZB6OlJwn+udy68604/BOO2QHnHmUju0g6xbdFRNJ4iHj+WKNtboVIxOUj9MZgEQX3W+G5sgBWiuET9wjrwtjhA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDg+3d9cEkfC6b1tbWVFlOdz5X02vxelWCtYF8xws7NZgIgfKDQOmlThav/xPvDbY72ACps421PfUDRLi3QyfFa7dk="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-12-west.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.31.tgz_1463428325071_0.3998969604726881"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.32":{"name":"grunt-idra3","version":"0.0.32","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"extend":"^3.0.0","mime":"*","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.32","_shasum":"a4ebbb6336e18bab3e66fbea37be81487eec29cd","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.1","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"a4ebbb6336e18bab3e66fbea37be81487eec29cd","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.32.tgz","integrity":"sha512-6nCe8uqrNQCBogUvIcR8BUE8Evlw7zONMV00sVvlV1Ai0j0d6uShfAg7HECPn4WX3+IX4yVsYDplD8L642yBTQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIBuQTVGLY6XyhR53cQoHUlPbGE/muGN7leNyuDWgpWXpAiEA1l7vkaEd9KD6wJLXIrRTiPPpqcbQRT0v1zFjnQfCiu0="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-16-east.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.32.tgz_1463762218067_0.756334446137771"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.33":{"name":"grunt-idra3","version":"0.0.33","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"extend":"^3.0.0","mime":"*","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.33","_shasum":"e3c7cd31d8a11333fc6523915dc11a43d98787dc","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.1","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"e3c7cd31d8a11333fc6523915dc11a43d98787dc","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.33.tgz","integrity":"sha512-xLYU1/ko5s2yU+DgIFileGljIgImgYkvBGBMo2nSveLmzfj96LoEcRO8u2N6aYRCcbi2cV6K6JWIAD9lOXtZLA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDfOokYxwcjFcQildT8XLvvEYHvzpPVSP+WV3938HoVrQIgL+CUEG2GUdXsosIq9/r+B81EHLOfi7IgzZhtGX6FACI="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-12-west.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.33.tgz_1464040218060_0.19824571791104972"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.34":{"name":"grunt-idra3","version":"0.0.34","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"extend":"^3.0.0","mime":"*","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.34","_shasum":"59018c9cac974de3f1b869e178e5fe8b05532119","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.1","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"59018c9cac974de3f1b869e178e5fe8b05532119","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.34.tgz","integrity":"sha512-EujXeoeTfFAdkJ3gWU/SuN9M+Dwx0GF6b2WAcbjSfzCU3n3ArK++TPwRBVS5fSMrZ+ixqpzgy1C+pRgCKzFogg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDy28Q6ZEgRcuN/DURN3HC6HVVdyTj4dTy4yC6YW/JTewIgYAFCGb23Jwghq9pxgTHyN3D7XuEyl7C/br2/qBgZ+5Y="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-16-east.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.34.tgz_1464109648566_0.5691119381226599"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.35":{"name":"grunt-idra3","version":"0.0.35","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"extend":"^3.0.0","mime":"*","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.35","_shasum":"f79d2647d6e4ea98c6621e6e44e657f61f1892d1","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.1","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"f79d2647d6e4ea98c6621e6e44e657f61f1892d1","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.35.tgz","integrity":"sha512-rUgK9Unx/JkinGs0f2ZJqURCm5NXfktuUtBbTlVZsqQH8Pp0bhYToW+vQ3wQEYdE/CXczmOulVKERZ9Ig9akNQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIGO0msvOVuRET8zs9DfRLqSRV1CZkpkSO5FcbFZKPKN4AiEAnarwm6FVWFRhx2J/UoJCfgcO85DAMjXmfdDzcPUyM+o="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-16-east.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.35.tgz_1464283240724_0.5515979677438736"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.36":{"name":"grunt-idra3","version":"0.0.36","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"extend":"^3.0.0","mime":"*","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.36","_shasum":"285b73b2f5161c0e30b5b031715bb1ef1ce7a02d","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.1","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"285b73b2f5161c0e30b5b031715bb1ef1ce7a02d","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.36.tgz","integrity":"sha512-D3asNVi3mOzV0tX3dPbH/YgIzar0bp9NSM7dmsJ6dZQvpg7+FH+5cwIt7ACNnWtDAi7syqjxxs604BfChVtp5w==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIAeBzXyhZF3SoIslHZMiiEsI8HgUM00TfWt2pQiAgc/8AiBYg1/36HAwfTYSWMFMYAiWnPfSnHLnFdOMuq47006sFQ=="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-12-west.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.36.tgz_1464284553405_0.036785873817279935"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.37":{"name":"grunt-idra3","version":"0.0.37","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"extend":"^3.0.0","mime":"*","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.37","_shasum":"74e7e0d95e9acb1454370e76ae786ecafcac6af7","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.1","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"74e7e0d95e9acb1454370e76ae786ecafcac6af7","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.37.tgz","integrity":"sha512-7omsj8uvf4X85kh54W9RZZrIDfYSeIc2sIlrHEkpmNFEGcVym5Hvsf7cl60veVfjOpTUZv1zzaS6AcCxiB2EbA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCAgd8YtN2oIwjPDabLMtty6fhXH59VhhC33Sw6479GcAIgJmU9Z/R0i8Y77c97DoWd1E3YkTZcdmeBx2kHDTE9lwY="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-16-east.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.37.tgz_1464288654072_0.5809455560520291"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.38":{"name":"grunt-idra3","version":"0.0.38","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"extend":"^3.0.0","mime":"*","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.38","_shasum":"7b0e84b9c72b1e43041116cc7fb7a266b1387d8e","_from":".","_npmVersion":"3.7.3","_nodeVersion":"5.8.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"7b0e84b9c72b1e43041116cc7fb7a266b1387d8e","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.38.tgz","integrity":"sha512-p7454infOuaXlmGpIeXDlt96scsiAMmoWapLuTBWkLpDZHj04MDILAEZUOHh/P/d728/tIx5Ax/bijFaYqXzUg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIFi7ZR/+GX3KqybcMHt5Inm/h9pHAL+MmeWyi9zrdSiiAiBk2A4rJPy2Nvhmox9v9qOH4itonuElNakI+mhbZ9/PNw=="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-12-west.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.38.tgz_1465486046404_0.36386956577189267"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.39":{"name":"grunt-idra3","version":"0.0.39","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"extend":"^3.0.0","mime":"*","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.39","_shasum":"4e5404a5272ad84fa8749ffbeb51103ad9545938","_from":".","_npmVersion":"2.15.8","_nodeVersion":"4.4.7","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"4e5404a5272ad84fa8749ffbeb51103ad9545938","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.39.tgz","integrity":"sha512-xhztqPh2UGumgZMTFD2s6/uhRAyBS+byk2oiiPTsxeMqjNYzZoNCf9B9CgRZuwwNvm1uLmFkylkmQ4Q1TaRYjg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCBMgeRrvks22iXR5qj87f8iRfiXmsWfxP1hQSB5VAnpwIhAOSwG962/8rp1y726+QHu1yuoTlSiAALt5OlanZ/ao6i"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-12-west.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.39.tgz_1476745969871_0.6598496956285089"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.40":{"name":"grunt-idra3","version":"0.0.40","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"extend":"^3.0.0","mime":"*","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.40","_shasum":"d59492ff8023ebe6333fb50ca1d2212360a9add0","_from":".","_npmVersion":"2.15.8","_nodeVersion":"4.4.7","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"d59492ff8023ebe6333fb50ca1d2212360a9add0","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.40.tgz","integrity":"sha512-LAmOLhr6gPcn4RzT8B3kLYGnMLxttM3uJmdrtc/7MxJN7CdETn8HogjuSXh+rqT+DQGs0OvkZhbjm5FX81sMjQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQC32J/FSy5K4QfIIWp9/0P+oy51/rJRWpKpRAWIB5dsSwIhAJIqyI5ZCLxOphNB1Xd5fk6cqSPgELbaNjnlbma7Xlkn"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-16-east.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.40.tgz_1476747840161_0.2781575368717313"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.41":{"name":"grunt-idra3","version":"0.0.41","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"extend":"^3.0.0","mime":"*","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.41","_shasum":"87070db0349229853229ef3b3ca071fbc78172fb","_from":".","_npmVersion":"2.15.8","_nodeVersion":"4.4.7","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"87070db0349229853229ef3b3ca071fbc78172fb","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.41.tgz","integrity":"sha512-gbzuzjigx6XhEB0wN4uJ2cPoIi8FAjyIQRLhGkeahc4d5bJxQTYrwr+J0DRquIXSwlRBOprx3yCOk4S7hb/kYA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIBtvWV2XarqJnhovfwPuH4wrwT2/b49bLF0im3c8rCtgAiEAmD9xJOJkmUvpasHfdb+N/W5No5DMhXaKxihusCISflg="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-12-west.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.41.tgz_1476983064338_0.3982476538512856"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.42":{"name":"grunt-idra3","version":"0.0.42","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"extend":"^3.0.0","mime":"*","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.42","_shasum":"ab0270566ff7f397b403547e73bc99c357a25041","_from":".","_npmVersion":"2.15.8","_nodeVersion":"4.4.7","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"ab0270566ff7f397b403547e73bc99c357a25041","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.42.tgz","integrity":"sha512-2m+Kh28YoBMhfg0qJ3mG1I7EAVVDk+RBvr7e3evJDykz4G79Nw2snq5Rm90ffG0tKzeYr3EUswRhUEsQo4EyFA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQD4DszNEt39UY09gvem8dlddy+no77nVorRh/Crdy8njQIhALmX+VOGYXbbulYIko4wWcZLivbEx4gC4DLrmYH2PSHG"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-18-east.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.42.tgz_1477933413137_0.6163890960160643"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.43":{"name":"grunt-idra3","version":"0.0.43","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"extend":"^3.0.0","mime":"*","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.43","_shasum":"fe91bab878398601f3713e21d92e87fd03353de3","_from":".","_npmVersion":"2.15.8","_nodeVersion":"4.4.7","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"fe91bab878398601f3713e21d92e87fd03353de3","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.43.tgz","integrity":"sha512-O3tSNpF7NlRMnI5A2vdmYFsDYqfCDeGlzrTjIFQtQBgJgzsioqAwGaEFmK0vqZJpo4rSEjO/ucuEtOHqBLAPxw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIDcuBVNAIXNq+lhHrZYGGlQqeXq2CntFbBv/bmIHGaA8AiAd7zBbfzqpVNd6ozOeh+sHJgL3MpaKiemyOV34Ux3jmg=="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-18-east.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.43.tgz_1478295769168_0.477001859806478"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.44":{"name":"grunt-idra3","version":"0.0.44","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"extend":"^3.0.0","mime":"*","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.44","_shasum":"1d3e0a713b0bb4bcabd91c899698b2320a0c6afe","_from":".","_npmVersion":"3.7.2","_nodeVersion":"5.8.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"1d3e0a713b0bb4bcabd91c899698b2320a0c6afe","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.44.tgz","integrity":"sha512-tRTa9H0RhEhf9QXmuoIbb9UjK6UhxsBRWT12xdmFROPKHToTyiujniq/zdL+3xnkBlabiWeeKHEdU5nToa/jkg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDivMl1Lcf6VAiSDf7ikeHSPxfuBatGbK1imnMux/LibQIhAPwrG6jhKanvfRs4SErDU9S9L+1ejE3PdcV6JIhsnQmS"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-18-east.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.44.tgz_1485810496753_0.6595149913337082"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.45":{"name":"grunt-idra3","version":"0.0.45","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"async":"^2.1.4","extend":"^3.0.0","mime":"*","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.45","_shasum":"554aad3813c8c46ea7289081c739031425335af1","_from":".","_npmVersion":"3.7.2","_nodeVersion":"5.8.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"554aad3813c8c46ea7289081c739031425335af1","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.45.tgz","integrity":"sha512-u3tSUw7tWzfQL2/bzefigNR4FuR4k/HQu8NxGwqnx50tqm0OOgV188Da81bPn12ILKALZh9F28GnXHg4ULkL0w==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIDzfH8e0bBlQMWUL33AMAiNe8Z0iIQRBJbh0dr6K1SU4AiBGbFb4+BWKZt6Xi7Yz3JV3v7pLujWlj3bqwsi3WLE+Cg=="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-12-west.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.45.tgz_1485882960226_0.705406554043293"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.46":{"name":"grunt-idra3","version":"0.0.46","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"async":"^2.1.4","extend":"^3.0.0","mime":"*","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.46","_shasum":"6d8481f196dcdafc9336cfec5fdd6cf711fad979","_from":".","_npmVersion":"3.7.2","_nodeVersion":"5.8.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"6d8481f196dcdafc9336cfec5fdd6cf711fad979","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.46.tgz","integrity":"sha512-1HcgZytVNd7q3UB2vRRPFyZRicfmrsDjSuScR7+E2M4gxz3k1b5QyPeX++p9zvF9d/gf/qKOZ4b7RC2qsh3MCA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIFHEAm4kHC5e9OJKuJdJw+wHdkMzJtpm8k3/OaCGgTq/AiEApLcM9hQ3ahsqRCuhsvlpYf/j152OS2KbL8iDNS/RTv0="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-18-east.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.46.tgz_1486052347207_0.2456358305644244"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.47":{"name":"grunt-idra3","version":"0.0.47","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"async":"^2.1.4","extend":"^3.0.0","mime":"*","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.47","_shasum":"cbdd74696adc5284b7b53a28fe3a00dab2f05ff5","_from":".","_npmVersion":"3.7.2","_nodeVersion":"5.8.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"cbdd74696adc5284b7b53a28fe3a00dab2f05ff5","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.47.tgz","integrity":"sha512-bScjm94eXOvFvyBMQOjcHP4vriICc9weVpXtECzpMUtxs/lX9dzMg1ISODQtScvJHVFX8YGyeyXKvk2ePa1AfQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCJgaKsvRJiVjoAaWBlINGUWUu0TrVDDG5NIBWn09K9dwIgelCtuDNYUf7GngdS4W7cKX/5yaMILZkPUsVbpyFjwmU="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-12-west.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.47.tgz_1486055342484_0.47842960455454886"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.48":{"name":"grunt-idra3","version":"0.0.48","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"async":"^2.1.4","extend":"^3.0.0","mime":"*","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.48","_shasum":"56f7216b9fdc43d02402fa9db295a3075de26706","_from":".","_npmVersion":"3.7.2","_nodeVersion":"5.8.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"56f7216b9fdc43d02402fa9db295a3075de26706","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.48.tgz","integrity":"sha512-MbGvSOvlBqTfVKW0EHnKDRUf5a1E1R16XK9ZZ00e8msLUBno/Zo79SCOWxeEJ/qhkuamJbYeUaRKKuljuCKepA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCm/bwhp/CAhmvGJfOC9RLIuEaLUDOg+SbTaXcMD0q3ZAIhALvmMwv6WYo0sI25FtLhGeg/a/Bsbd2EucVcZmJniX3j"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-12-west.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.48.tgz_1486231212079_0.8283986283931881"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.49":{"name":"grunt-idra3","version":"0.0.49","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"async":"^2.1.4","extend":"^3.0.0","mime":"*","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.49","_shasum":"fb07ddef3c55a6f652efb59a71dd65f03e983b45","_from":".","_npmVersion":"2.15.8","_nodeVersion":"4.4.7","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"fb07ddef3c55a6f652efb59a71dd65f03e983b45","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.49.tgz","integrity":"sha512-DTzjgdG5ijR+Lokdl9BcLXlpFjknMtLmbB7FyywSFfq1hiCf8cVsgUrixcRB9gwidy6gcP1V8cYKkYEKsFm85g==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIFztk6rN+Jus62aIw/mHqDkj3u6R7MlMX73Sx2cHfkWSAiBxsyXGwSA35s4t5iQFiFRUNggykvvKy0mZurnJg/Jnjw=="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-18-east.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.49.tgz_1486396656828_0.19067422882653773"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.50":{"name":"grunt-idra3","version":"0.0.50","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"async":"^2.1.4","extend":"^3.0.0","mime":"*","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.50","_shasum":"643466b9de6aeedb4affdd2bd5cfa7d07a1892ea","_from":".","_npmVersion":"2.15.8","_nodeVersion":"4.4.7","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"643466b9de6aeedb4affdd2bd5cfa7d07a1892ea","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.50.tgz","integrity":"sha512-S3tW8PqLBfuz8APyStAq5wWhpeECeJzQLwVFII4GOxQ/MyYZuY+x8W9TCrzOQHzapcERNoamDZjgO/UWfEiwEg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQD1T+gp3CP9MkMmLow9Sq0kQ41PqzKhFdky2u/a8CZRiwIhALWYuieiSXcPU0zh4Wbsd2Ce7vKT8ygUEO3UsJREY0JV"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-12-west.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.50.tgz_1486401421217_0.6133887644391507"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.51":{"name":"grunt-idra3","version":"0.0.51","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"async":"^2.1.4","extend":"^3.0.0","mime":"*","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.51","_shasum":"80464a053125b1f22c457f0fc263bfeebbacb23d","_from":".","_npmVersion":"3.7.2","_nodeVersion":"5.8.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"80464a053125b1f22c457f0fc263bfeebbacb23d","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.51.tgz","integrity":"sha512-fBm1+46FOQJmRssZlKY4LF9AZHrYB0Z8A8CtveOYdch3iNMo08hHgC08ZoCmuS941o37LpIAX9ggM4XKxJU2CA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDuX2p+ACMs7fXwcq4GYa0NfYQLtbyq9EeQBGPCSG6amgIhAJlANe+hNQzRkHoWtllOVlyDvNGyHR1la7IETtB+fH1d"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-12-west.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.51.tgz_1486764940064_0.2753980972338468"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.52":{"name":"grunt-idra3","version":"0.0.52","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"async":"^2.1.4","extend":"^3.0.0","mime":"*","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.52","_shasum":"77b0c7cb54041f71d3d4a019f9133e4338ba7570","_from":".","_npmVersion":"3.7.2","_nodeVersion":"5.8.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"77b0c7cb54041f71d3d4a019f9133e4338ba7570","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.52.tgz","integrity":"sha512-yhAQyYJrTr6IjRkkSJ7GnTpr29Gs7g1PxMs2fwPmIv0HMg2npVnfO7ASYj12LwdfoLemYDFMV5CTbPlKmUWQ/w==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCBj1hoFoR7qZLtR6q0ooXLxEUV3teH4K0Azv9uH7bPXwIhAJs1tTR2icLK/lHfyQGtscT6fACW6iyRKtqirmV84WbP"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-12-west.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.52.tgz_1486766129145_0.5195531893987209"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.53":{"name":"grunt-idra3","version":"0.0.53","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"async":"^2.1.4","extend":"^3.0.0","mime":"*","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.53","_shasum":"c22d1208075788c8648efd95a82912253a24feeb","_from":".","_npmVersion":"3.7.2","_nodeVersion":"5.8.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"c22d1208075788c8648efd95a82912253a24feeb","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.53.tgz","integrity":"sha512-43hbOmlHjbuvWGuyVTY9Ndj92k3z2nwB0ZivdlNcqSWzgsgH0iofOnulUVGNZC21OQzIvWNIcdQqKY8Rz6J51A==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIEdLcWXd4Wr4n2adg9ZrINZDnc2GN7rZkFL8YSf+MmTiAiEAzjmctuUuacGfCnwVpLBJad0qfE2TSUXs1miDxGoPYdA="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-12-west.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.53.tgz_1487000456431_0.5020409489516169"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.54":{"name":"grunt-idra3","version":"0.0.54","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"async":"^2.1.4","extend":"^3.0.0","mime":"*","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.54","_shasum":"2b5c9ee594a2871a6fa3a8043162cac631456891","_from":".","_npmVersion":"2.15.8","_nodeVersion":"4.4.7","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"2b5c9ee594a2871a6fa3a8043162cac631456891","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.54.tgz","integrity":"sha512-ycsdSvpiYRASVCbG0iSdAmUA6HY+hrasNsz1i52pmSMFmCq4tjLZBNAJENcxquNvRBXbf/me5f7F8ed8olXakA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCTYVDRnif8g7O3AJeUNrtJrPvQXkT6asBlc9Sw+hdamwIhAISD7aMK7Jt+bCL+MTV3032vevK2wNutByWy01ACRSxO"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-12-west.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.54.tgz_1487799743932_0.757453752681613"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.55":{"name":"grunt-idra3","version":"0.0.55","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"async":"^2.1.4","extend":"^3.0.0","mime":"*","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.55","_shasum":"a2531fdbafa5dde8b79f71f11b09aabf83586bb4","_from":".","_npmVersion":"2.15.8","_nodeVersion":"4.4.7","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"a2531fdbafa5dde8b79f71f11b09aabf83586bb4","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.55.tgz","integrity":"sha512-/RLFgZHc9ntd0tdbKjJi4ZlZbfACxAXF/1vebYZjbt/C3istdD8g0NQupaahrH3xLhjVhv89t3f7/hWljsapUA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIE72or3wNhEGvt9nlJgGSLGaD+VkfdjtKaWUgjCOj7THAiEAtumhHQthbH0h7FLAWTFy50QHbMKjiJSw+8SU+SCUcaY="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-18-east.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.55.tgz_1487866586377_0.9686784006189555"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.56":{"name":"grunt-idra3","version":"0.0.56","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"async":"^2.1.4","extend":"^3.0.0","mime":"*","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.56","_shasum":"68895a507745eee9ba07ba04958d8ba8e1a42b3d","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"68895a507745eee9ba07ba04958d8ba8e1a42b3d","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.56.tgz","integrity":"sha512-KJSvPOfn/wiNScFPQTBx1sxKCcfJtquTeH+NjheY0rB6V9CuNBhoMT+FYySAcUqtQ/czmIV3XfW9c1sYITzdug==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDGLMKfHEjgmumAIpYakHJiYiKnwfdTkXPqcnQVf1qwBgIgQVqr9hicg54mLQhCGgW+ho+USvbLCHNiswGZO5T+Etc="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-12-west.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.56.tgz_1488575780146_0.5352926517371088"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.57":{"name":"grunt-idra3","version":"0.0.57","description":"Grunt Plugin for IBM DevOps Deployment Risk Analyzer","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["DRAGruntPlugin"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"async":"^2.1.4","extend":"^3.0.0","mime":"*","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.57","_shasum":"00a8ce5ba93793e539e672b85956149ebb8b920a","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"00a8ce5ba93793e539e672b85956149ebb8b920a","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.57.tgz","integrity":"sha512-xG9hjigG/VXSb6+QmF2MPUUQYzOVi57tUGe6FV3qFBEdW3YU2UJSBMApxtfD9SXpcD3CcD+N1wTD4qoe4wKhdw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIFTbwDFbPT943hnSfiYLye+oJzMqf7QwAffp4ZT79tzAAiEArsgyncwrBscO2PD5JQ/6JXCXkrKJrlpqvGx6QiWWKLk="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-18-east.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.57.tgz_1488919557399_0.8788066485431045"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.58":{"name":"grunt-idra3","version":"0.0.58","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"async":"^2.1.4","extend":"^3.0.0","mime":"*","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.58","_shasum":"89b954b2dde6aec14004d28e137bcae771497b0e","_from":".","_npmVersion":"2.15.9","_nodeVersion":"4.6.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"89b954b2dde6aec14004d28e137bcae771497b0e","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.58.tgz","integrity":"sha512-K+s/Ugb3gYsR4tqWXojrecQrQbW0QolIcx7itgtEXwO/j1AnSoOq9rXqJScWjfp42ADM1C+6J1nsQtNMGwlZ8Q==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCVxwvjrUOrUnxaPpVd+YjJcoY2fNl5WFPNt1acSeurQgIgMD1KkaHmD/98BBqYhp1DyBg9qY4+2t4El28GeeLMFhA="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"packages-12-west.internal.npmjs.com","tmp":"tmp/grunt-idra3-0.0.58.tgz_1494439535785_0.634783319896087"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.59":{"name":"grunt-idra3","version":"0.0.59","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"async":"^2.1.4","extend":"^3.0.0","mime":"*","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.59","_shasum":"16b7fa2cfdbded543c07d3991268b338545cc204","_from":".","_npmVersion":"3.10.2","_nodeVersion":"4.0.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"16b7fa2cfdbded543c07d3991268b338545cc204","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.59.tgz","integrity":"sha512-y3n192ck2hXxFBwzqpFNB/FmWfvtld/EymjTFWZFAVQgZiRIpygxLA47BZExlszA1XJ4MB4Y8YM7SPV9W5/+fA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCfE0LJ4rTz7MgIxYiiidt4FQmQ47QE+a01AGZJuehjBwIgeELnddX77EE0pURUCHWfw2JB+hlI/jSX3lY7ZD6zGME="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.0.59.tgz_1496265500103_0.9667112305760384"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.60":{"name":"grunt-idra3","version":"0.0.60","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"async":"^2.1.4","extend":"^3.0.0","mime":"*","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.60","_shasum":"fd9d3be2119b1f0b8cf30f50bdfe59bfc011c98c","_from":".","_npmVersion":"2.15.9","_nodeVersion":"4.6.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"fd9d3be2119b1f0b8cf30f50bdfe59bfc011c98c","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.60.tgz","integrity":"sha512-LCg9I13ThG2wy7+NvZGinIo5qnpogEGuZXm+lc7eAY9EadBf6ubT1OmnDhsmNkGj8xugQFkE0bPsPukQunekyg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIEG5F8c5FFDKraGzWjkjl4F18TpCmxnybYXgzfnueF9TAiBJTaiYQvG97fbEQ4IMrXX+EiHnBwA2Gxh2isccxtyHEw=="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.0.60.tgz_1498687132243_0.22689152276143432"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.61":{"name":"grunt-idra3","version":"0.0.61","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"async":"^2.1.4","extend":"^3.0.0","mime":"*","node-uuid":"^1.4.7","request":"^2.69.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.61","_shasum":"5dfa48633a06a7437b21ebbde30061702df1204c","_from":".","_npmVersion":"2.15.9","_nodeVersion":"4.6.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"5dfa48633a06a7437b21ebbde30061702df1204c","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.61.tgz","integrity":"sha512-EsV+YBxPqY/trPY18dYDlNqjg3Ot3KWJgT1FvWh0Dp3lEtdXh2a6i0mc/zWAK17pNzEk+7PWW0Qm/FIikxUHuA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCv6nlK9JnxX9vUalvFBzWHnNB8F7FHuyFSjSOW9pySBAIhANkId/rPrK+OARxQxKcf0wl+DcUr7u8a4Rgen+YuaTSo"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.0.61.tgz_1498763425282_0.016642829170450568"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.62":{"name":"grunt-idra3","version":"0.0.62","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","glob-fs":"^0.1.6","mime":"*","request":"^2.69.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.62","_shasum":"b3165e02e369fb9b10d8e6bf8e617b4e75916105","_from":".","_npmVersion":"2.15.9","_nodeVersion":"4.6.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"b3165e02e369fb9b10d8e6bf8e617b4e75916105","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.62.tgz","integrity":"sha512-tHNb0vOGnszWrhloH5qcwCd0OvbqwN6H7kenOKAbrzgMPA5uLls41/u8u8nZWIOFkceOOFc/KbgxAOaFe75A5A==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIA5mxPtFzbtEHr7aAe/oUg31RcGAyggUALd9tQm40xl+AiEAp3+EJME5H+uTBYn082Cidl/S8+jVTY4ea1NwJ9gYsws="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.0.62.tgz_1501019445992_0.30867114453576505"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.63":{"name":"grunt-idra3","version":"0.0.63","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","glob-fs":"^0.1.6","mime":"*","request":"^2.69.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.63","_shasum":"d5977ea293c1214fbc8d20ac18857cd7b2ae1901","_from":".","_npmVersion":"2.15.9","_nodeVersion":"4.6.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"d5977ea293c1214fbc8d20ac18857cd7b2ae1901","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.63.tgz","integrity":"sha512-x6Fj3uXMPePtm6B7VLj2ovHwLqBljLwkywhPqLbfGqIu+znDQxOZnioQjhSgtqunAkSlRLMi4KrYfls5fq/eRQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDlRx9QxFtDWtWt4ruzsaho8KCXR9Rx8VZdHGuLoOWWRQIgVfZ8EGw3cnivY2z9XmdsraJJKGmnXLPJEXqdbfL5ngk="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.0.63.tgz_1501023694219_0.3662489603739232"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.64":{"name":"grunt-idra3","version":"0.0.64","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","glob-fs":"^0.1.6","mime":"*","request":"^2.69.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.64","_shasum":"e4a9745c0b46b4c0caf829ceec8ad0bef8617524","_from":".","_npmVersion":"2.15.9","_nodeVersion":"4.6.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"e4a9745c0b46b4c0caf829ceec8ad0bef8617524","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.64.tgz","integrity":"sha512-ca2cszEDJNpvSqxRKBHlslCWpp8XkhiOUP4mxwjf5pymMGB88t3caQnRQKCB/4NIXEciNYnUxfejIhddMSzlcg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDWNhdVbeB0vpacaC1c6g6Mh2A6vXkKMEsxypHkvzLVKwIgCM5jfCNZmWfECuSmfbWzlHSUUQxtwx8N/6golzr1gPs="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.0.64.tgz_1501081273973_0.40137580409646034"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.65":{"name":"grunt-idra3","version":"0.0.65","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","glob-fs":"^0.1.6","mime":"*","request":"^2.69.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.65","_shasum":"3fda128016f869ec9141a63a9044c0c3b9fb3a8c","_from":".","_npmVersion":"2.15.9","_nodeVersion":"4.6.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"3fda128016f869ec9141a63a9044c0c3b9fb3a8c","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.65.tgz","integrity":"sha512-5E7iGtBgpPgc747yNeqgTsze+F423a2VcCedEYoSoMzgkAUOo8ybIlHZunWCJl3R/O9FZIOV5pqjkCFltUTXDg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDVfMA5GplNiaJY+4VhRjBBvVbruGFZKrZNLg2LEHgtbQIgOgYTrQGmrUKNiIcVEHut3tz0eQXJyoaWorJSZBL4nhE="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.0.65.tgz_1501082791688_0.7950452021323144"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.66":{"name":"grunt-idra3","version":"0.0.66","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob-fs":"^0.1.6","mime":"*","node-uuid":"^1.4.8","request":"^2.69.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.66","_shasum":"3596d356c48084ec6f742186bbbeceacbdb0691b","_from":".","_npmVersion":"2.15.9","_nodeVersion":"4.6.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"3596d356c48084ec6f742186bbbeceacbdb0691b","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.66.tgz","integrity":"sha512-hRLYhvF6eKhGsB1/0TzsxseNfM/SEuSSRw/aOSKbOxf5bZPzE+jXFhW2n2rUmHA+jk/H4ESmZs8zivkXSiBFow==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCwbPlJPeHu9fB0rXo3/Qi7OflVLDlfCKA6xUGKprTUtQIhANL8hOUs6+xHYuWn+xTYJg0sfvlR2SbcWlfklaNRIyfi"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.0.66.tgz_1501088041242_0.0946477260440588"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.67":{"name":"grunt-idra3","version":"0.0.67","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob-fs":"^0.1.6","mime":"*","node-uuid":"^1.4.8","request":"^2.69.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.67","_shasum":"3a1f96c59afb53ac9b10a44e90acf853a0b4f266","_from":".","_npmVersion":"2.15.9","_nodeVersion":"4.6.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"3a1f96c59afb53ac9b10a44e90acf853a0b4f266","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.67.tgz","integrity":"sha512-ybPyf0+PK6Hcrah6IrzSpv5TulMV0tVpHQ0INbrkWByWSwfUxyH2YZBhcZ7i2Dklt15EyOAM4B9MyScTfMjoYw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCSpuaX6GbD2qVUiv2zeeqaAjfCJEg3CxOpIvjCqFRtXAIgbaMvIfTX2z4AhIw4GltY7Jp/OcwCuv8Sew9SToE+2Ww="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.0.67.tgz_1501091958143_0.9077001179102808"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.68":{"name":"grunt-idra3","version":"0.0.68","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob-fs":"^0.1.6","mime":"*","node-uuid":"^1.4.8","request":"^2.69.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.68","_shasum":"82ade05d5ba940e963b3c0759f605df1c4b7d19b","_from":".","_npmVersion":"2.15.9","_nodeVersion":"4.6.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"82ade05d5ba940e963b3c0759f605df1c4b7d19b","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.68.tgz","integrity":"sha512-UwOMCEAn32ayp2vv8O1K/jVxWRzukLDHKjcshB/baHn8iRSAE+7iGb5632XjQLQV9bOVluUx65AZeCFZ4mBO8A==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIEIYXe+2XakmLM0Ppuh8UegNfYZ2qT0QUBYFZgxq4VmaAiBCJLGgJ0EgtMhYUoNqj5I8j/eoZgoYrIuu88dRRVLKuw=="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.0.68.tgz_1501171786363_0.6019278517924249"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.69":{"name":"grunt-idra3","version":"0.0.69","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob-fs":"^0.1.6","mime":"*","node-uuid":"^1.4.8","request":"^2.69.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.69","_shasum":"a2cc1c1bf039b74c1b5cdf18f1d83a79e8a9acd8","_from":".","_npmVersion":"2.15.9","_nodeVersion":"4.6.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"a2cc1c1bf039b74c1b5cdf18f1d83a79e8a9acd8","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.69.tgz","integrity":"sha512-CJh5b3bjWPIBkp5T/hnhjmobfeHgcNBElQ8OaL9dBhYZEmZ5uvxxJMuvjtYhJP2+iXqkhTX6qFMscjjkN49u9A==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCdMUlVsVNXPDe9mN0Ck4zY21rYJV/vWUhLYmOjxnwfgQIhAMS/EB6FPYdmgm5rxJ8jV2Gezf18Z8J0i0as9sa1pxxr"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.0.69.tgz_1501180130263_0.8238412332721055"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.70":{"name":"grunt-idra3","version":"0.0.70","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob-fs":"^0.1.6","mime":"*","node-uuid":"^1.4.8","request":"^2.69.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.70","_shasum":"0ad2de963e007af2ddb800121dc8f9f554a165cc","_from":".","_npmVersion":"2.15.9","_nodeVersion":"4.6.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"0ad2de963e007af2ddb800121dc8f9f554a165cc","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.70.tgz","integrity":"sha512-qIPVNgVhPVMd1WvZCfKOR4QXCmFVIs4ROlB37etGMbtXWWS+KB9AjLw45uMq32RkK+l4oFRQBbEhsVNQATGYhg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQD0kpunUgsi7StNCf5GB/O+dvCAiLR11Lm9Pc3LJ2cYgAIgUtEhwTWZoXQNRraJ/2CSCQnwSY8XTkAsaS4KLFUZwkY="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.0.70.tgz_1501186837590_0.22889867587946355"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.71":{"name":"grunt-idra3","version":"0.0.71","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob-fs":"^0.1.6","mime":"*","node-uuid":"^1.4.8","request":"^2.69.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.71","_shasum":"f83da2a1e4d5e16c6a6ffd949fa901931c3b3a9c","_from":".","_npmVersion":"2.15.9","_nodeVersion":"4.6.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"f83da2a1e4d5e16c6a6ffd949fa901931c3b3a9c","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.71.tgz","integrity":"sha512-D27bURnQSxoNCy52pE7KQjYl9qGX8Ka2C38JacVwi3YYmkN0Qt0JhEKqppdGZvkWKuBsU4PBv9hvFfrB6l6W1g==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCxUd9OVKYPOS7zZcSkKjH82dD6ebuxi1g47yzSmlHaxgIhAJdt/AbhZbH2O3cUui0WYrFiw5Vga5F3nSWqkf8wi8OG"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.0.71.tgz_1501195908187_0.07944994210265577"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.72":{"name":"grunt-idra3","version":"0.0.72","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob-fs":"^0.1.7","mime":"*","node-uuid":"^1.4.8","request":"^2.69.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.72","_shasum":"1a3b184e44fc24153d8ac987d7d66a89e5310e6d","_from":".","_npmVersion":"2.15.9","_nodeVersion":"4.6.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"1a3b184e44fc24153d8ac987d7d66a89e5310e6d","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.72.tgz","integrity":"sha512-pd/hPEqcnXJtNCDLodiHlCYYEmFQEd3lLZv0yFGCn65INHWuedZ1ZK9ejW5DtZDO9nPaJVWR+6j4hD8isMHVDg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDUapQm8unvC+6PkeHVWzCvh3UYCeo62Dco7Um22oGYdQIgev08GW1RIVeB4izWPOKepj51iFIjachSiBxeQiTg+xY="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.0.72.tgz_1501263362585_0.6585040087811649"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.73":{"name":"grunt-idra3","version":"0.0.73","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","mime":"*","node-uuid":"^1.4.8","request":"^2.69.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.73","_shasum":"c27ff2b8e6b2a30f1460af607c8096ffa90e52d5","_from":".","_npmVersion":"2.15.9","_nodeVersion":"4.6.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"c27ff2b8e6b2a30f1460af607c8096ffa90e52d5","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.73.tgz","integrity":"sha512-YQNrm6IOTnUMIqUWvNyHkj+XdqVT+fALSDgXB0gJKFbDA3wGmwrjuKRDwUt3ugryVEOPpymDR6JabG3TW4onhw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIB5DXdwPwMcRaC8xm+KmQ+EfMLvzllcQa6Awx/DwCwMqAiEA5CdkEhcbBXMKO9oq2KbIaRqe5F/tccJZuwOes0UrNBM="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.0.73.tgz_1501279168757_0.014028672827407718"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.74":{"name":"grunt-idra3","version":"0.0.74","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","mime":"*","node-uuid":"^1.4.8","request":"^2.69.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.74","_shasum":"e4ad5576367f9b928e0e432a47c85efd6b1624f0","_from":".","_npmVersion":"2.15.9","_nodeVersion":"4.6.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"e4ad5576367f9b928e0e432a47c85efd6b1624f0","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.74.tgz","integrity":"sha512-NsECpjlI0vmsbBjxexQsM8eCw3fPrVtq8WTdyCEfdhoXPc0thurQQMy5REEimiuqyrwLWeFsnlV5nRRjdlc/jQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIEjVHaUEJhMpGh1LX739og+kA7MJCC9C44f8Gvv1dnBZAiEAwGYZdLK9AnNslc/BsVVQ0Bz242Oe++Ux0KdksP9SBtU="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.0.74.tgz_1501520011594_0.65703384578228"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.75":{"name":"grunt-idra3","version":"0.0.75","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","mime":"*","node-uuid":"^1.4.8","request":"^2.69.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.75","_shasum":"ef3e16079da4c2f8c4b069b9a21644c27d9a854d","_from":".","_npmVersion":"2.15.9","_nodeVersion":"4.6.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"ef3e16079da4c2f8c4b069b9a21644c27d9a854d","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.75.tgz","integrity":"sha512-fMZQSNMJFFt09issf8QjDFaiU8M99BeDFsCBVXvrevhvBBz9odRYGYjp2/7GtV02zwYXcJwN5Euqda7RADSf0Q==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIHy/sr1r9PNQSjxzMklkH/6NFNujD55RymLEr+iVtS+CAiAPpb23v+f9afNjIuSkKOvV59Go4ohA07TSl9tFMtn3UQ=="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.0.75.tgz_1501613733855_0.8013281440362334"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.76":{"name":"grunt-idra3","version":"0.0.76","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","mime":"*","node-uuid":"^1.4.8","request":"^2.69.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.76","_shasum":"303e3baae83f6eacab9ac64815b73559c60b68a2","_from":".","_npmVersion":"2.15.9","_nodeVersion":"4.6.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"303e3baae83f6eacab9ac64815b73559c60b68a2","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.76.tgz","integrity":"sha512-6n05UV2KTqV9Mx2ZmzHeUq2HVVrpY0QGtCPWGkpq0qPHvCB/7pMMQN+EWtztwH824F+USDvQ/2T//ItSO9UQ6A==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDFnC8VioR0GjiyRqZwvhoEpAOhBOq1zwULFv08mwMRkAIhAJ6Hmslq/88z1jk3zO3lDHfsbOiBGMYUSciYmo/YEgO3"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.0.76.tgz_1501776010490_0.840971989557147"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.77":{"name":"grunt-idra3","version":"0.0.77","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","mime":"*","node-uuid":"^1.4.8","request":"^2.69.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.77","_shasum":"a29a2d9432734f7f1bc3124613b613a9b144de48","_from":".","_npmVersion":"2.15.9","_nodeVersion":"4.6.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"a29a2d9432734f7f1bc3124613b613a9b144de48","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.77.tgz","integrity":"sha512-XcOGz5E2hXnDJHhlLExHnVPDVMZeYSuXRzTnEGRvtpQAMphieF8T+fUzsdtIBsNwev02B/ebdnREOjzffUUoMw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIBwBHrjBBKh3Oo8RfnFBAJjrcjcmfDfUj/EYI8h/ywGwAiBrygOVYnSNyF7FFHo2/JacVEg+acGG7QJFTLl+dS+uJQ=="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.0.77.tgz_1501785244867_0.7515939341392368"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.78":{"name":"grunt-idra3","version":"0.0.78","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","mime":"*","node-uuid":"^1.4.8","request":"^2.69.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.78","_shasum":"93f4f79c2e897290e45eacf4ca0497874be78f95","_from":".","_npmVersion":"2.15.9","_nodeVersion":"4.6.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"93f4f79c2e897290e45eacf4ca0497874be78f95","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.78.tgz","integrity":"sha512-pNQVlKF+kivZHaC4WFkY8djZKrS1Co+rrxqSQIx7FAT+WgG9w+KLqBHDUF75blyVJ8RmLJNhatSsWa6+duxv5w==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCJqZQyIXrZBv5ZEb50H/e5ewmbk5Zh+Nal/UttQidOyAIhAPwm76ohUmdDLZvgvILohO9mEUalKPaSVN06Vr6DeW9/"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.0.78.tgz_1501864587620_0.8233504167292267"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.79":{"name":"grunt-idra3","version":"0.0.79","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","mime":"*","node-uuid":"^1.4.8","request":"^2.69.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.79","_shasum":"419a0b980c2eb4292ba5e347f7d501812e94962a","_from":".","_npmVersion":"2.15.9","_nodeVersion":"4.6.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"419a0b980c2eb4292ba5e347f7d501812e94962a","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.79.tgz","integrity":"sha512-PXs2G+xtgaxxD2KX46bSPQwZDkq+Ks3/n8Y3L8iQZ3LJUVTjTmpL9lw1ULLu2YBUkMZuAGz44j0qtlI8tInsvA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCPPNofEuVIgyQ6CfxtvtQszjzd767ZMgquHowJ4UfS5gIgUaPAbpo1waf+p5vxPVaU/KPWjmQicGgGCepqCJoV9/Q="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.0.79.tgz_1501875849287_0.05979182641021907"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.80":{"name":"grunt-idra3","version":"0.0.80","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","mime":"*","request":"^2.69.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.80","_shasum":"34ad97232cf8e40620e97d5c5d0624e61cd7f943","_from":".","_npmVersion":"2.15.9","_nodeVersion":"4.6.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"34ad97232cf8e40620e97d5c5d0624e61cd7f943","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.80.tgz","integrity":"sha512-crIEmZK/yerJ925Yrawm6O2j3AfMJGZKpoBHN8fWSYl7BGLJQ2a7yrBIbnWTZXo2rBPvLVOP3RBxmeVxrqRxhA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIDiqn6fIVxsXydrefe8tIP3XOzy33A0awdKns5J6UiK9AiBFVKLML45vnREfGDRyjoyF4zUm2lKwGx7Z3hGhg9Fkpg=="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.0.80.tgz_1502308632490_0.5366906451527029"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.81":{"name":"grunt-idra3","version":"0.0.81","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","mime":"*","request":"^2.69.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.81","_shasum":"b6db50d0348462604d460e7cc0a25ea46d140bbb","_from":".","_npmVersion":"2.15.9","_nodeVersion":"4.6.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"b6db50d0348462604d460e7cc0a25ea46d140bbb","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.81.tgz","integrity":"sha512-ulcBpuAhQyCXki46aKYCgmBgjsz91osugQqXtCsPvtfD3bsRmzEocRWJSUNsC70QXD6dC9gUU1NFu6GWkGlnFA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIGtreQ9eTO9fW4QsY+ZaWPQ0Da4pkcTRDiznciYmA5kTAiEA5fkt0iIpZ4VY7hgb46g31zlbsvmy0r/tVEdNulLxpgM="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.0.81.tgz_1503678997978_0.7852181543130428"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.82":{"name":"grunt-idra3","version":"0.0.82","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","mime":"*","request":"^2.69.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.82","_shasum":"484f782134b52d4dc4dc4da83b98b579a794b4ce","_from":".","_npmVersion":"2.15.9","_nodeVersion":"4.6.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"484f782134b52d4dc4dc4da83b98b579a794b4ce","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.82.tgz","integrity":"sha512-Y52Iwp49JSu5vDjF44a572SV1sv5vpkpP9pj/EMOWy2aO6ekteH3V99iP3tsC1k9YQXw4EJ8/E9+OuPuGC9L4w==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCeVBLaB/TThShq48dAzRG98SZVhv8iGuYlJ4sr/0oNfAIhALyP7Lle4KmT1tGnsM2+LQ1wjqObtygyEXbLuOwR5Dh0"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.0.82.tgz_1504629655068_0.7970515503548086"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.83":{"name":"grunt-idra3","version":"0.0.83","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","mime":"*","request":"^2.69.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.83","_shasum":"718d9c631c7b4820fed7668c081b5df8704e08b3","_from":".","_npmVersion":"2.15.9","_nodeVersion":"4.6.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"718d9c631c7b4820fed7668c081b5df8704e08b3","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.83.tgz","integrity":"sha512-fa2+PpWtc0kB5+pqkIn84+I0QsYHxSLFoB/iBIMQ7n9ZfV5cn3DTfdUIvOeMwitcHolTutqg5wQsShR1Zvz0CQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIGHFqelC52dG0gAoVHywe79yRg9qP6fGDey46/HRcbf5AiAFnkXF8lbavETU6BT0ZHZLmPMAWtMiTSdAId8NMvuJzQ=="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.0.83.tgz_1504892136518_0.29889590037055314"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.84":{"name":"grunt-idra3","version":"0.0.84","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","mime":"^1.3.4","request":"^2.69.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.84","_shasum":"ca4b3a0f153f3c5bf152122639bc82fe564d1bb3","_from":".","_npmVersion":"2.15.9","_nodeVersion":"4.6.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"ca4b3a0f153f3c5bf152122639bc82fe564d1bb3","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.84.tgz","integrity":"sha512-iupo2dquQ1ze76ajDwVNTvSQ4EsfWXP5U8YQg3VO73hIefLlSx9mHGyreiOlIlcRZeUCLYscW/bsbDmN5Hv7Og==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDihdLi6ZeGVsMp6UG7u5pBzVPXyGk9ClSas6uf4XcwfgIgSgSMk0k1s/GVyTrhh7hTkQA79JxqW1lHPQBlu309z60="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.0.84.tgz_1505319251000_0.5154770412482321"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.85":{"name":"grunt-idra3","version":"0.0.85","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","mime":"^1.3.4","request":"^2.69.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.0.85","_shasum":"cb1af9b908a64c33e2bf52b6f75dee7c6bfeb7d4","_from":".","_npmVersion":"2.15.9","_nodeVersion":"4.6.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"cb1af9b908a64c33e2bf52b6f75dee7c6bfeb7d4","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.85.tgz","integrity":"sha512-qJFY3DGLNlxLlWoFA/9W44/0NMkqomPlZbVDpKBbcXaT//HyC+afVSnvrbdhyVP8lFLI/8NBnctLOMZPiB/YOQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIG9CYag9WnHVLhXX28WcslaJp3M2Fuxmw5F8zI1j8+EfAiEAtrvmflvU8SQwnmNMNoHR3MkU+qkm4yOnD09pJwMJ6oo="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.0.85.tgz_1505770413181_0.032902546459808946"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.86":{"name":"grunt-idra3","version":"0.0.86","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","sonar-scanner":"^1.0.1"},"dependencies":{"async":"2.1.4","command-line-args":"4.0.6","extend":"3.0.1","glob":"7.1.2","mime":"1.3.4","request":"2.69.0","url":"0.11.0","valid-url":"1.0.9","xml2js":"0.4.16"},"_id":"grunt-idra3@0.0.86","_shasum":"0cb5748971865a5fa294fbbffbe845023a3c46bc","_from":".","_npmVersion":"2.15.9","_nodeVersion":"4.6.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"0cb5748971865a5fa294fbbffbe845023a3c46bc","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.86.tgz","integrity":"sha512-8Fn4pdr60zKK6NwUy+jzL6sPRZPpOtt7pGfUj4yBgq9tN8kdXsMRjCuIgnC+C2zREFJTr+67GgeFC11uwC+m7Q==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCX6Z/06+szitur95mh/9U+C545v/A6gIxw6w6v7PZOLAIhANUN9cW9wc/ReSv3kXn6KG9bsqfMD2VgD7i9exXxTQDg"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.0.86.tgz_1507569861861_0.1661351656075567"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.87":{"name":"grunt-idra3","version":"0.0.87","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","sonar-scanner":"^1.0.1"},"dependencies":{"async":"2.1.4","command-line-args":"4.0.6","extend":"3.0.1","glob":"7.1.2","mime":"1.3.4","request":"2.69.0","strip-bom":"3.0.0","url":"0.11.0","valid-url":"1.0.9","xml2js":"0.4.16"},"_id":"grunt-idra3@0.0.87","_shasum":"7b3bc0685ed6f145d08f74cc18db908412e242c6","_from":".","_npmVersion":"2.15.9","_nodeVersion":"4.6.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"7b3bc0685ed6f145d08f74cc18db908412e242c6","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.87.tgz","integrity":"sha512-w/54ADR4fxLQT+ouaEs2Ln6DB6nmZqyDPcaWyHqgrmTqQrw52ogS5eVk+1ICB4cQv4sKtRoh/wFxi62VPQNoyQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIATZliDb3uL9CBnES4pHc6KwHdB9RTNqLJTNN7QIu7AwAiEAoJHCdm3qEwNh2SD3ldKvxTAj2gg0gEE2gWTFd7U4agg="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.0.87.tgz_1508867222463_0.0842288937419653"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.0.88":{"name":"grunt-idra3","version":"0.0.88","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","sonar-scanner":"^1.0.1"},"dependencies":{"async":"2.1.4","command-line-args":"4.0.6","extend":"3.0.1","glob":"7.1.2","mime":"1.3.4","request":"2.69.0","url":"0.11.0","valid-url":"1.0.9","xml2js":"0.4.16"},"_id":"grunt-idra3@0.0.88","_shasum":"3f6ad87e115b50b951a30c2838501dd5ab778fa8","_from":".","_npmVersion":"2.15.9","_nodeVersion":"4.6.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"3f6ad87e115b50b951a30c2838501dd5ab778fa8","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.0.88.tgz","integrity":"sha512-VYo31aHurhd0zyDxJlCJm51TGXaHATeMxWkDQKRf3uzxbmWRD8+KaE2DmB6EN7I0LKnBQGw4t3NuoNW4U2817g==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIF/xi/X6ALzy9wt/tG/YX1wVUNBE7FzUb/iPyPAi+CNBAiAqpvLndgwr/kYN07dEkijV32wzSLhi8LIRhL1UxGD1ng=="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.0.88.tgz_1508884907275_0.9193325638771057"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.0":{"name":"grunt-idra3","version":"0.1.0","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","sonar-scanner":"^1.0.1"},"dependencies":{"async":"2.1.4","command-line-args":"4.0.6","extend":"3.0.1","glob":"7.1.2","mime":"1.3.4","request":"2.69.0","url":"0.11.0","valid-url":"1.0.9","xml2js":"0.4.16"},"_id":"grunt-idra3@0.1.0","_shasum":"2febbeb70e1b9a073774dafa1322a62e85a8726c","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.2","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"2febbeb70e1b9a073774dafa1322a62e85a8726c","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.0.tgz","integrity":"sha512-PtQO9v7PrrqDeO/6yLm6bU90VG68UHWFmWExfqjCjYAVWjnZlapk6q6t8Kz/rHQmDuwqsMTj0BYQsysZJcO2YA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCqZtLPba74TQSLx6k0Zw/jzA2fnUrXlvPFKLpW6Y5V9gIhAK2u9X3baDt+GYUjw4onhZEdEnFuevM6ud2Sux6JTtQd"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.1.0.tgz_1510181409192_0.4872463522478938"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.1":{"name":"grunt-idra3","version":"0.1.1","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","sonar-scanner":"^1.0.1"},"dependencies":{"async":"2.1.4","command-line-args":"4.0.6","extend":"3.0.1","glob":"7.1.2","mime":"1.3.4","request":"2.69.0","url":"0.11.0","valid-url":"1.0.9","xml2js":"0.4.16"},"_id":"grunt-idra3@0.1.1","_shasum":"e74fda71ba0e8c3726ac4db715bd256050b8131a","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.2","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"e74fda71ba0e8c3726ac4db715bd256050b8131a","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.1.tgz","integrity":"sha512-B96FlEcxtcuMwPedQWRk+KKRolu4C7r/K5UQhwjJDkIfnYlZA6OcTu+/ay6dAwJRzQVLplLeLbCDdgl4xJGOTQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIG2Ctqrv8Ev4FNGGebVJd1cyHAbEurDITkm7M5DSg0nJAiAiZHKobn284fOMW/FZXWR23PeoBv1FsJzs2KElLoNGVA=="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.1.1.tgz_1510182309619_0.373661189340055"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.2":{"name":"grunt-idra3","version":"0.1.2","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","sonar-scanner":"^1.0.1"},"dependencies":{"async":"2.1.4","command-line-args":"4.0.6","extend":"3.0.1","glob":"7.1.2","mime":"1.3.4","request":"2.69.0","url":"0.11.0","valid-url":"1.0.9","xml2js":"0.4.16"},"_id":"grunt-idra3@0.1.2","_shasum":"cc8578733cf666d9c58dc3e55a2ae64f9628a1d1","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.2","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"cc8578733cf666d9c58dc3e55a2ae64f9628a1d1","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.2.tgz","integrity":"sha512-kyP5+YbnMtGSdNnvjbENHRwD3/abW9IV4Iq6Yd0dCx5Pz72G/7aBNdurZsnFUxHu9Sb9DvNrVk1JC1QF8SRJ/Q==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDEtZMlWMgHG3+NSE1fJlkX1AyeiDxxdxgVPXDjtD/CRQIhAMs08GNHjDE1y32tCxDKT2zUaOCm/Gs6iyq32+K1Wqad"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.1.2.tgz_1510614566607_0.9755205863621086"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.3":{"name":"grunt-idra3","version":"0.1.3","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","sonar-scanner":"^1.0.1"},"dependencies":{"async":"2.1.4","command-line-args":"4.0.6","extend":"3.0.1","glob":"7.1.2","mime":"1.3.4","request":"2.69.0","url":"0.11.0","valid-url":"1.0.9","xml2js":"0.4.16"},"_id":"grunt-idra3@0.1.3","_shasum":"96480f1947382fefee07d5e447bb2d757c49bc4f","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.2","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"96480f1947382fefee07d5e447bb2d757c49bc4f","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.3.tgz","integrity":"sha512-AgAIaRtG5ddi101vvJ3tT7YX6QbScAcAqpnWohnB2vqpZkS1Mq3Ui35B8fmkNrDf1AyzB4BU8gEq5gEarGBYqw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDkkmsmx8mihKPdDhFOCtk8FptCRizqkkGWzBhCLezuhAIhAJjhrXB967721K2+1VNSYsx0apb4PYgsN9BiZD2CvDS0"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.1.3.tgz_1510957150026_0.4136912061367184"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.4":{"name":"grunt-idra3","version":"0.1.4","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","sonar-scanner":"^1.0.1"},"dependencies":{"async":"2.1.4","command-line-args":"4.0.6","extend":"3.0.1","glob":"7.1.2","mime":"1.3.4","request":"2.69.0","url":"0.11.0","valid-url":"1.0.9","xml2js":"0.4.16"},"_id":"grunt-idra3@0.1.4","_shasum":"228cd5d57579d069abda2a0cbe84fed8773b9fc4","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.2","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"228cd5d57579d069abda2a0cbe84fed8773b9fc4","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.4.tgz","integrity":"sha512-9faJhg8Ot6cJqM30rf1O5zMC49Og2oGPymSbf2iWcVsLtqvCZJKhVxrE6qf2WN2cybHoyUSJx3HfsSyHi0H3LA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIGzBimuurqGrfGuHL6rFNvW/wpXxSjQ0S3cBmyephAsbAiB9QN2KTqolsRPJjz9A4p6BEHD+DeUKNj4tTEOJSUdH3g=="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.1.4.tgz_1513710075991_0.05739418952725828"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.5":{"name":"grunt-idra3","version":"0.1.5","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.2.5","sonar-scanner":"^1.0.1"},"dependencies":{"async":"2.1.4","command-line-args":"4.0.6","extend":"3.0.1","glob":"7.1.2","mime":"1.3.4","request":"2.69.0","url":"0.11.0","valid-url":"1.0.9","xml2js":"0.4.16"},"_id":"grunt-idra3@0.1.5","_shasum":"06b2113c266cc25139c723d2541b82e59045d7c3","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.2","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"06b2113c266cc25139c723d2541b82e59045d7c3","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.5.tgz","integrity":"sha512-0CEkRVF8VOUm20QDL4HwUwG+tN7xNeDXFd10VhGWEIgYB6zmPFEAPNzg6Z/rE1HIqjuDdS2Mgqm6QU0heuMbRw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIE2MmGrY6iW4rsSip+VtwFE2EIATTcEK+z1QbfkpTVT2AiAiv4jYSaGVdAo4IDGGRROk3ivSxQQ2wi85pkFsQy4/2Q=="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.1.5.tgz_1516108977020_0.8847123321611434"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.6":{"name":"grunt-idra3","version":"0.1.6","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.2.5","sonar-scanner":"^1.0.1"},"dependencies":{"async":"2.1.4","command-line-args":"4.0.6","extend":"3.0.1","glob":"7.1.2","mime":"1.3.4","request":"2.69.0","url":"0.11.0","valid-url":"1.0.9","xml2js":"0.4.16"},"_id":"grunt-idra3@0.1.6","_shasum":"e43172d3188daf862a6afe28c984c3b6bd214b26","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.2","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"e43172d3188daf862a6afe28c984c3b6bd214b26","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.6.tgz","integrity":"sha512-0/k6nA7xu6kcLsOevsLbG5Yu0RFQKMkmQF6cJvKPAl2WDuLSt5FaINFHN/qRghTmZCx1Aeux57lPf7Yr4db8JQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQD6XaVKZTOumJGhb+jZA1NmiXvuNEtHI9MqGGHQa60CswIhAIX8NCflJd4GoBhQaUwSsGgSoXLg5U6m5kiXBq59RD4U"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.1.6.tgz_1516110311753_0.43028702470473945"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.7":{"name":"grunt-idra3","version":"0.1.7","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.2.5","sonar-scanner":"^1.0.1"},"dependencies":{"async":"2.1.4","command-line-args":"4.0.6","extend":"3.0.1","glob":"7.1.2","mime":"1.3.4","request":"2.69.0","url":"0.11.0","valid-url":"1.0.9","xml2js":"0.4.16"},"_id":"grunt-idra3@0.1.7","_shasum":"cc7732a0df74ea6705f2eb2cb5cdd5af9ca5c17c","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.2","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"cc7732a0df74ea6705f2eb2cb5cdd5af9ca5c17c","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.7.tgz","integrity":"sha512-4znMxCl88AU9eTmSkasnrT9nMV0t+PM0lm6nBkly76vjxavyL/6cOJCWt6FYUP4DhU67b0wlSMZsS9RSoEFomg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEMCHxhHxxIM4gPy+3jaFlKFvmMfoY/m/X8xHeHSXooDf5ECIBE3p/vj4SIYFo9Jr7FH1A9VSmuowlLoxCdh4xBqjM8q"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.1.7.tgz_1516204032254_0.13476487784646451"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.8":{"name":"grunt-idra3","version":"0.1.8","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.2.5","sonar-scanner":"^1.0.1"},"dependencies":{"async":"2.1.4","command-line-args":"4.0.6","extend":"3.0.1","glob":"7.1.2","mime":"1.3.4","request":"2.69.0","url":"0.11.0","valid-url":"1.0.9","xml2js":"0.4.16"},"_id":"grunt-idra3@0.1.8","_shasum":"6a605009183a9b30466a461f8236fcc42b74538b","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.2","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"6a605009183a9b30466a461f8236fcc42b74538b","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.8.tgz","integrity":"sha512-lHdIWnlitTlPPwuBxR2Zljdo5ZcxkzYB4VDtvJ2SujHEVpY+mK6TiekFl/JYaz0fItjNGZ3iKWBt8baIQyE67w==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCm/DTg+EyD9gPaWk5MdtGklCmQGgr3OaBGxbShGZMvKwIhAIzGhMTfqzk79ZmSmMJNQJDcWtIGLCyWVIJz75+8UzSM"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.1.8.tgz_1516913549970_0.5705440847668797"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.9":{"name":"grunt-idra3","version":"0.1.9","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.2.5","sonar-scanner":"^1.0.1"},"dependencies":{"async":"2.1.4","command-line-args":"4.0.6","extend":"3.0.1","glob":"7.1.2","mime":"1.3.4","request":"2.69.0","url":"0.11.0","valid-url":"1.0.9","xml2js":"0.4.16"},"_id":"grunt-idra3@0.1.9","_shasum":"430d29b37c596dcd84371e36166db58ebdf408e0","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.2","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"430d29b37c596dcd84371e36166db58ebdf408e0","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.9.tgz","integrity":"sha512-mH8t8yOa/oz4sHFldWm34JFkqBp9ZnOJX5/4PnbH9ejqpL75Lwn4CDD6Ur52Z3BVf6ptgGGfgKiRdufm518mLw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQD1GK64uCKiYgY/zUoYfJ3iIZvJa8/3M4/vSqH/NW5SMQIhAPSh/YoNpFFiesd70abUBEHI98dUdSHOKH6XI1oiiX1u"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.1.9.tgz_1516924765701_0.4101740720216185"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.10":{"name":"grunt-idra3","version":"0.1.10","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.2.5","sonar-scanner":"^1.0.1"},"dependencies":{"async":"2.1.4","command-line-args":"4.0.6","extend":"3.0.1","glob":"7.1.2","mime":"1.3.4","request":"2.69.0","url":"0.11.0","valid-url":"1.0.9","xml2js":"0.4.16"},"_id":"grunt-idra3@0.1.10","_shasum":"266706afa4e8957625f0ae0e32b12cbbca763230","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.2","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"266706afa4e8957625f0ae0e32b12cbbca763230","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.10.tgz","integrity":"sha512-I9BwLp1h/ceAOEa5bW9qtxAmXA8ZTtaJysjS4qNLd+r7vqVYDTFrmOrky6hojkY/fIjBLQfTIZOET+cHSWw1AQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDimuKT4dFOZhMeGOxXrX8CqiQ8yMo6lMgQZMwp3TqybwIhAL7iYNNrTkgsHWlFndPGeJrceeyBDM2h+0xxriFrvObl"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.1.10.tgz_1516930231146_0.5665456876158714"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.11":{"name":"grunt-idra3","version":"0.1.11","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.2.5","sonar-scanner":"^1.0.1"},"dependencies":{"async":"2.1.4","command-line-args":"4.0.6","extend":"3.0.1","glob":"7.1.2","mime":"1.3.4","request":"2.69.0","url":"0.11.0","valid-url":"1.0.9","xml2js":"0.4.16"},"_id":"grunt-idra3@0.1.11","_shasum":"c11907c8331ff362d4301c39c6df0952a871a6b1","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.2","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"c11907c8331ff362d4301c39c6df0952a871a6b1","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.11.tgz","integrity":"sha512-2I8mSXf2qnd7KxBJ+hhdxiu/ofOeyChfe/NpMfcFs2cYCcECgD3uCs/l9oACYC6j+zTGZgc5HiHpeAjO4TnB0Q==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIDLkgdYOoOuFZeePUU4x7btu/GR8ZZifZOf0peBA3VvLAiEAtzjYQv4g6h5QKToqHRP7DD+p/HGmh/ihJwtn/dPIMa0="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.1.11.tgz_1517258843979_0.8694119530264288"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.12":{"name":"grunt-idra3","version":"0.1.12","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.2.5","sonar-scanner":"^1.0.1"},"dependencies":{"async":"2.1.4","command-line-args":"4.0.6","extend":"3.0.1","glob":"7.1.2","mime":"1.3.4","request":"2.69.0","url":"0.11.0","valid-url":"1.0.9","xml2js":"0.4.16"},"_id":"grunt-idra3@0.1.12","_shasum":"3c6f286a4176905c31160fdece465954f789085d","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.2","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"3c6f286a4176905c31160fdece465954f789085d","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.12.tgz","integrity":"sha512-gaIj2FGfd+1swZsB6Ubt/7qs04TsDD4YWxJXP9YZ2gNK8DDVVk96mYLcMZi3PxoWeTMNkZ3S8gHe13ZkTDK9sw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDP2CpHTOW90SDkGDZFFwJwkh7ePB3I0TJ3pZr5xk6sEgIgdU1vJaD4ZZaASDQOYhInPXBpoqbc7YR6kwE3df/n/0k="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3-0.1.12.tgz_1517321065634_0.07138888700865209"},"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.13":{"name":"grunt-idra3","version":"0.1.13","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.2.5","sonar-scanner":"^1.0.1"},"dependencies":{"async":"2.1.4","command-line-args":"4.0.6","extend":"3.0.1","glob":"7.1.2","mime":"1.3.4","request":"2.83.0","url":"0.11.0","valid-url":"1.0.9","xml2js":"0.4.16"},"_id":"grunt-idra3@0.1.13","_shasum":"c2b436f56bce9830918c12d65fe46ba909d57edb","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.2","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"c2b436f56bce9830918c12d65fe46ba909d57edb","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.13.tgz","fileCount":20,"unpackedSize":235245,"integrity":"sha512-KkvoUbutAzjyzYMmZ2D9O/l57qvW1eMfQrpYPkVPAqzy9e4p2xcshXKpdOcdgxdunJE9MglZZWUc46dlsA2iag==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIB2ONUQv3gQyxm1eHrfB4ru0GNlT+JN/K1HUePhbET33AiEA720JixO67LbHN28+dJ2o83SfaqD+dQcDH1uWs9y0fr4="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.13_1518482407781_0.6976989385238876"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.14":{"name":"grunt-idra3","version":"0.1.14","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.2.5","sonar-scanner":"^1.0.1"},"dependencies":{"async":"2.1.4","command-line-args":"4.0.6","extend":"3.0.1","glob":"7.1.2","mime":"1.3.4","request":"2.83.0","url":"0.11.0","valid-url":"1.0.9","xml2js":"0.4.16"},"_id":"grunt-idra3@0.1.14","_shasum":"20ffc21b4d02c8095d5a094b182c18087ce0653d","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.2","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"20ffc21b4d02c8095d5a094b182c18087ce0653d","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.14.tgz","fileCount":20,"unpackedSize":237465,"integrity":"sha512-YIzPGpdPNJqL78JwmXVuRtUmh+WHe838Nc/xJYeV9sVuZsDbettLtu6ZIwLwy7SiSdToCw13CjzIfubtzix3dw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIGj6AcdKyMKGvLhAU8IjOnCIdxq3p6XBkawIhA+tQZzZAiEA4WiW8htokOiC/rjVNDC0apc6U8JqU6tE9QDJR4vgxdE="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.14_1519420952155_0.05216529635619782"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.15":{"name":"grunt-idra3","version":"0.1.15","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.2.5","sonar-scanner":"^1.0.1"},"dependencies":{"async":"2.1.4","command-line-args":"4.0.6","extend":"3.0.1","glob":"7.1.2","mime":"1.3.4","request":"2.83.0","url":"0.11.0","valid-url":"1.0.9","xml2js":"0.4.16"},"_id":"grunt-idra3@0.1.15","_shasum":"30db77c7f80556bef3a97ccf9abf567fc8d4744a","_from":".","_npmVersion":"3.10.10","_nodeVersion":"6.11.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"30db77c7f80556bef3a97ccf9abf567fc8d4744a","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.15.tgz","fileCount":24,"unpackedSize":224569,"integrity":"sha512-r7fCLW4mSFR7Pe0SFyqd3YZP9+0Zfnu9p6TW8iDtOuB6mK1YFCmY5Twzn7ak/Typia9PwFPqjIJCAOKiu5UfrQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDi3E6mM5Of42SEpjle0bOhknJG/w8b+f4SA03OeVDqDQIgf0Jd0W9FwHVIBM+YRJyXrraiMCW/tZoDoAf9QNWIouA="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.15_1519756359749_0.20682592207532635"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.16":{"name":"grunt-idra3","version":"0.1.16","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.2.5","sonar-scanner":"^1.0.1"},"dependencies":{"async":"2.1.4","command-line-args":"4.0.6","extend":"3.0.1","glob":"7.1.2","mime":"1.3.4","request":"2.83.0","url":"0.11.0","valid-url":"1.0.9","xml2js":"0.4.16"},"readme":"# idra\n\n> Command Line utility for integrating with IBM® DevOps Insights\n\nTo install this utility\n```\nnpm install -g grunt-idra3\n```\n\n## Getting Started\n\nUse this utility to integrate IBM® DevOps Insights with Travis CI, Concourse, IBM Urban Code Deploy, IBM Continuous Delivery Pipelines and other CI/CD tools. If you are using Jenkins, use this [Jenkins plugin](https://plugins.jenkins.io/ibm-cloud-devops) instead.\n\nUsing this utility, you can\n- publish build records, test records and deploy records to IBM® DevOps Insights \n- make go/no-go decisions about a build's quality by using a Gate policy \n\nFor samples of dashboards in IBM® DevOps Insights, see [Value Proposition](https://plugins.jenkins.io/ibm-cloud-devops).\n\nFor more information about IBM DevOps Insights, see [the official documentation](https://console.bluemix.net/docs/services/DevOpsInsights/index.html).\n\n### Scenarios\nThis document covers two scenarios:\n1. You are integrating DevOps Insights with IBM Continuous Delivery tool.\n2. You are integrating DevOps Insights with other CI/CD tools (e.g., Travis CI, Concourse, IBM Urban Code Deploy, others)\n\n### Prerequisites\n\nTo use the CLI, you need to do the following. These steps should take about 10 minutes.\n\n1. A valid IBM Cloud account. If you don't have one, [register here](https://console.bluemix.net/registration).\n\n2. Once you have an account, you can create an API Key. Log in to [IBM Cloud](https://console.bluemix.net). Click on **Manage**->**Security**->**Platform API Key**. On that screen, create an API Key.\n\n3. An IBM Continuous Delivery toolchain. To create a toolchain:\n- Go to https://console.bluemix.net/devops\n- Click on **Create a Toolchain** button and then select **Build Your Own Toolchain** template. \n- In the next screen, click **Create**.\n- From the URL displayed in the browser, make note of your toolchain id. For example, if your URL is https://console.bluemix.net/devops/toolchains/05572df3-01dc-441b-911d-b2202fe33f96, the toolchain id is the long string after **toolchains/**\n- You can always navigate to your toolchain by [clicking here](https://console.bluemix.net/devops)\n\n4. Add DevOps Insights tool to your toolchain\n- Go to your toolchain\n- Click on **Add a Tool** button\n- Select DevOps Insights tool and click **Create Integration** button\n\n5. Your CI/CD tool must have Node.js® 4.x or greater. \n\n### Environment Variables \n\nIf you are using Travis, Concourse or any CI/CD tool other than the IBM Continuous Delivery pipeline, then set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|ORGANIZATION_NAME| **Required.** The Bluemix organization's name|\n|TOOLCHAIN_ID| **Required.** The toolchain's GUID |\n|IBM_CLOUD_API_KEY| **Required.** The Bluemix user's Api key|\n|BUILD_NUMBER| **Required.** Any string that identifies the build |\n|LOGICAL_APP_NAME| **Required.** The application's name.|\n\n\n\nIf you are using IBM Continuous Delivery pipeline, you need to set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|BUILD_PREFIX| **Required.** Any string. For example, the Git branch name. |\n|LOGICAL_APP_NAME| **Required.** The application's name.|\n|PATH|**Required.** In order to have required version of Node.js in your path, set the PATH variable before invoking the utility: `export PATH=/opt/IBM/node-v4.2/bin:$PATH`|\n\nIf you are using IBM Continuous Delivery pipeline and if you want to publish Insights data to another toolchain, then set the following environment variables. \n\n|Name|Description|\n|-----|-----|\n|ORGANIZATION_NAME or ORGANIZATION_ID| **Required.** The target Bluemix organization's name or GUID. |\n|TOOLCHAIN_ID| **Required.** The target toolchain's GUID. The toolchain id provided here should be from the same environment pointed by the BLUEMIX_CONSOLE_URL (If BLUEMIX_CONSOLE_URL is not provided then it should be in USSouth Bluemix public ) |\n|IBM_CLOUD_API_KEY| _Optional._ If the target toolchain is owned by different user than that owner's Bluemix Api key|\n|BUILD_PREFIX| **Required.** Any string. For example, the Git branch name. |\n|LOGICAL_APP_NAME| **Required.** The application's name.|\n|PATH|**Required,** In order to have required version of Node.js in your path, set the PATH variable before invoking the utility: `export PATH=/opt/IBM/node-v4.2/bin:$PATH`|\n\n\n\nIf you are using IBM UrbanCode Deploy, DevOps Insights relies on the previous set of variables, and this one:\n\n|Name|Description|\n|-----|-----|\n|UCD_REQUEST_ID| This maps to the ${p:request.id} property value. |\n\n### Enabling Debug logs\nIf you want to enable debug logs for the DevOps Insights CLI, set the `IDRA_DEBUG` environment variable to `true`. This works in all environments.\n\n|Name|Description|\n|-----|-----|\n|IDRA_DEBUG| When this value is `true`, the DevOps Insights CLI's debugging mode is enabled. By default, the value is `false`. |\n\n\n### Using the CLI\n\nSet [environment details](#environment-details) as described above. Ensure that Node.js 4.2 or higher is avaialble in your CI/CD tool.\n\nTo install this utility, use `npm install -g grunt-idra3`\n\nThen you can invoke the CLI with the `idra` command. You can run the CLI in any pipeline job's command script. For example, this command uploads functional verification test results to DevOps Insights:\n\n```\n# Upload test results\nidra --publishtestresult --filelocation=\"results.json\" --type=fvt\n```\n\n\n## Uploading Build Records\nUse the `--publishbuildrecord` command (alias `-b`) to upload build records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishbuildrecord --branch= --repositoryurl= --commitid= --status= [--joburl=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--branch`|`-B` | **Required.** The repository branch on which the build is being performed. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--repositoryurl`|`-R` | **Required.** The url of the git repository. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--commitid`|`-C` | **Required.** The git commit id. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--status`|`-S` | **Required.** The build status. This value must be either `pass` or `fail`. |\n|`--joburl`|`-J` | _Optional_. The URL to the job's build logs. |\n\n\n### An example command\n\nIn this an example, the command uploads a build record from a pipeline job.\n\n```shell\nidra --publishbuildrecord --branch=master --repositoryurl=\"https://github.com/oic/dlms.git\" --commitid=dff7884b9168168d91cb9e5aec78e93db0fa80d9 --status=pass\n```\n\n## Uploading Test Results\n\nUse the `--publishtestresult` command (alias `-p`) to upload results from these test types to DevOps Insights:\n\n* Unit tests\n* Code coverage tests\n* Functional verification tests (FVT)\n* Static security scans from IBM Application Security on Cloud\n* Dynamic app scans from IBM Application Security on Cloud\n* [SonarQube results](#uploading-sonarqube-results)\n\n\n### Command syntax and options\n\n```shell\nidra --publishtestresult --filelocation= --type= [--tool=] [--drilldownurl=] [--env=] [--token=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--filelocation`| `-F` |**Required.** The location of the test results that you want to upload. This can be a single file, an entire directory, or multiple files that match a wildcard expression.|\n|`--type`| `-T` |**Required.** The type of test results that you want to upload. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, and `sonarqube` for SonarQube scans. In addition to these types you can also use a custom quality data set tag to upload test results of different type.|\n|`--tool`| `-L` |_Optional_. The name for the test tool. |\n|`--drilldownurl`| `-U` |_Optional._ A URL where more information about the test results can be found. If this URL is invalid, the option is ignored. |\n|`--env`| `-E` |_Optional._ The environment name to associate with the test results. This option is ignored for unit tests, code coverage tests, and static security scans. |\n|`--token`| `-K` |_Optional_. This is a SonarQube token. This flag is valid only if the type specified is `sonarqube`. It is used by the CLI to pull additional information from the SonarQube server. |\n\n### An example command\n\nIn this example, the command uploads all JSON-formatted FVT results from a directory to DevOps Insights. Additionally, a test tool is declared, a test result URL is given, and a logical staging environment is provided. Specifying an environment is especially important when you want your results to be analyzed alongside other activities that take place in that same environment.\n\n```shell\nidra --publishtestresult --filelocation=\"tests/fvt/*.json\" --type=fvt --tool=\"your-test-runner\" -drilldownurl=\"https://example.com/testinfo\" --env=\"staging\"\n```\n\n## Uploading SonarQube Results\nTo upload data from SonarQube, you must provide the SonarQube server token using ```--token```. Your SonarQube server is not required to be accessible from IBM Cloud.\n\nAfter you run a scan using SonarQube, you can upload SonarQube results by running this command.\n\n```idra --publishtestresult --filelocation=.scannerwork/report-task.txt --type=sonarqube --token=234234434```\n\nIn the above command, report-task.txt is a file generated during the SonarQube scan.\n\nIf this command fails for some reason, you can enable logs by setting IDRA_DEBUG environment variable to true.\n\nIf you are using self-signed certificates for SonarQube server, you will need to set ```export NODE_TLS_REJECT_UNAUTHORIZED=0```\n\n\n## Uploading Vulnerability Scan Results\n\nUse the `--publishvulnerabilityresult` command (alias `-v`) to upload [vulnerability advisor](https://console.bluemix.net/docs/containers/va/va_index.html) results to DevOps Insights:\n\n### Command syntax and options\n\n```shell\nidra --publishvulnerabilityresult --image= --account=\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--image`| `-M` |**Required.** Name of image including the repository and the tag.|\n|`--account`| `-O` |**Required.** The unique ID for your IBM Cloud account. Run 'bx cr info' to get the ID of the target account. |\n\n### An example command\n\nIn this example, the command uploads the vulnerability scan details of the image specified, to DevOps Insights. It gets the details by querying the relevant image repository.\n\n```shell\nidra --publishvulnerabilityresult --image=\"registry.ng.bluemix.net/auser/hello-containers-auser-1129:1\" --account=65fc31e13b143434540bcb495\n```\n## Uploading Deployment Records\nUse the `--publishdeployrecord` command (alias `-d`) to upload deployment records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishdeployrecord --env= --status= [--joburl=] [--appurl=] [--deployableid=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--env`|`-E` | **Required.** The environment where the pipeline job deployed the app. |\n|`--status`|`-S` | **Required.** The deployment status. This value must be either `pass` or `fail`. |\n|`--joburl`|`-J` | _Optional_. The URL to the job's deployment logs. |\n|`--appurl`|`-A` | _Optional._ The URL where the deployed app is running. |\n|`--deployableid`| `-I` | _Optional._ The deployed app's application ID. You can get the ID by running the Cloud Foundry CLI's `cf env` command. The application ID is listed under `VCAP_APPLICATION`. |\n\n### An example command\n\nIn this an example, the command uploads a deployment record from a pipeline job. The deployment is to the \"staging\" environment. The deployment is successful and the app is running at a specified URL.\n\n```shell\nidra --publishdeployrecord --env=\"staging\" --status=pass --appurl=\"https://app.staging.example.com\"\n```\n\n## Making Decisions about Build Quality using Gate Policies\n\nTo use this feature, create a quality policy by using the user interface. Navigate to your toolchain, click on **DevOps Insights** card. Then on the left menu, click on **Deployment Risk**->**Policies**. \n\nUse the `--evaluategate` command (alias `-g`) to request a gate decision for a DevOps Insights policy in your pipeline. If the policy is satisfied, the pipeline continues running. If not, and you use the `--forcedecision` flag, the pipeline stops running.\n\n### Command syntax and options\n\n```shell\nidra --evaluategate --policy= [--forcedecision] [--env=] [--type=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--policy`|`-P` | **Required.** The name of the policy that the gate uses to make its decision. |\n|`--forcedecision`|`-D` | _Optional._ This flag causes the process to exit with an error code if the policy evaluation fails. If you do not include it, the pipeline will run regardless of the gate's decision. |\n|`--type`|`-E` | _Optional_. A rule type to consider. If you include this option, only rules of this type are considered in the decision-making process. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, and `sonarqube` for SonarQube scans. |\n|`--env`|`-T` | _Optional._ The environment that is considered in the decision-making process. Test results that are not associated with this environment are excluded from the process. |\n\n\n\n## Release History\n_(Nothing yet)_\n","readmeFilename":"README.md","_id":"grunt-idra3@0.1.16","_shasum":"8a6badfc5b584c303b38a0a0209e39a0bd39c5f3","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.2","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"8a6badfc5b584c303b38a0a0209e39a0bd39c5f3","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.16.tgz","fileCount":19,"unpackedSize":200782,"integrity":"sha512-I+HoxX3aoJBKuN4K47Q4fZ5dfet+qwt58bC+XA/xgC4nnvhsvIKU/y03OJrIgvTMCjrsUqggEtRPHnbiYEdFzA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIErBZE4I1oNx88mcQ5jBb4aWtqZVM2VPIBCmtPLKlx82AiEA9GJFEIfjU6NuQjutR66s98cv1LaiiY750bT0dLMc+ts="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.16_1523391941794_0.3367857208305436"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.17":{"name":"grunt-idra3","version":"0.1.17","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.2.5","sonar-scanner":"^1.0.1"},"dependencies":{"async":"2.1.4","command-line-args":"4.0.6","extend":"3.0.1","glob":"7.1.2","mime":"1.3.4","request":"2.83.0","url":"0.11.0","valid-url":"1.0.9","xml2js":"0.4.16"},"readme":"# idra\n\n> Command Line utility for integrating with IBM® DevOps Insights\n\nTo install this utility\n```\nnpm install -g grunt-idra3\n```\n\n## Getting Started\n\nUse this utility to integrate IBM® DevOps Insights with Travis CI, Concourse, IBM Urban Code Deploy, IBM Continuous Delivery Pipelines and other CI/CD tools. If you are using Jenkins, use this [Jenkins plugin](https://plugins.jenkins.io/ibm-cloud-devops) instead.\n\nUsing this utility, you can\n- publish build records, test records and deploy records to IBM® DevOps Insights \n- make go/no-go decisions about a build's quality by using a Gate policy \n\nFor samples of dashboards in IBM® DevOps Insights, see [Value Proposition](https://plugins.jenkins.io/ibm-cloud-devops).\n\nFor more information about IBM DevOps Insights, see [the official documentation](https://console.bluemix.net/docs/services/DevOpsInsights/index.html).\n\n### Scenarios\nThis document covers two scenarios:\n1. You are integrating DevOps Insights with IBM Continuous Delivery tool.\n2. You are integrating DevOps Insights with other CI/CD tools (e.g., Travis CI, Concourse, IBM Urban Code Deploy, others)\n\n### Prerequisites\n\nTo use the CLI, you need to do the following. These steps should take about 10 minutes.\n\n1. A valid IBM Cloud account. If you don't have one, [register here](https://console.bluemix.net/registration).\n\n2. Once you have an account, you can create an API Key. Log in to [IBM Cloud](https://console.bluemix.net). Click on **Manage**->**Security**->**Platform API Key**. On that screen, create an API Key.\n\n3. An IBM Continuous Delivery toolchain. To create a toolchain:\n- Go to https://console.bluemix.net/devops\n- Click on **Create a Toolchain** button and then select **Build Your Own Toolchain** template. \n- In the next screen, click **Create**.\n- From the URL displayed in the browser, make note of your toolchain id. For example, if your URL is https://console.bluemix.net/devops/toolchains/05572df3-01dc-441b-911d-b2202fe33f96, the toolchain id is the long string after **toolchains/**\n- You can always navigate to your toolchain by [clicking here](https://console.bluemix.net/devops)\n\n4. Add DevOps Insights tool to your toolchain\n- Go to your toolchain\n- Click on **Add a Tool** button\n- Select DevOps Insights tool and click **Create Integration** button\n\n5. Your CI/CD tool must have Node.js® 4.x or greater. \n\n### Environment Variables \n\nIf you are using Travis, Concourse or any CI/CD tool other than the IBM Continuous Delivery pipeline, then set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|ORGANIZATION_NAME| **Required.** The Bluemix organization's name|\n|TOOLCHAIN_ID| **Required.** The toolchain's GUID |\n|IBM_CLOUD_API_KEY| **Required.** The Bluemix user's Api key|\n|BUILD_NUMBER| **Required.** Any string that identifies the build |\n|LOGICAL_APP_NAME| **Required.** The application's name.|\n\n\n\nIf you are using IBM Continuous Delivery pipeline, you need to set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|BUILD_PREFIX| **Required.** Any string. For example, the Git branch name. |\n|LOGICAL_APP_NAME| **Required.** The application's name.|\n|PATH|**Required.** In order to have required version of Node.js in your path, set the PATH variable before invoking the utility: `export PATH=/opt/IBM/node-v4.2/bin:$PATH`|\n\nIf you are using IBM Continuous Delivery pipeline and if you want to publish Insights data to another toolchain, then set the following environment variables. \n\n|Name|Description|\n|-----|-----|\n|ORGANIZATION_NAME or ORGANIZATION_ID| **Required.** The target Bluemix organization's name or GUID. |\n|TOOLCHAIN_ID| **Required.** The target toolchain's GUID. The toolchain id provided here should be from the same environment pointed by the BLUEMIX_CONSOLE_URL (If BLUEMIX_CONSOLE_URL is not provided then it should be in USSouth Bluemix public ) |\n|IBM_CLOUD_API_KEY| _Optional._ If the target toolchain is owned by different user than that owner's Bluemix Api key|\n|BUILD_PREFIX| **Required.** Any string. For example, the Git branch name. |\n|LOGICAL_APP_NAME| **Required.** The application's name.|\n|PATH|**Required,** In order to have required version of Node.js in your path, set the PATH variable before invoking the utility: `export PATH=/opt/IBM/node-v4.2/bin:$PATH`|\n\n\n\nIf you are using IBM UrbanCode Deploy, DevOps Insights relies on the previous set of variables, and this one:\n\n|Name|Description|\n|-----|-----|\n|UCD_REQUEST_ID| This maps to the ${p:request.id} property value. |\n\n### Enabling Debug logs\nIf you want to enable debug logs for the DevOps Insights CLI, set the `IDRA_DEBUG` environment variable to `true`. This works in all environments.\n\n|Name|Description|\n|-----|-----|\n|IDRA_DEBUG| When this value is `true`, the DevOps Insights CLI's debugging mode is enabled. By default, the value is `false`. |\n\n\n### Using the CLI\n\nSet [environment details](#environment-details) as described above. Ensure that Node.js 4.2 or higher is avaialble in your CI/CD tool.\n\nTo install this utility, use `npm install -g grunt-idra3`\n\nThen you can invoke the CLI with the `idra` command. You can run the CLI in any pipeline job's command script. For example, this command uploads functional verification test results to DevOps Insights:\n\n```\n# Upload test results\nidra --publishtestresult --filelocation=\"results.json\" --type=fvt\n```\n\n\n## Uploading Build Records\nUse the `--publishbuildrecord` command (alias `-b`) to upload build records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishbuildrecord --branch= --repositoryurl= --commitid= --status= [--joburl=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--branch`|`-B` | **Required.** The repository branch on which the build is being performed. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--repositoryurl`|`-R` | **Required.** The url of the git repository. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--commitid`|`-C` | **Required.** The git commit id. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--status`|`-S` | **Required.** The build status. This value must be either `pass` or `fail`. |\n|`--joburl`|`-J` | _Optional_. The URL to the job's build logs. |\n\n\n### An example command\n\nIn this an example, the command uploads a build record from a pipeline job.\n\n```shell\nidra --publishbuildrecord --branch=master --repositoryurl=\"https://github.com/oic/dlms.git\" --commitid=dff7884b9168168d91cb9e5aec78e93db0fa80d9 --status=pass\n```\n\n## Uploading Test Results\n\nUse the `--publishtestresult` command (alias `-p`) to upload results from these test types to DevOps Insights:\n\n* Unit tests\n* Code coverage tests\n* Functional verification tests (FVT)\n* Static security scans from IBM Application Security on Cloud\n* Dynamic app scans from IBM Application Security on Cloud\n* [SonarQube results](#uploading-sonarqube-results)\n\n\n### Command syntax and options\n\n```shell\nidra --publishtestresult --filelocation= --type= [--tool=] [--drilldownurl=] [--env=] [--token=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--filelocation`| `-F` |**Required.** The location of the test results that you want to upload. This can be a single file, an entire directory, or multiple files that match a wildcard expression.|\n|`--type`| `-T` |**Required.** The type of test results that you want to upload. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, and `sonarqube` for SonarQube scans. In addition to these types you can also use a custom quality data set tag to upload test results of different type.|\n|`--tool`| `-L` |_Optional_. The name for the test tool. |\n|`--drilldownurl`| `-U` |_Optional._ A URL where more information about the test results can be found. If this URL is invalid, the option is ignored. |\n|`--env`| `-E` |_Optional._ The environment name to associate with the test results. This option is ignored for unit tests, code coverage tests, and static security scans. |\n|`--token`| `-K` |_Optional_. This is a SonarQube token. This flag is valid only if the type specified is `sonarqube`. It is used by the CLI to pull additional information from the SonarQube server. |\n\n### An example command\n\nIn this example, the command uploads all JSON-formatted FVT results from a directory to DevOps Insights. Additionally, a test tool is declared, a test result URL is given, and a logical staging environment is provided. Specifying an environment is especially important when you want your results to be analyzed alongside other activities that take place in that same environment.\n\n```shell\nidra --publishtestresult --filelocation=\"tests/fvt/*.json\" --type=fvt --tool=\"your-test-runner\" -drilldownurl=\"https://example.com/testinfo\" --env=\"staging\"\n```\n\n## Uploading SonarQube Results\nTo upload data from SonarQube, you must provide the SonarQube server token using ```--token```. Your SonarQube server is not required to be accessible from IBM Cloud.\n\nAfter you run a scan using SonarQube, you can upload SonarQube results by running this command.\n\n```idra --publishtestresult --filelocation=.scannerwork/report-task.txt --type=sonarqube --token=234234434```\n\nIn the above command, report-task.txt is a file generated during the SonarQube scan.\n\nIf this command fails for some reason, you can enable logs by setting IDRA_DEBUG environment variable to true.\n\nIf you are using self-signed certificates for SonarQube server, you will need to set ```export NODE_TLS_REJECT_UNAUTHORIZED=0```\n\n\n## Uploading Vulnerability Scan Results\n\nUse the `--publishvulnerabilityresult` command (alias `-v`) to upload [vulnerability advisor](https://console.bluemix.net/docs/containers/va/va_index.html) results to DevOps Insights:\n\n### Command syntax and options\n\n```shell\nidra --publishvulnerabilityresult --image= --account=\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--image`| `-M` |**Required.** Name of image including the repository and the tag.|\n|`--account`| `-O` |**Required.** The unique ID for your IBM Cloud account. Run 'bx cr info' to get the ID of the target account. |\n\n### An example command\n\nIn this example, the command uploads the vulnerability scan details of the image specified, to DevOps Insights. It gets the details by querying the relevant image repository.\n\n```shell\nidra --publishvulnerabilityresult --image=\"registry.ng.bluemix.net/auser/hello-containers-auser-1129:1\" --account=65fc31e13b143434540bcb495\n```\n## Uploading Deployment Records\nUse the `--publishdeployrecord` command (alias `-d`) to upload deployment records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishdeployrecord --env= --status= [--joburl=] [--appurl=] [--deployableid=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--env`|`-E` | **Required.** The environment where the pipeline job deployed the app. |\n|`--status`|`-S` | **Required.** The deployment status. This value must be either `pass` or `fail`. |\n|`--joburl`|`-J` | _Optional_. The URL to the job's deployment logs. |\n|`--appurl`|`-A` | _Optional._ The URL where the deployed app is running. |\n|`--deployableid`| `-I` | _Optional._ The deployed app's application ID. You can get the ID by running the Cloud Foundry CLI's `cf env` command. The application ID is listed under `VCAP_APPLICATION`. |\n\n### An example command\n\nIn this an example, the command uploads a deployment record from a pipeline job. The deployment is to the \"staging\" environment. The deployment is successful and the app is running at a specified URL.\n\n```shell\nidra --publishdeployrecord --env=\"staging\" --status=pass --appurl=\"https://app.staging.example.com\"\n```\n\n## Making Decisions about Build Quality using Gate Policies\n\nTo use this feature, create a quality policy by using the user interface. Navigate to your toolchain, click on **DevOps Insights** card. Then on the left menu, click on **Deployment Risk**->**Policies**. \n\nUse the `--evaluategate` command (alias `-g`) to request a gate decision for a DevOps Insights policy in your pipeline. If the policy is satisfied, the pipeline continues running. If not, and you use the `--forcedecision` flag, the pipeline stops running.\n\n### Command syntax and options\n\n```shell\nidra --evaluategate --policy= [--forcedecision] [--env=] [--type=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--policy`|`-P` | **Required.** The name of the policy that the gate uses to make its decision. |\n|`--forcedecision`|`-D` | _Optional._ This flag causes the process to exit with an error code if the policy evaluation fails. If you do not include it, the pipeline will run regardless of the gate's decision. |\n|`--type`|`-E` | _Optional_. A rule type to consider. If you include this option, only rules of this type are considered in the decision-making process. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, and `sonarqube` for SonarQube scans. |\n|`--env`|`-T` | _Optional._ The environment that is considered in the decision-making process. Test results that are not associated with this environment are excluded from the process. |\n\n\n\n## Release History\n_(Nothing yet)_\n","readmeFilename":"README.md","_id":"grunt-idra3@0.1.17","_shasum":"e0bc9f75228ef93f47e6b87d11bb7e57bfab05fa","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.2","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"e0bc9f75228ef93f47e6b87d11bb7e57bfab05fa","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.17.tgz","fileCount":19,"unpackedSize":200802,"integrity":"sha512-fQ7OEv1C6kWlOe+bTEHqyForrEHPcmZ2gprGjD94J6mdkBpCXp/X9FXi1FEdxIOtbYfyRK+jMDLWwON96O4wGg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCDfwg/189pbWnOXxS3m5R9X+KFJP8ZneWD0shLs2j8iAIhALbY7Hqs+wht0dLcbrU/65krxdW4EoaynIkSIpPkD9l9"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.17_1523548757798_0.7923473088439261"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.18":{"name":"grunt-idra3","version":"0.1.18","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.2.5","sonar-scanner":"^1.0.1"},"dependencies":{"async":"2.1.4","command-line-args":"4.0.6","extend":"3.0.1","glob":"7.1.2","mime":"1.3.4","request":"2.83.0","url":"0.11.0","valid-url":"1.0.9","xml2js":"0.4.16"},"readme":"# idra\n\n> Command Line utility for integrating with IBM® DevOps Insights\n\nTo install this utility\n```\nnpm install -g grunt-idra3\n```\n\n## Getting Started\n\nUse this utility to integrate IBM® DevOps Insights with Travis CI, Concourse, IBM Urban Code Deploy, IBM Continuous Delivery Pipelines and other CI/CD tools. If you are using Jenkins, use this [Jenkins plugin](https://plugins.jenkins.io/ibm-cloud-devops) instead.\n\nUsing this utility, you can\n- publish build records, test records and deploy records to IBM® DevOps Insights \n- make go/no-go decisions about a build's quality by using a Gate policy \n\nFor samples of dashboards in IBM® DevOps Insights, see [Value Proposition](https://plugins.jenkins.io/ibm-cloud-devops).\n\nFor more information about IBM DevOps Insights, see [the official documentation](https://console.bluemix.net/docs/services/DevOpsInsights/index.html).\n\n### Scenarios\nThis document covers two scenarios:\n1. You are integrating DevOps Insights with IBM Continuous Delivery tool.\n2. You are integrating DevOps Insights with other CI/CD tools (e.g., Travis CI, Concourse, IBM Urban Code Deploy, others)\n\n### Prerequisites\n\nTo use the CLI, you need to do the following. These steps should take about 10 minutes.\n\n1. A valid IBM Cloud account. If you don't have one, [register here](https://console.bluemix.net/registration).\n\n2. Once you have an account, you can create an API Key. Log in to [IBM Cloud](https://console.bluemix.net). Click on **Manage**->**Security**->**Platform API Key**. On that screen, create an API Key.\n\n3. An IBM Continuous Delivery toolchain. To create a toolchain:\n- Go to https://console.bluemix.net/devops\n- Click on **Create a Toolchain** button and then select **Build Your Own Toolchain** template. \n- In the next screen, click **Create**.\n- From the URL displayed in the browser, make note of your toolchain id. For example, if your URL is https://console.bluemix.net/devops/toolchains/05572df3-01dc-441b-911d-b2202fe33f96, the toolchain id is the long string after **toolchains/**\n- You can always navigate to your toolchain by [clicking here](https://console.bluemix.net/devops)\n\n4. Add DevOps Insights tool to your toolchain\n- Go to your toolchain\n- Click on **Add a Tool** button\n- Select DevOps Insights tool and click **Create Integration** button\n\n5. Your CI/CD tool must have Node.js® 4.x or greater. \n\n### Environment Variables \n\nIf you are using Travis, Concourse or any CI/CD tool other than the IBM Continuous Delivery pipeline, then set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|ORGANIZATION_NAME| **Required.** The Bluemix organization's name|\n|TOOLCHAIN_ID| **Required.** The toolchain's GUID |\n|IBM_CLOUD_API_KEY| **Required.** The Bluemix user's Api key|\n|BUILD_NUMBER| **Required.** Any string that identifies the build |\n|LOGICAL_APP_NAME| **Required.** The application's name.|\n\n\n\nIf you are using IBM Continuous Delivery pipeline, you need to set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|BUILD_PREFIX| **Required.** Any string. For example, the Git branch name. |\n|LOGICAL_APP_NAME| **Required.** The application's name.|\n|PATH|**Required.** In order to have required version of Node.js in your path, set the PATH variable before invoking the utility: `export PATH=/opt/IBM/node-v4.2/bin:$PATH`|\n\nIf you are using IBM Continuous Delivery pipeline and if you want to publish Insights data to another toolchain, then set the following environment variables. \n\n|Name|Description|\n|-----|-----|\n|ORGANIZATION_NAME or ORGANIZATION_ID| **Required.** The target Bluemix organization's name or GUID. |\n|TOOLCHAIN_ID| **Required.** The target toolchain's GUID. The toolchain id provided here should be from the same environment pointed by the BLUEMIX_CONSOLE_URL (If BLUEMIX_CONSOLE_URL is not provided then it should be in USSouth Bluemix public ) |\n|IBM_CLOUD_API_KEY| _Optional._ If the target toolchain is owned by different user than that owner's Bluemix Api key|\n|BUILD_PREFIX| **Required.** Any string. For example, the Git branch name. |\n|LOGICAL_APP_NAME| **Required.** The application's name.|\n|PATH|**Required,** In order to have required version of Node.js in your path, set the PATH variable before invoking the utility: `export PATH=/opt/IBM/node-v4.2/bin:$PATH`|\n\n\n\nIf you are using IBM UrbanCode Deploy, DevOps Insights relies on the previous set of variables, and this one:\n\n|Name|Description|\n|-----|-----|\n|UCD_REQUEST_ID| This maps to the ${p:request.id} property value. |\n\n### Enabling Debug logs\nIf you want to enable debug logs for the DevOps Insights CLI, set the `IDRA_DEBUG` environment variable to `true`. This works in all environments.\n\n|Name|Description|\n|-----|-----|\n|IDRA_DEBUG| When this value is `true`, the DevOps Insights CLI's debugging mode is enabled. By default, the value is `false`. |\n\n\n### Using the CLI\n\nSet [environment details](#environment-details) as described above. Ensure that Node.js 4.2 or higher is avaialble in your CI/CD tool.\n\nTo install this utility, use `npm install -g grunt-idra3`\n\nThen you can invoke the CLI with the `idra` command. You can run the CLI in any pipeline job's command script. For example, this command uploads functional verification test results to DevOps Insights:\n\n```\n# Upload test results\nidra --publishtestresult --filelocation=\"results.json\" --type=fvt\n```\n\n\n## Uploading Build Records\nUse the `--publishbuildrecord` command (alias `-b`) to upload build records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishbuildrecord --branch= --repositoryurl= --commitid= --status= [--joburl=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--branch`|`-B` | **Required.** The repository branch on which the build is being performed. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--repositoryurl`|`-R` | **Required.** The url of the git repository. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--commitid`|`-C` | **Required.** The git commit id. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--status`|`-S` | **Required.** The build status. This value must be either `pass` or `fail`. |\n|`--joburl`|`-J` | _Optional_. The URL to the job's build logs. |\n\n\n### An example command\n\nIn this an example, the command uploads a build record from a pipeline job.\n\n```shell\nidra --publishbuildrecord --branch=master --repositoryurl=\"https://github.com/oic/dlms.git\" --commitid=dff7884b9168168d91cb9e5aec78e93db0fa80d9 --status=pass\n```\n\n## Uploading Test Results\n\nUse the `--publishtestresult` command (alias `-p`) to upload results from these test types to DevOps Insights:\n\n* Unit tests\n* Code coverage tests\n* Functional verification tests (FVT)\n* Static security scans from IBM Application Security on Cloud\n* Dynamic app scans from IBM Application Security on Cloud\n* [SonarQube results](#uploading-sonarqube-results)\n\n\n### Command syntax and options\n\n```shell\nidra --publishtestresult --filelocation= --type= [--tool=] [--drilldownurl=] [--env=] [--token=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--filelocation`| `-F` |**Required.** The location of the test results that you want to upload. This can be a single file, an entire directory, or multiple files that match a wildcard expression.|\n|`--type`| `-T` |**Required.** The type of test results that you want to upload. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, and `sonarqube` for SonarQube scans. In addition to these types you can also use a custom quality data set tag to upload test results of different type.|\n|`--tool`| `-L` |_Optional_. The name for the test tool. |\n|`--drilldownurl`| `-U` |_Optional._ A URL where more information about the test results can be found. If this URL is invalid, the option is ignored. |\n|`--env`| `-E` |_Optional._ The environment name to associate with the test results. This option is ignored for unit tests, code coverage tests, and static security scans. |\n|`--token`| `-K` |_Optional_. This is a SonarQube token. This flag is valid only if the type specified is `sonarqube`. It is used by the CLI to pull additional information from the SonarQube server. |\n\n### An example command\n\nIn this example, the command uploads all JSON-formatted FVT results from a directory to DevOps Insights. Additionally, a test tool is declared, a test result URL is given, and a logical staging environment is provided. Specifying an environment is especially important when you want your results to be analyzed alongside other activities that take place in that same environment.\n\n```shell\nidra --publishtestresult --filelocation=\"tests/fvt/*.json\" --type=fvt --tool=\"your-test-runner\" -drilldownurl=\"https://example.com/testinfo\" --env=\"staging\"\n```\n\n## Uploading SonarQube Results\nTo upload data from SonarQube, you must provide the SonarQube server token using ```--token```. Your SonarQube server is not required to be accessible from IBM Cloud.\n\nAfter you run a scan using SonarQube, you can upload SonarQube results by running this command.\n\n```idra --publishtestresult --filelocation=.scannerwork/report-task.txt --type=sonarqube --token=234234434```\n\nIn the above command, report-task.txt is a file generated during the SonarQube scan.\n\nIf this command fails for some reason, you can enable logs by setting IDRA_DEBUG environment variable to true.\n\nIf you are using self-signed certificates for SonarQube server, you will need to set ```export NODE_TLS_REJECT_UNAUTHORIZED=0```\n\n\n## Uploading Vulnerability Scan Results\n\nUse the `--publishvulnerabilityresult` command (alias `-v`) to upload [vulnerability advisor](https://console.bluemix.net/docs/containers/va/va_index.html) results to DevOps Insights:\n\n### Command syntax and options\n\n```shell\nidra --publishvulnerabilityresult --image= --account=\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--image`| `-M` |**Required.** Name of image including the repository and the tag.|\n|`--account`| `-O` |**Required.** The unique ID for your IBM Cloud account. Run 'bx cr info' to get the ID of the target account. |\n\n### An example command\n\nIn this example, the command uploads the vulnerability scan details of the image specified, to DevOps Insights. It gets the details by querying the relevant image repository.\n\n```shell\nidra --publishvulnerabilityresult --image=\"registry.ng.bluemix.net/auser/hello-containers-auser-1129:1\" --account=65fc31e13b143434540bcb495\n```\n## Uploading Deployment Records\nUse the `--publishdeployrecord` command (alias `-d`) to upload deployment records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishdeployrecord --env= --status= [--joburl=] [--appurl=] [--deployableid=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--env`|`-E` | **Required.** The environment where the pipeline job deployed the app. |\n|`--status`|`-S` | **Required.** The deployment status. This value must be either `pass` or `fail`. |\n|`--joburl`|`-J` | _Optional_. The URL to the job's deployment logs. |\n|`--appurl`|`-A` | _Optional._ The URL where the deployed app is running. |\n|`--deployableid`| `-I` | _Optional._ The deployed app's application ID. You can get the ID by running the Cloud Foundry CLI's `cf env` command. The application ID is listed under `VCAP_APPLICATION`. |\n\n### An example command\n\nIn this an example, the command uploads a deployment record from a pipeline job. The deployment is to the \"staging\" environment. The deployment is successful and the app is running at a specified URL.\n\n```shell\nidra --publishdeployrecord --env=\"staging\" --status=pass --appurl=\"https://app.staging.example.com\"\n```\n\n## Making Decisions about Build Quality using Gate Policies\n\nTo use this feature, create a quality policy by using the user interface. Navigate to your toolchain, click on **DevOps Insights** card. Then on the left menu, click on **Deployment Risk**->**Policies**. \n\nUse the `--evaluategate` command (alias `-g`) to request a gate decision for a DevOps Insights policy in your pipeline. If the policy is satisfied, the pipeline continues running. If not, and you use the `--forcedecision` flag, the pipeline stops running.\n\n### Command syntax and options\n\n```shell\nidra --evaluategate --policy= [--forcedecision] [--env=] [--type=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--policy`|`-P` | **Required.** The name of the policy that the gate uses to make its decision. |\n|`--forcedecision`|`-D` | _Optional._ This flag causes the process to exit with an error code if the policy evaluation fails. If you do not include it, the pipeline will run regardless of the gate's decision. |\n|`--type`|`-E` | _Optional_. A rule type to consider. If you include this option, only rules of this type are considered in the decision-making process. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, and `sonarqube` for SonarQube scans. |\n|`--env`|`-T` | _Optional._ The environment that is considered in the decision-making process. Test results that are not associated with this environment are excluded from the process. |\n\n\n\n## Release History\n_(Nothing yet)_\n","readmeFilename":"README.md","_id":"grunt-idra3@0.1.18","_shasum":"df85ccb2ca7945366a4f82a5a986894756aadf19","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.2","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"df85ccb2ca7945366a4f82a5a986894756aadf19","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.18.tgz","fileCount":19,"unpackedSize":201204,"integrity":"sha512-Wd0deGqVhxr5e3XPVIVpeNNbtMBKdh2rDrXUUdwdUYSLBklav825cGOqk4krmtxp4Y0lLVB0/foL5jGASCS6+w==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDYsH8TgjGEpDmo9+NAz005Y1KT6zIgMBu7yCHzasFPogIgfdyc2cXbvAFvvGqT8IAL/8VJgjXNoRPvQUmbWsIeizg="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.18_1523575028834_0.9841224482247499"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.19":{"name":"grunt-idra3","version":"0.1.19","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.2.5","sonar-scanner":"^1.0.1"},"dependencies":{"async":"2.1.4","command-line-args":"4.0.6","extend":"3.0.1","glob":"7.1.2","mime":"1.3.4","request":"2.83.0","url":"0.11.0","valid-url":"1.0.9","xml2js":"0.4.16"},"readme":"# idra\n\n> Command Line utility for integrating with IBM® DevOps Insights\n\nTo install this utility\n```\nnpm install -g grunt-idra3\n```\n\n## Getting Started\n\nUse this utility to integrate IBM® DevOps Insights with Travis CI, Concourse, IBM Urban Code Deploy, IBM Continuous Delivery Pipelines and other CI/CD tools. If you are using Jenkins, use this [Jenkins plugin](https://plugins.jenkins.io/ibm-cloud-devops) instead.\n\nUsing this utility, you can\n- publish build records, test records and deploy records to IBM® DevOps Insights \n- make go/no-go decisions about a build's quality by using a Gate policy \n\nFor samples of dashboards in IBM® DevOps Insights, see [Value Proposition](https://plugins.jenkins.io/ibm-cloud-devops).\n\nFor more information about IBM DevOps Insights, see [the official documentation](https://console.bluemix.net/docs/services/DevOpsInsights/index.html).\n\n### Scenarios\nThis document covers two scenarios:\n1. You are integrating DevOps Insights with IBM Continuous Delivery tool.\n2. You are integrating DevOps Insights with other CI/CD tools (e.g., Travis CI, Concourse, IBM Urban Code Deploy, others)\n\n### Prerequisites\n\nTo use the CLI, you need to do the following. These steps should take about 10 minutes.\n\n1. A valid IBM Cloud account. If you don't have one, [register here](https://console.bluemix.net/registration).\n\n2. Once you have an account, you can create an API Key. Log in to [IBM Cloud](https://console.bluemix.net). Click on **Manage**->**Security**->**Platform API Key**. On that screen, create an API Key.\n\n3. An IBM Continuous Delivery toolchain. To create a toolchain:\n- Go to https://console.bluemix.net/devops\n- Click on **Create a Toolchain** button and then select **Build Your Own Toolchain** template. \n- In the next screen, click **Create**.\n- From the URL displayed in the browser, make note of your toolchain id. For example, if your URL is https://console.bluemix.net/devops/toolchains/05572df3-01dc-441b-911d-b2202fe33f96, the toolchain id is the long string after **toolchains/**\n- You can always navigate to your toolchain by [clicking here](https://console.bluemix.net/devops)\n\n4. Add DevOps Insights tool to your toolchain\n- Go to your toolchain\n- Click on **Add a Tool** button\n- Select DevOps Insights tool and click **Create Integration** button\n\n5. Your CI/CD tool must have Node.js® 4.x or greater. \n\n### Environment Variables \n\nIf you are using Travis, Concourse or any CI/CD tool other than the IBM Continuous Delivery pipeline, then set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|ORGANIZATION_NAME| **Required.** The Bluemix organization's name|\n|TOOLCHAIN_ID| **Required.** The toolchain's GUID |\n|IBM_CLOUD_API_KEY| **Required.** The Bluemix user's Api key|\n|BUILD_NUMBER| **Required.** Any string that identifies the build |\n|LOGICAL_APP_NAME| **Required.** The application's name.|\n\n\n\nIf you are using IBM Continuous Delivery pipeline, you need to set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|BUILD_PREFIX| **Required.** Any string. For example, the Git branch name. |\n|LOGICAL_APP_NAME| **Required.** The application's name.|\n|PATH|**Required.** In order to have required version of Node.js in your path, set the PATH variable before invoking the utility: `export PATH=/opt/IBM/node-v4.2/bin:$PATH`|\n\nIf you are using IBM Continuous Delivery pipeline and if you want to publish Insights data to another toolchain, then set the following environment variables. \n\n|Name|Description|\n|-----|-----|\n|ORGANIZATION_NAME or ORGANIZATION_ID| **Required.** The target Bluemix organization's name or GUID. |\n|TOOLCHAIN_ID| **Required.** The target toolchain's GUID. The toolchain id provided here should be from the same environment pointed by the BLUEMIX_CONSOLE_URL (If BLUEMIX_CONSOLE_URL is not provided then it should be in USSouth Bluemix public ) |\n|IBM_CLOUD_API_KEY| _Optional._ If the target toolchain is owned by different user than that owner's Bluemix Api key|\n|BUILD_PREFIX| **Required.** Any string. For example, the Git branch name. |\n|LOGICAL_APP_NAME| **Required.** The application's name.|\n|PATH|**Required,** In order to have required version of Node.js in your path, set the PATH variable before invoking the utility: `export PATH=/opt/IBM/node-v4.2/bin:$PATH`|\n\n\n\nIf you are using IBM UrbanCode Deploy, DevOps Insights relies on the previous set of variables, and this one:\n\n|Name|Description|\n|-----|-----|\n|UCD_REQUEST_ID| This maps to the ${p:request.id} property value. |\n\n### Enabling Debug logs\nIf you want to enable debug logs for the DevOps Insights CLI, set the `IDRA_DEBUG` environment variable to `true`. This works in all environments.\n\n|Name|Description|\n|-----|-----|\n|IDRA_DEBUG| When this value is `true`, the DevOps Insights CLI's debugging mode is enabled. By default, the value is `false`. |\n\n\n### Using the CLI\n\nSet [environment details](#environment-details) as described above. Ensure that Node.js 4.2 or higher is avaialble in your CI/CD tool.\n\nTo install this utility, use `npm install -g grunt-idra3`\n\nThen you can invoke the CLI with the `idra` command. You can run the CLI in any pipeline job's command script. For example, this command uploads functional verification test results to DevOps Insights:\n\n```\n# Upload test results\nidra --publishtestresult --filelocation=\"results.json\" --type=fvt\n```\n\n\n## Uploading Build Records\nUse the `--publishbuildrecord` command (alias `-b`) to upload build records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishbuildrecord --branch= --repositoryurl= --commitid= --status= [--joburl=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--branch`|`-B` | **Required.** The repository branch on which the build is being performed. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--repositoryurl`|`-R` | **Required.** The url of the git repository. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--commitid`|`-C` | **Required.** The git commit id. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--status`|`-S` | **Required.** The build status. This value must be either `pass` or `fail`. |\n|`--joburl`|`-J` | _Optional_. The URL to the job's build logs. |\n\n\n### An example command\n\nIn this an example, the command uploads a build record from a pipeline job.\n\n```shell\nidra --publishbuildrecord --branch=master --repositoryurl=\"https://github.com/oic/dlms.git\" --commitid=dff7884b9168168d91cb9e5aec78e93db0fa80d9 --status=pass\n```\n\n## Uploading Test Results\n\nUse the `--publishtestresult` command (alias `-p`) to upload results from these test types to DevOps Insights:\n\n* Unit tests\n* Code coverage tests\n* Functional verification tests (FVT)\n* Static security scans from IBM Application Security on Cloud\n* Dynamic app scans from IBM Application Security on Cloud\n* [SonarQube results](#uploading-sonarqube-results)\n\n\n### Command syntax and options\n\n```shell\nidra --publishtestresult --filelocation= --type= [--tool=] [--drilldownurl=] [--env=] [--token=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--filelocation`| `-F` |**Required.** The location of the test results that you want to upload. This can be a single file, an entire directory, or multiple files that match a wildcard expression.|\n|`--type`| `-T` |**Required.** The type of test results that you want to upload. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, and `sonarqube` for SonarQube scans. In addition to these types you can also use a custom quality data set tag to upload test results of different type.|\n|`--tool`| `-L` |_Optional_. The name for the test tool. |\n|`--drilldownurl`| `-U` |_Optional._ A URL where more information about the test results can be found. If this URL is invalid, the option is ignored. |\n|`--env`| `-E` |_Optional._ The environment name to associate with the test results. This option is ignored for unit tests, code coverage tests, and static security scans. |\n|`--token`| `-K` |_Optional_. This is a SonarQube token. This flag is valid only if the type specified is `sonarqube`. It is used by the CLI to pull additional information from the SonarQube server. |\n\n### An example command\n\nIn this example, the command uploads all JSON-formatted FVT results from a directory to DevOps Insights. Additionally, a test tool is declared, a test result URL is given, and a logical staging environment is provided. Specifying an environment is especially important when you want your results to be analyzed alongside other activities that take place in that same environment.\n\n```shell\nidra --publishtestresult --filelocation=\"tests/fvt/*.json\" --type=fvt --tool=\"your-test-runner\" -drilldownurl=\"https://example.com/testinfo\" --env=\"staging\"\n```\n\n## Uploading SonarQube Results\nTo upload data from SonarQube, you must provide the SonarQube server token using ```--token```. Your SonarQube server is not required to be accessible from IBM Cloud.\n\nAfter you run a scan using SonarQube, you can upload SonarQube results by running this command.\n\n```idra --publishtestresult --filelocation=.scannerwork/report-task.txt --type=sonarqube --token=234234434```\n\nIn the above command, report-task.txt is a file generated during the SonarQube scan.\n\nIf this command fails for some reason, you can enable logs by setting IDRA_DEBUG environment variable to true.\n\nIf you are using self-signed certificates for SonarQube server, you will need to set ```export NODE_TLS_REJECT_UNAUTHORIZED=0```\n\n\n## Uploading Vulnerability Scan Results\n\nUse the `--publishvulnerabilityresult` command (alias `-v`) to upload [vulnerability advisor](https://console.bluemix.net/docs/containers/va/va_index.html) results to DevOps Insights:\n\n### Command syntax and options\n\n```shell\nidra --publishvulnerabilityresult --image= --account=\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--image`| `-M` |**Required.** Name of image including the repository and the tag.|\n|`--account`| `-O` |**Required.** The unique ID for your IBM Cloud account. Run 'bx cr info' to get the ID of the target account. |\n\n### An example command\n\nIn this example, the command uploads the vulnerability scan details of the image specified, to DevOps Insights. It gets the details by querying the relevant image repository.\n\n```shell\nidra --publishvulnerabilityresult --image=\"registry.ng.bluemix.net/auser/hello-containers-auser-1129:1\" --account=65fc31e13b143434540bcb495\n```\n## Uploading Deployment Records\nUse the `--publishdeployrecord` command (alias `-d`) to upload deployment records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishdeployrecord --env= --status= [--joburl=] [--appurl=] [--deployableid=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--env`|`-E` | **Required.** The environment where the pipeline job deployed the app. |\n|`--status`|`-S` | **Required.** The deployment status. This value must be either `pass` or `fail`. |\n|`--joburl`|`-J` | _Optional_. The URL to the job's deployment logs. |\n|`--appurl`|`-A` | _Optional._ The URL where the deployed app is running. |\n|`--deployableid`| `-I` | _Optional._ The deployed app's application ID. You can get the ID by running the Cloud Foundry CLI's `cf env` command. The application ID is listed under `VCAP_APPLICATION`. |\n\n### An example command\n\nIn this an example, the command uploads a deployment record from a pipeline job. The deployment is to the \"staging\" environment. The deployment is successful and the app is running at a specified URL.\n\n```shell\nidra --publishdeployrecord --env=\"staging\" --status=pass --appurl=\"https://app.staging.example.com\"\n```\n\n## Making Decisions about Build Quality using Gate Policies\n\nTo use this feature, create a quality policy by using the user interface. Navigate to your toolchain, click on **DevOps Insights** card. Then on the left menu, click on **Deployment Risk**->**Policies**. \n\nUse the `--evaluategate` command (alias `-g`) to request a gate decision for a DevOps Insights policy in your pipeline. If the policy is satisfied, the pipeline continues running. If not, and you use the `--forcedecision` flag, the pipeline stops running.\n\n### Command syntax and options\n\n```shell\nidra --evaluategate --policy= [--forcedecision] [--env=] [--type=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--policy`|`-P` | **Required.** The name of the policy that the gate uses to make its decision. |\n|`--forcedecision`|`-D` | _Optional._ This flag causes the process to exit with an error code if the policy evaluation fails. If you do not include it, the pipeline will run regardless of the gate's decision. |\n|`--type`|`-E` | _Optional_. A rule type to consider. If you include this option, only rules of this type are considered in the decision-making process. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, and `sonarqube` for SonarQube scans. |\n|`--env`|`-T` | _Optional._ The environment that is considered in the decision-making process. Test results that are not associated with this environment are excluded from the process. |\n\n\n\n## Release History\n_(Nothing yet)_\n","readmeFilename":"README.md","_id":"grunt-idra3@0.1.19","_shasum":"f4b82e7d3285bfc3c49c608fc9451b8c87fca92e","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.2","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"f4b82e7d3285bfc3c49c608fc9451b8c87fca92e","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.19.tgz","fileCount":19,"unpackedSize":201659,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJa17GyCRA9TVsSAnZWagAAuXwP/1cOERfQxHtDo2jUogpK\n7pipGPkpfPVdyqhHODc65pVE2UF3sLfx3S8PsA7b3zubacu/n6DFLoN6MOtM\nEzhsVkHMWq9zrWo+Iu4CZ01mlAK7jfkJRaXqYoZKl2GwSmi+43pOZZJdp2gT\nzV5AJ7DLTb3FduIuGxCTEZVRxmkK62tlJQNhE6bDrVn/eGU0BpEHNB8VUYjN\nOz63c7tZvdopQx5U2SCcf0Se7AMf3J4fqpjglKozdWaj9vHYavhu7Oup7k3+\ngYT2VcEox+IkjbyLz8MIgKMYDPjISS8N5xoEpQDpnQRkzGqGwmPOKds/B+5B\n0LpkGNwmDFtW57oo9ovf0ZS01R+yxBNDswbGhtaRYgIJckh6IWaHl2B2DWnj\nX0NedCMbzICI06B5OVr1ZdDRB3ofbgMokHMaLzZggj1f0+BK67mAu4U3pzaQ\nQSBnqTKvIMf1WhvMJqG92KPZMwWSJ9SUqJc8cro9mifWoJXpz9PfVYNBq2zH\n3NPv12TDNPXqbzsXvBM+D+x+L6ktNCmDvF1hymkLKA2uYuw25tbZDapmfGhC\napGL71C19lizdKK3Nu70rxSwQ2XgLryEldpfuQMVYJy4yg+z9oiir5Vp849R\n4uCou06WLbPuUSi6ec+dvYGXqXtKFZ2hJdCJ6JSI4f+9MHnBU+1/Ua9X3zt7\ntr26\r\n=kf7s\r\n-----END PGP SIGNATURE-----\r\n","integrity":"sha512-DxlJzGbdQ9m49+L0Y1zsLvZIcBDkUXN5rv2vg9vRZBCz4B7F/vnoCtRXg4AXb7WAkCb2+yWeo12iFPUHyqxLww==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIFc1mvYw02p1m0lXKED5fx3ESLKfF2HHSrRDXON2a3keAiBb6shbFEq/IPo6kecXvEv7gtfafHTyaZTcHoXPV04LPQ=="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.19_1524085169452_0.8512875046472197"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.20":{"name":"grunt-idra3","version":"0.1.20","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.2.5","sonar-scanner":"^1.0.1"},"dependencies":{"async":"2.1.4","command-line-args":"4.0.6","extend":"3.0.1","glob":"7.1.2","inquirer":"^3.0.0","mime":"1.3.4","request":"2.83.0","url":"0.11.0","valid-url":"1.0.9","xml2js":"0.4.16"},"readme":"# idra\n\n> Command Line utility for integrating with IBM® DevOps Insights\n\nTo install this utility\n```\nnpm install -g grunt-idra3\n```\n\n# Table of Contents\n1. [Getting Started](#getting-started)\n2. [Scenarios](#scenarios)\n 1. [Prerequisites](#prerequisites)\n 2. [Environment Variables](#environment-variables)\n 3. [Enabling Debug Logs](#enabling-debug-logs)\n 4. [Using the CLI](#using-the-cli)\n3. [Upload Build Records](#upload-build-records)\n4. [Upload Test Results](#upload-test-results)\n5. [Upload SonarQube Results](#upload-sonarqube-results)\n6. [Upload Vulnerability Scan Results](#upload-vulnerability-scan-results)\n7. [Upload Deployment Records](#upload-deployment-records)\n8. [Making decisions about Build Quality using Gate Policies](#making-decisions-about-build-quality-using-gate-policies)\n\n\n## Getting Started\n\nUse this utility to integrate IBM® DevOps Insights with Travis CI, Concourse, IBM Urban Code Deploy, IBM Continuous Delivery Pipelines and other CI/CD tools. If you are using Jenkins, use this [Jenkins plugin](https://plugins.jenkins.io/ibm-cloud-devops) instead.\n\nUsing this utility, you can\n- publish build records, test records and deploy records to IBM® DevOps Insights \n- make go/no-go decisions about a build's quality by using a Gate policy\n\nFor samples of dashboards in IBM® DevOps Insights, see [Value Proposition](https://plugins.jenkins.io/ibm-cloud-devops).\n\nFor more information about IBM DevOps Insights, see [the official documentation](https://console.bluemix.net/docs/services/DevOpsInsights/index.html).\n\n### Scenarios\nThis document covers two scenarios:\n1. You are integrating DevOps Insights with IBM Continuous Delivery tool.\n2. You are integrating DevOps Insights with other CI/CD tools (e.g., Travis CI, Concourse, IBM Urban Code Deploy, others)\n\n### Prerequisites\n\nTo use the CLI, you need to do the following. These steps should take about 10 minutes.\n\n1. A valid IBM Cloud account. If you don't have one, [register here](https://console.bluemix.net/registration).\n\n2. Once you have an account, you can create an API Key. Log in to [IBM Cloud](https://console.bluemix.net). Click on **Manage**->**Security**->**Platform API Key**. On that screen, create an API Key.\n\n3. An IBM Continuous Delivery toolchain. To create a toolchain:\n- Go to https://console.bluemix.net/devops\n- Click on **Create a Toolchain** button and then select **Build Your Own Toolchain** template. \n- In the next screen, click **Create**.\n- From the URL displayed in the browser, make note of your toolchain id. For example, if your URL is https://console.bluemix.net/devops/toolchains/05572df3-01dc-441b-911d-b2202fe33f96, the toolchain id is the long string after **toolchains/**\n- You can always navigate to your toolchain by [clicking here](https://console.bluemix.net/devops)\n\n4. Add DevOps Insights tool to your toolchain\n- Go to your toolchain\n- Click on **Add a Tool** button\n- Select DevOps Insights tool and click **Create Integration** button\n\n5. Your CI/CD tool must have Node.js® 4.x or greater.\n\n### Environment Variables \n\nIf you are using Travis, Concourse or any CI/CD tool other than the IBM Continuous Delivery pipeline, then set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|ORGANIZATION_NAME| **Required.** The Bluemix organization's name|\n|TOOLCHAIN_ID| **Required.** The toolchain's GUID |\n|IBM_CLOUD_API_KEY| **Required.** The Bluemix user's Api key|\n|BUILD_NUMBER| **Required.** Any string that identifies the build |\n|LOGICAL_APP_NAME| **Required.** The application's name.|\n\n\n\nIf you are using IBM Continuous Delivery pipeline, you need to set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|BUILD_PREFIX| **Required.** Any string. For example, the Git branch name. |\n|LOGICAL_APP_NAME| **Required.** The application's name.|\n|PATH|**Required.** In order to have required version of Node.js in your path, set the PATH variable before invoking the utility: `export PATH=/opt/IBM/node-v4.2/bin:$PATH`|\n\nIf you are using IBM Continuous Delivery pipeline and if you want to publish Insights data to another toolchain, then set the following environment variables. \n\n|Name|Description|\n|-----|-----|\n|ORGANIZATION_NAME or ORGANIZATION_ID| **Required.** The target Bluemix organization's name or GUID. |\n|TOOLCHAIN_ID| **Required.** The target toolchain's GUID. The toolchain id provided here should be from the same environment pointed by the BLUEMIX_CONSOLE_URL (If BLUEMIX_CONSOLE_URL is not provided then it should be in USSouth Bluemix public ) |\n|IBM_CLOUD_API_KEY| _Optional._ If the target toolchain is owned by different user than that owner's Bluemix Api key|\n|BUILD_PREFIX| **Required.** Any string. For example, the Git branch name. |\n|LOGICAL_APP_NAME| **Required.** The application's name.|\n|PATH|**Required,** In order to have required version of Node.js in your path, set the PATH variable before invoking the utility: `export PATH=/opt/IBM/node-v4.2/bin:$PATH`|\n\n\n\nIf you are using IBM UrbanCode Deploy, DevOps Insights relies on the previous set of variables, and this one:\n\n|Name|Description|\n|-----|-----|\n|UCD_REQUEST_ID| This maps to the ${p:request.id} property value. |\n\n### Enabling Debug logs\nIf you want to enable debug logs for the DevOps Insights CLI, set the `IDRA_DEBUG` environment variable to `true`. This works in all environments.\n\n|Name|Description|\n|-----|-----|\n|IDRA_DEBUG| When this value is `true`, the DevOps Insights CLI's debugging mode is enabled. By default, the value is `false`. |\n\n\n### Using the CLI\n\nSet [environment details](#environment-details) as described above. Ensure that Node.js 4.2 or higher is avaialble in your CI/CD tool.\n\nTo install this utility, use `npm install -g grunt-idra3`\n\nThen you can invoke the CLI with the `idra` command. You can run the CLI in any pipeline job's command script. For example, this command uploads functional verification test results to DevOps Insights:\n\n```\n# Upload test results\nidra --publishtestresult --filelocation=\"results.json\" --type=fvt\n```\n\n\n## Upload Build Records\nUse the `--publishbuildrecord` command (alias `-b`) to upload build records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishbuildrecord --branch= --repositoryurl= --commitid= --status= [--joburl=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--branch`|`-B` | **Required.** The repository branch on which the build is being performed. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--repositoryurl`|`-R` | **Required.** The url of the git repository. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--commitid`|`-C` | **Required.** The git commit id. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--status`|`-S` | **Required.** The build status. This value must be either `pass` or `fail`. |\n|`--joburl`|`-J` | _Optional_. The URL to the job's build logs. |\n\n\n### An example command\n\nIn this an example, the command uploads a build record from a pipeline job.\n\n```shell\nidra --publishbuildrecord --branch=master --repositoryurl=\"https://github.com/oic/dlms.git\" --commitid=dff7884b9168168d91cb9e5aec78e93db0fa80d9 --status=pass\n```\n\n## Upload Test Results\n\nUse the `--publishtestresult` command (alias `-p`) to upload results from these test types to DevOps Insights:\n\n* Unit tests\n* Code coverage tests\n* Functional verification tests (FVT)\n* Static security scans from IBM Application Security on Cloud\n* Dynamic app scans from IBM Application Security on Cloud\n* [SonarQube results](#uploading-sonarqube-results)\n\n\n### Command syntax and options\n\n```shell\nidra --publishtestresult --filelocation= --type= [--tool=] [--drilldownurl=] [--env=] [--token=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--filelocation`| `-F` |**Required.** The location of the test results that you want to upload. This can be a single file, an entire directory, or multiple files that match a wildcard expression.|\n|`--type`| `-T` |**Required.** The type of test results that you want to upload. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, and `sonarqube` for SonarQube scans. In addition to these types you can also use a custom quality data set tag to upload test results of different type.|\n|`--tool`| `-L` |_Optional_. The name for the test tool. |\n|`--drilldownurl`| `-U` |_Optional._ A URL where more information about the test results can be found. If this URL is invalid, the option is ignored. |\n|`--env`| `-E` |_Optional._ The environment name to associate with the test results. This option is ignored for unit tests, code coverage tests, and static security scans. |\n|`--token`| `-K` |_Optional_. This is a SonarQube token. This flag is valid only if the type specified is `sonarqube`. It is used by the CLI to pull additional information from the SonarQube server. |\n\n### An example command\n\nIn this example, the command uploads all JSON-formatted FVT results from a directory to DevOps Insights. Additionally, a test tool is declared, a test result URL is given, and a logical staging environment is provided. Specifying an environment is especially important when you want your results to be analyzed alongside other activities that take place in that same environment.\n\n```shell\nidra --publishtestresult --filelocation=\"tests/fvt/*.json\" --type=fvt --tool=\"your-test-runner\" -drilldownurl=\"https://example.com/testinfo\" --env=\"staging\"\n```\n\n### Supported Test Formats\n|Type of Test|tag|Supported Formats|\n|-----|-----|-----|\n|Unit Test|`unittest`|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Test Case|`fvt`|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Code Coverage|`code`|Cobertura (xml), lcov, Istanbul, JaCoCo|\n|SonarQube|`sonarqube`|SonarQube|\n|Static Security Scan|`staticsecurityscan`|IBM Application Security|\n|Dynamic Security Scan|`dynamicsecurityscan`|IBM Application Security|\n|Vulnerability Advisor|`vulnerabilityadvisor`|Vulnerability Advisor|\n\nFor golang [gocov](https://github.com/axw/gocov/) users, please convert to Cobertura using [gocov XML(Cobertura) export](https://github.com/yaoyaozong/gocov-xml)\n\n## Upload SonarQube Results\nTo upload data from SonarQube, you must provide the SonarQube server token using ```--token```. Your SonarQube server is not required to be accessible from your CI/CD tool.\n\nAfter you run a scan using SonarQube, you can upload SonarQube results by running this command.\n\n```idra --publishtestresult --filelocation=.scannerwork/report-task.txt --type=sonarqube --token=234234434```\n\nIn the above command, report-task.txt is a file generated during the SonarQube scan.\n\nIf this command fails for some reason, you can enable logs by setting IDRA_DEBUG environment variable to true.\n\nIf you are using self-signed certificates for SonarQube server, you will need to set ```export NODE_TLS_REJECT_UNAUTHORIZED=0```\n\n\n## Uploading Vulnerability Scan Results\n\nUse the `--publishvulnerabilityresult` command (alias `-v`) to upload [vulnerability advisor](https://console.bluemix.net/docs/containers/va/va_index.html) results to DevOps Insights:\n\n### Command syntax and options\n\n```shell\nidra --publishvulnerabilityresult --image= --account=\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--image`| `-M` |**Required.** Name of image including the repository and the tag.|\n|`--account`| `-O` |**Required.** The unique ID for your IBM Cloud account. Run 'bx cr info' to get the ID of the target account. |\n\n### An example command\n\nIn this example, the command uploads the vulnerability scan details of the image specified, to DevOps Insights. It gets the details by querying the relevant image repository.\n\n```shell\nidra --publishvulnerabilityresult --image=\"registry.ng.bluemix.net/auser/hello-containers-auser-1129:1\" --account=65fc31e13b143434540bcb495\n```\n## Upload Deployment Records\nUse the `--publishdeployrecord` command (alias `-d`) to upload deployment records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishdeployrecord --env= --status= [--joburl=] [--appurl=] [--deployableid=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--env`|`-E` | **Required.** The environment where the pipeline job deployed the app. |\n|`--status`|`-S` | **Required.** The deployment status. This value must be either `pass` or `fail`. |\n|`--joburl`|`-J` | _Optional_. The URL to the job's deployment logs. |\n|`--appurl`|`-A` | _Optional._ The URL where the deployed app is running. |\n|`--deployableid`| `-I` | _Optional._ The deployed app's application ID. You can get the ID by running the Cloud Foundry CLI's `cf env` command. The application ID is listed under `VCAP_APPLICATION`. |\n\n### An example command\n\nIn this an example, the command uploads a deployment record from a pipeline job. The deployment is to the \"staging\" environment. The deployment is successful and the app is running at a specified URL.\n\n```shell\nidra --publishdeployrecord --env=\"staging\" --status=pass --appurl=\"https://app.staging.example.com\"\n```\n\n## Making Decisions about Build Quality using Gate Policies\n\nTo use this feature, create a quality policy by using the user interface. Navigate to your toolchain, click on **DevOps Insights** card. Then on the left menu, click on **Deployment Risk**->**Policies**.\n\nUse the `--evaluategate` command (alias `-g`) to request a gate decision for a DevOps Insights policy in your pipeline. If the policy is satisfied, the pipeline continues running. If not, and you use the `--forcedecision` flag, the pipeline stops running.\n\n### Command syntax and options\n\n```shell\nidra --evaluategate --policy= [--forcedecision] [--env=] [--type=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--policy`|`-P` | **Required.** The name of the policy that the gate uses to make its decision. |\n|`--forcedecision`|`-D` | _Optional._ This flag causes the process to exit with an error code if the policy evaluation fails. If you do not include it, the pipeline will run regardless of the gate's decision. |\n|`--type`|`-E` | _Optional_. A rule type to consider. If you include this option, only rules of this type are considered in the decision-making process. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, and `sonarqube` for SonarQube scans. |\n|`--env`|`-T` | _Optional._ The environment that is considered in the decision-making process. Test results that are not associated with this environment are excluded from the process. |\n\n\n\n## Release History\n_(Nothing yet)_\n","readmeFilename":"README.md","_id":"grunt-idra3@0.1.20","_shasum":"b69f2a1166e5b5b8ed0ccaeb81b0579ca0ca1866","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.2","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"b69f2a1166e5b5b8ed0ccaeb81b0579ca0ca1866","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.20.tgz","fileCount":54,"unpackedSize":256119,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJa61xXCRA9TVsSAnZWagAAOK4QAJUfG/7L265Zd59uzjKa\n9nJRRqKnUYqMf4TpMIXsU1RH62oqisvIv0ctTSXl7EQam4MgmdRbmFW4Ewop\n+VYKkLpnj1c2GU+3WaZf0l08hWnHaBykhS/EqByZ9iL5gDEMQeL6qlU3iEqL\no07icOunnov36svbecIBan83+54ywemsVyp+7jKFbPtfdzHAVKnJrv3vFzzU\ntFFwhkbOjJJzjnSpU8AaNNytK5+J4ogx3/OnIzu+7uuWtQckFOr76uJpCOXg\nJYRcnqGhzbaiqgzWJjpyaZY4ZXslm5veucGNiaJ/Z924DcYeo68OdNFeH7vO\nTrGhEYcD7Upi7/W6lvICr48bhXZ6tBDdJIWGDhxh/4OWqV8/VS4ugMPWC8Du\nSCBdOfgiDg2Ycbbld20HwqFbK/P5ZjfMNCyetHsnWc2wq1rBtlEx9u7UVTUK\nnnLjAbWxrsORHo1yWsyzd/Cvt0GyJQiGC+lY9thKK499dD71s+oDWq9XUqfK\ncekM7NguYvSm5uo5hs9wcf22Llyo+pHxV9xhlZ09Xd+QX633r7AMzLMfF5hD\n0pxJ3cFK8oAFoZgidCpffepZcM0e6CH6FtyMiAwpvtyoXbuZJCatzzYrvGiL\nSFzAp+5wUj1NLdgEFVMz/GpwQGD0DXvSjjxlLrpfEPdawxgVXMg55t4vUI/b\n9JO7\r\n=j3P+\r\n-----END PGP SIGNATURE-----\r\n","integrity":"sha512-Wk66A4Oe1r+dq9mOzmzbCUJ2Sw3kOZI5u+Y5oJ/3QdJy2BJY3ame6DUjsE/H77IrCuMABJQox8hXnP4zLKWsIA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDI/TzNlY1mDM8PonxYC3HhEVOZSpY/BjlIzlHKZJxvowIgc865N4ARuq//0U3ShxjJmcZ1ePtulVzpKp82ikwnN8Y="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.20_1525374038985_0.8875659596819534"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.21":{"name":"grunt-idra3","version":"0.1.21","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.2.5","sonar-scanner":"^1.0.1"},"dependencies":{"async":"2.1.4","command-line-args":"4.0.6","extend":"3.0.1","glob":"7.1.2","inquirer":"^3.0.0","mime":"1.3.4","request":"2.83.0","url":"0.11.0","valid-url":"1.0.9","xml2js":"0.4.16"},"readme":"# idra\n\n> Command Line utility for integrating with IBM® DevOps Insights\n\nTo install this utility\n```\nnpm install -g grunt-idra3\n```\n\n# Table of Contents\n1. [Getting Started](#getting-started)\n2. [Scenarios](#scenarios)\n 1. [Prerequisites](#prerequisites)\n 2. [Environment Variables](#environment-variables)\n 3. [Enabling Debug Logs](#enabling-debug-logs)\n 4. [Using the CLI](#using-the-cli)\n3. [Upload Build Records](#upload-build-records)\n4. [Upload Test Results](#upload-test-results)\n5. [Upload SonarQube Results](#upload-sonarqube-results)\n6. [Upload Vulnerability Scan Results](#upload-vulnerability-scan-results)\n7. [Upload Deployment Records](#upload-deployment-records)\n8. [Making decisions about Build Quality using Gate Policies](#making-decisions-about-build-quality-using-gate-policies)\n\n\n## Getting Started\n\nUse this utility to integrate IBM® DevOps Insights with Travis CI, Concourse, IBM Urban Code Deploy, IBM Continuous Delivery Pipelines and other CI/CD tools. If you are using Jenkins, use this [Jenkins plugin](https://plugins.jenkins.io/ibm-cloud-devops) instead.\n\nUsing this utility, you can\n- publish build records, test records and deploy records to IBM® DevOps Insights \n- make go/no-go decisions about a build's quality by using a Gate policy\n\nFor samples of dashboards in IBM® DevOps Insights, see [Value Proposition](https://plugins.jenkins.io/ibm-cloud-devops).\n\nFor more information about IBM DevOps Insights, see [the official documentation](https://console.bluemix.net/docs/services/DevOpsInsights/index.html).\n\n### Scenarios\nThis document covers two scenarios:\n1. You are integrating DevOps Insights with IBM Continuous Delivery tool.\n2. You are integrating DevOps Insights with other CI/CD tools (e.g., Travis CI, Concourse, IBM Urban Code Deploy, others)\n\n### Prerequisites\n\nTo use the CLI, you need to do the following. These steps should take about 10 minutes.\n\n1. A valid IBM Cloud account. If you don't have one, [register here](https://console.bluemix.net/registration).\n\n2. Once you have an account, you can create an API Key. Log in to [IBM Cloud](https://console.bluemix.net). Click on **Manage**->**Security**->**Platform API Key**. On that screen, create an API Key.\n\n3. An IBM Continuous Delivery toolchain. To create a toolchain:\n- Go to https://console.bluemix.net/devops\n- Click on **Create a Toolchain** button and then select **Build Your Own Toolchain** template. \n- In the next screen, click **Create**.\n- From the URL displayed in the browser, make note of your toolchain id. For example, if your URL is https://console.bluemix.net/devops/toolchains/05572df3-01dc-441b-911d-b2202fe33f96, the toolchain id is the long string after **toolchains/**\n- You can always navigate to your toolchain by [clicking here](https://console.bluemix.net/devops)\n\n4. Add DevOps Insights tool to your toolchain\n- Go to your toolchain\n- Click on **Add a Tool** button\n- Select DevOps Insights tool and click **Create Integration** button\n\n5. Your CI/CD tool must have Node.js® 4.x or greater.\n\n### Environment Variables \n\nIf you are using Travis, Concourse or any CI/CD tool other than the IBM Continuous Delivery pipeline, then set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|TOOLCHAIN_ID| **Required.** The toolchain's GUID |\n|IBM_CLOUD_API_KEY| **Required.** The Bluemix user's Api key|\n|BUILD_NUMBER| **Required.** Any string that identifies the build |\n|LOGICAL_APP_NAME| **Required.** The application's name.|\n\n\n\nIf you are using IBM Continuous Delivery pipeline, you need to set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|BUILD_PREFIX| **Required.** Any string. For example, the Git branch name. |\n|LOGICAL_APP_NAME| **Required.** The application's name.|\n|PATH|**Required.** In order to have required version of Node.js in your path, set the PATH variable before invoking the utility: `export PATH=/opt/IBM/node-v4.2/bin:$PATH`|\n\nIf you are using IBM Continuous Delivery pipeline and if you want to publish Insights data to another toolchain, then set the following environment variables. \n\n|Name|Description|\n|-----|-----|\n|TOOLCHAIN_ID| **Required.** The target toolchain's GUID. The toolchain id provided here should be from the same environment pointed by the BLUEMIX_CONSOLE_URL (If BLUEMIX_CONSOLE_URL is not provided then it should be in USSouth Bluemix public ) |\n|IBM_CLOUD_API_KEY| _Optional._ If the target toolchain is owned by different user than that owner's Bluemix Api key|\n|BUILD_PREFIX| **Required.** Any string. For example, the Git branch name. |\n|LOGICAL_APP_NAME| **Required.** The application's name.|\n|PATH|**Required,** In order to have required version of Node.js in your path, set the PATH variable before invoking the utility: `export PATH=/opt/IBM/node-v4.2/bin:$PATH`|\n\n\n\nIf you are using IBM UrbanCode Deploy, DevOps Insights relies on the previous set of variables, and this one:\n\n|Name|Description|\n|-----|-----|\n|UCD_REQUEST_ID| This maps to the ${p:request.id} property value. |\n\n### Enabling Debug logs\nIf you want to enable debug logs for the DevOps Insights CLI, set the `IDRA_DEBUG` environment variable to `true`. This works in all environments.\n\n|Name|Description|\n|-----|-----|\n|IDRA_DEBUG| When this value is `true`, the DevOps Insights CLI's debugging mode is enabled. By default, the value is `false`. |\n\n\n### Using the CLI\n\nSet [environment details](#environment-details) as described above. Ensure that Node.js 4.2 or higher is avaialble in your CI/CD tool.\n\nTo install this utility, use `npm install -g grunt-idra3`\n\nThen you can invoke the CLI with the `idra` command. You can run the CLI in any pipeline job's command script. For example, this command uploads functional verification test results to DevOps Insights:\n\n```\n# Upload test results\nidra --publishtestresult --filelocation=\"results.json\" --type=fvt\n```\n\n\n## Upload Build Records\nUse the `--publishbuildrecord` command (alias `-b`) to upload build records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishbuildrecord --branch= --repositoryurl= --commitid= --status= [--joburl=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--branch`|`-B` | **Required.** The repository branch on which the build is being performed. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--repositoryurl`|`-R` | **Required.** The url of the git repository. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--commitid`|`-C` | **Required.** The git commit id. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--status`|`-S` | **Required.** The build status. This value must be either `pass` or `fail`. |\n|`--joburl`|`-J` | _Optional_. The URL to the job's build logs. |\n\n\n### An example command\n\nIn this an example, the command uploads a build record from a pipeline job.\n\n```shell\nidra --publishbuildrecord --branch=master --repositoryurl=\"https://github.com/oic/dlms.git\" --commitid=dff7884b9168168d91cb9e5aec78e93db0fa80d9 --status=pass\n```\n\n## Upload Test Results\n\nUse the `--publishtestresult` command (alias `-p`) to upload results from these test types to DevOps Insights:\n\n* Unit tests\n* Code coverage tests\n* Functional verification tests (FVT)\n* Static security scans from IBM Application Security on Cloud\n* Dynamic app scans from IBM Application Security on Cloud\n* [SonarQube results](#uploading-sonarqube-results)\n\n\n### Command syntax and options\n\n```shell\nidra --publishtestresult --filelocation= --type= [--tool=] [--drilldownurl=] [--env=] [--token=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--filelocation`| `-F` |**Required.** The location of the test results that you want to upload. This can be a single file, an entire directory, or multiple files that match a wildcard expression.|\n|`--type`| `-T` |**Required.** The type of test results that you want to upload. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, and `sonarqube` for SonarQube scans. In addition to these types you can also use a custom quality data set tag to upload test results of different type.|\n|`--tool`| `-L` |_Optional_. The name for the test tool. |\n|`--drilldownurl`| `-U` |_Optional._ A URL where more information about the test results can be found. If this URL is invalid, the option is ignored. |\n|`--env`| `-E` |_Optional._ The environment name to associate with the test results. This option is ignored for unit tests, code coverage tests, and static security scans. |\n|`--token`| `-K` |_Optional_. This is a SonarQube token. This flag is valid only if the type specified is `sonarqube`. It is used by the CLI to pull additional information from the SonarQube server. |\n\n### An example command\n\nIn this example, the command uploads all JSON-formatted FVT results from a directory to DevOps Insights. Additionally, a test tool is declared, a test result URL is given, and a logical staging environment is provided. Specifying an environment is especially important when you want your results to be analyzed alongside other activities that take place in that same environment.\n\n```shell\nidra --publishtestresult --filelocation=\"tests/fvt/*.json\" --type=fvt --tool=\"your-test-runner\" -drilldownurl=\"https://example.com/testinfo\" --env=\"staging\"\n```\n\n### Supported Test Formats\n|Type of Test|tag|Supported Formats|\n|-----|-----|-----|\n|Unit Test|`unittest`|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Test Case|`fvt`|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Code Coverage|`code`|Cobertura (xml), lcov, Istanbul, JaCoCo|\n|SonarQube|`sonarqube`|SonarQube|\n|Static Security Scan|`staticsecurityscan`|IBM Application Security|\n|Dynamic Security Scan|`dynamicsecurityscan`|IBM Application Security|\n|Vulnerability Advisor|`vulnerabilityadvisor`|Vulnerability Advisor|\n\nFor golang [gocov](https://github.com/axw/gocov/) users, please convert to Cobertura using [gocov XML(Cobertura) export](https://github.com/yaoyaozong/gocov-xml)\n\n## Upload SonarQube Results\nTo upload data from SonarQube, you must provide the SonarQube server token using ```--token```. Your SonarQube server is not required to be accessible from your CI/CD tool.\n\nAfter you run a scan using SonarQube, you can upload SonarQube results by running this command.\n\n```idra --publishtestresult --filelocation=.scannerwork/report-task.txt --type=sonarqube --token=234234434```\n\nIn the above command, report-task.txt is a file generated during the SonarQube scan.\n\nIf this command fails for some reason, you can enable logs by setting IDRA_DEBUG environment variable to true.\n\nIf you are using self-signed certificates for SonarQube server, you will need to set ```export NODE_TLS_REJECT_UNAUTHORIZED=0```\n\n\n## Uploading Vulnerability Scan Results\n\nUse the `--publishvulnerabilityresult` command (alias `-v`) to upload [vulnerability advisor](https://console.bluemix.net/docs/containers/va/va_index.html) results to DevOps Insights:\n\n### Command syntax and options\n\n```shell\nidra --publishvulnerabilityresult --image= --account=\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--image`| `-M` |**Required.** Name of image including the repository and the tag.|\n|`--account`| `-O` |**Required.** The unique ID for your IBM Cloud account. Run 'bx cr info' to get the ID of the target account. |\n\n### An example command\n\nIn this example, the command uploads the vulnerability scan details of the image specified, to DevOps Insights. It gets the details by querying the relevant image repository.\n\n```shell\nidra --publishvulnerabilityresult --image=\"registry.ng.bluemix.net/auser/hello-containers-auser-1129:1\" --account=65fc31e13b143434540bcb495\n```\n## Upload Deployment Records\nUse the `--publishdeployrecord` command (alias `-d`) to upload deployment records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishdeployrecord --env= --status= [--joburl=] [--appurl=] [--deployableid=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--env`|`-E` | **Required.** The environment where the pipeline job deployed the app. |\n|`--status`|`-S` | **Required.** The deployment status. This value must be either `pass` or `fail`. |\n|`--joburl`|`-J` | _Optional_. The URL to the job's deployment logs. |\n|`--appurl`|`-A` | _Optional._ The URL where the deployed app is running. |\n|`--deployableid`| `-I` | _Optional._ The deployed app's application ID. You can get the ID by running the Cloud Foundry CLI's `cf env` command. The application ID is listed under `VCAP_APPLICATION`. |\n\n### An example command\n\nIn this an example, the command uploads a deployment record from a pipeline job. The deployment is to the \"staging\" environment. The deployment is successful and the app is running at a specified URL.\n\n```shell\nidra --publishdeployrecord --env=\"staging\" --status=pass --appurl=\"https://app.staging.example.com\"\n```\n\n## Making Decisions about Build Quality using Gate Policies\n\nTo use this feature, create a quality policy by using the user interface. Navigate to your toolchain, click on **DevOps Insights** card. Then on the left menu, click on **Deployment Risk**->**Policies**.\n\nUse the `--evaluategate` command (alias `-g`) to request a gate decision for a DevOps Insights policy in your pipeline. If the policy is satisfied, the pipeline continues running. If not, and you use the `--forcedecision` flag, the pipeline stops running.\n\n### Command syntax and options\n\n```shell\nidra --evaluategate --policy= [--forcedecision] [--env=] [--type=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--policy`|`-P` | **Required.** The name of the policy that the gate uses to make its decision. |\n|`--forcedecision`|`-D` | _Optional._ This flag causes the process to exit with an error code if the policy evaluation fails. If you do not include it, the pipeline will run regardless of the gate's decision. |\n|`--type`|`-E` | _Optional_. A rule type to consider. If you include this option, only rules of this type are considered in the decision-making process. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, and `sonarqube` for SonarQube scans. |\n|`--env`|`-T` | _Optional._ The environment that is considered in the decision-making process. Test results that are not associated with this environment are excluded from the process. |\n\n\n\n## Release History\n_(Nothing yet)_\n","readmeFilename":"README.md","_id":"grunt-idra3@0.1.21","_shasum":"8a660c3658690181816c4b9c01fc5ec7e7ef4d57","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.2","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"8a660c3658690181816c4b9c01fc5ec7e7ef4d57","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.21.tgz","fileCount":54,"unpackedSize":250076,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbGrmaCRA9TVsSAnZWagAAymEP/14jipTBZTlbgqE6QFHX\n4JfHf9hBFKYZIF76yQAPiHpGEMZ6mDYauZGWFMU5966btVGLp6m5PTOCXKKj\nOReqHv0YQNShYflLIGqfPab00bKfG9QCE4A6ewg2d7Mewd3Oj6OMz90iv9RE\n2VrHzqodvJoF6XnIxlbgoxW0Aej4EZez+/gR5jlJmChSc+nEuRDjEfLckWwT\nXxjPGhsrg4WF5ALzeA6h60gzQMX4ZuYZoxeA1tM2ct0VpxnB/k4vDsXzXwM6\n8FoBxTxedQKHF4KkSrRE/PouuWmfyctmGIh7vXzO6iab69JochMTuN4LMdto\n9J/o0RfKmpibjtEJHqtD1xFxXpa9O6+8PMX0AoJb1RNu5vIcrFQVoQjjiV1B\n+iGwPowcvx6m/plwzI+7UK4EATQttj6EviMp8rhbwMoJQ+Dq8irgQIbv+LrX\nQJz/zYtNvWUKqwe+FHMZnaDE6kc5saMfRbXRAZntFM0uvvIRV9hKoXJN+5sg\n8e79bq/VYK+GxnNRBk06cXitUyzjybV3zyXyJ5RgI7OaU3UuEpzrbAsTpzlF\neoLHqjmzn62haPXL7z/dXx0g9B/QgpCHvYJ+FJLXBGK0sHi+IZUugBA7Rx1h\n8ERaKBMc2AETr5vweCTMWmNMO7Vc3Huj5fQG/DH5dkStEw1U87QTnK92o3t/\nno6R\r\n=gnyI\r\n-----END PGP SIGNATURE-----\r\n","integrity":"sha512-ETrwuRo1ANQdwpUt2JhmV1D9O3rEQ+1M9sD1xjkT18ttAmemtERJVLDb6C0CW39JxTW+YqFoif+Nwn1MAAYHMg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCHzHk23v39BCAlvGcbQVZeBB2BrDVUWHEf9lbW+0b/QECIQCqQ7krU1xGk+ba7tuiNJDoAjjcZxpeedK2GQDtKxmKAw=="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.21_1528478106302_0.35458965478285664"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.22":{"name":"grunt-idra3","version":"0.1.22","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.2.5","sonar-scanner":"^1.0.1"},"dependencies":{"async":"2.1.4","command-line-args":"4.0.6","extend":"3.0.1","glob":"7.1.2","inquirer":"^3.0.0","mime":"1.3.4","request":"2.83.0","url":"0.11.0","valid-url":"1.0.9","xml2js":"0.4.16"},"_id":"grunt-idra3@0.1.22","_shasum":"3ab14719198c04aae53c6a230ab391543919eab1","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.2","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"3ab14719198c04aae53c6a230ab391543919eab1","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.22.tgz","fileCount":54,"unpackedSize":247825,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbGtPtCRA9TVsSAnZWagAANCsP/Rt8IA7tFIDfNuL+Lbeo\n0cez0nYXAv1j3cQzYmLWBzWc53bUy3xkbfyjrE7R5qSxmiiA8MoTMyWVP/N2\n5QoqFVI1lqZtHa5BhkfBlo90n6pBG0wSBXA1fZcahGnUNETeDDx7ZyyGYWQC\nHBVH66ip+y/PFta4/FYb73SLI+JC5p6L1fKbqP3ahpdu3gQ6ySxUTfbDul4n\nVpIaQcpM00ckhZ5Cmfv1iduprRwHkRTQ7qmxxW0QwqfuviCixZqHOeO8M0q3\nNxkyWcUfYT/V2g/j7dalggg4A9TtkO+2x6YLuYIDZAbtxIdD1H7MMa1N5YZg\ncoQT9sqoaVPvMleWVez2hs9+LMBqITS4tKAbFRDcpivt/7ZEqvWNxT33WYOD\nyOMg/7uomNW9c+DpIrv5sv6rANzJJ3CxRpWeJQqNoidtKdHhAlDgxzs7b5HJ\np1Cb24qm7LqClDLeAQunhNmu/k//gK5LTZ6+thrIxR0sV8vZPAhAKvip0WSa\nE+HM695ue1a0MgKUEmQZj/6OBAeXcGnZHTg6GLYRh43L2t2LJGXkuc34uT4J\nIH/nmOQ1moBIL6kvJXH3i5q6r3DszYduvHnkCnLz6EMnV9gJMDCr42/zu3G7\nlXDN11TZ//VLolNg4tRT/6Xf8w1mr1cXc6YJrmMR/dGYJ5mNpYgmwFAQx4a1\nsHzS\r\n=Z2/L\r\n-----END PGP SIGNATURE-----\r\n","integrity":"sha512-QhSNkzVE9QHG/J68yiRvh6nvp3duxyz/NO5ZjFeiNkj9t6iyAYs64BoUbXVydJ6TyvFW2y7BtE8HRd53n8qBBw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIEqoDJRwcPDmvHyjbJ3h9WApNxDWGJdaGaMie6qm6UoEAiEAva3JwTLC6K2FjmBYCuJbomr2OhNXxi0VbR38Wm6BNnI="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.22_1528484844909_0.709150803999566"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.23":{"name":"grunt-idra3","version":"0.1.23","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.2.5","sonar-scanner":"^1.0.1"},"dependencies":{"async":"2.1.4","command-line-args":"4.0.6","extend":"3.0.1","glob":"7.1.2","inquirer":"^3.0.0","mime":"1.3.4","request":"2.83.0","url":"0.11.0","valid-url":"1.0.9","xml2js":"0.4.16"},"readme":"# idra\n\n> Command Line utility for integrating with IBM® DevOps Insights\n\nTo install this utility\n```\nnpm install -g grunt-idra3\n```\n\n# Table of Contents\n1. [Getting Started](#getting-started)\n2. [Scenarios](#scenarios)\n 1. [Prerequisites](#prerequisites)\n 2. [Environment Variables](#environment-variables)\n 3. [Enabling Debug Logs](#enabling-debug-logs)\n 4. [Using the CLI](#using-the-cli)\n3. [Upload Build Records](#upload-build-records)\n4. [Upload Test Results](#upload-test-results)\n5. [Upload SonarQube Results](#upload-sonarqube-results)\n6. [Upload Vulnerability Scan Results](#upload-vulnerability-scan-results)\n7. [Upload Deployment Records](#upload-deployment-records)\n8. [Making decisions about Build Quality using Gate Policies](#making-decisions-about-build-quality-using-gate-policies)\n\n\n## Getting Started\n\nUse this utility to integrate IBM® DevOps Insights with Travis CI, Concourse, IBM Urban Code Deploy, IBM Continuous Delivery Pipelines and other CI/CD tools. If you are using Jenkins, use this [Jenkins plugin](https://plugins.jenkins.io/ibm-cloud-devops) instead.\n\nUsing this utility, you can\n- publish build records, test records and deploy records to IBM® DevOps Insights \n- make go/no-go decisions about a build's quality by using a Gate policy\n\nFor samples of dashboards in IBM® DevOps Insights, see [Value Proposition](https://plugins.jenkins.io/ibm-cloud-devops).\n\nFor more information about IBM DevOps Insights, see [the official documentation](https://console.bluemix.net/docs/services/DevOpsInsights/index.html).\n\n### Scenarios\nThis document covers two scenarios:\n1. You are integrating DevOps Insights with IBM Continuous Delivery tool.\n2. You are integrating DevOps Insights with other CI/CD tools (e.g., Travis CI, Concourse, IBM Urban Code Deploy, others)\n\n### Prerequisites\n\nTo use the CLI, you need to do the following. These steps should take about 10 minutes.\n\n1. A valid IBM Cloud account. If you don't have one, [register here](https://console.bluemix.net/registration).\n\n2. Once you have an account, you can create an API Key. Log in to [IBM Cloud](https://console.bluemix.net). Click on **Manage**->**Security**->**Platform API Key**. On that screen, create an API Key.\n\n3. An IBM Continuous Delivery toolchain. To create a toolchain:\n- Go to https://console.bluemix.net/devops\n- Click on **Create a Toolchain** button and then select **Build Your Own Toolchain** template. \n- In the next screen, click **Create**.\n- From the URL displayed in the browser, make note of your toolchain id. For example, if your URL is https://console.bluemix.net/devops/toolchains/05572df3-01dc-441b-911d-b2202fe33f96, the toolchain id is the long string after **toolchains/**\n- You can always navigate to your toolchain by [clicking here](https://console.bluemix.net/devops)\n\n4. Add DevOps Insights tool to your toolchain\n- Go to your toolchain\n- Click on **Add a Tool** button\n- Select DevOps Insights tool and click **Create Integration** button\n\n5. Your CI/CD tool must have Node.js® 4.x or greater.\n\n### Environment Variables \n\nIf you are using Travis, Concourse or any CI/CD tool other than the IBM Continuous Delivery pipeline, then set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|TOOLCHAIN_ID| **Required.** The toolchain's GUID |\n|IBM_CLOUD_API_KEY| **Required.** The Bluemix user's Api key|\n|BUILD_NUMBER| **Required.** Any string that identifies the build |\n|LOGICAL_APP_NAME| **Required.** The application's name.|\n\n\n\nIf you are using IBM Continuous Delivery pipeline, you need to set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|BUILD_PREFIX| **Required.** Any string. For example, the Git branch name. |\n|LOGICAL_APP_NAME| **Required.** The application's name.|\n|PATH|**Required.** In order to have required version of Node.js in your path, set the PATH variable before invoking the utility: `export PATH=/opt/IBM/node-v4.2/bin:$PATH`|\n\nIf you are using IBM Continuous Delivery pipeline and if you want to publish Insights data to another toolchain, then set the following environment variables. \n\n|Name|Description|\n|-----|-----|\n|TOOLCHAIN_ID| **Required.** The target toolchain's GUID. The toolchain id provided here should be from the same environment pointed by the BLUEMIX_CONSOLE_URL (If BLUEMIX_CONSOLE_URL is not provided then it should be in USSouth Bluemix public ) |\n|IBM_CLOUD_API_KEY| _Optional._ If the target toolchain is owned by different user than that owner's Bluemix Api key|\n|BUILD_PREFIX| **Required.** Any string. For example, the Git branch name. |\n|LOGICAL_APP_NAME| **Required.** The application's name.|\n|PATH|**Required,** In order to have required version of Node.js in your path, set the PATH variable before invoking the utility: `export PATH=/opt/IBM/node-v4.2/bin:$PATH`|\n\n\n\nIf you are using IBM UrbanCode Deploy, DevOps Insights relies on the previous set of variables, and this one:\n\n|Name|Description|\n|-----|-----|\n|UCD_REQUEST_ID| This maps to the ${p:request.id} property value. |\n\n### Enabling Debug logs\nIf you want to enable debug logs for the DevOps Insights CLI, set the `IDRA_DEBUG` environment variable to `true`. This works in all environments.\n\n|Name|Description|\n|-----|-----|\n|IDRA_DEBUG| When this value is `true`, the DevOps Insights CLI's debugging mode is enabled. By default, the value is `false`. |\n\n\n### Using the CLI\n\nSet [environment details](#environment-details) as described above. Ensure that Node.js 4.2 or higher is avaialble in your CI/CD tool.\n\nTo install this utility, use `npm install -g grunt-idra3`\n\nThen you can invoke the CLI with the `idra` command. You can run the CLI in any pipeline job's command script. For example, this command uploads functional verification test results to DevOps Insights:\n\n```\n# Upload test results\nidra --publishtestresult --filelocation=\"results.json\" --type=fvt\n```\n\n\n## Upload Build Records\nUse the `--publishbuildrecord` command (alias `-b`) to upload build records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishbuildrecord --branch= --repositoryurl= --commitid= --status= [--joburl=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--branch`|`-B` | **Required.** The repository branch on which the build is being performed. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--repositoryurl`|`-R` | **Required.** The url of the git repository. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--commitid`|`-C` | **Required.** The git commit id. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--status`|`-S` | **Required.** The build status. This value must be either `pass` or `fail`. |\n|`--joburl`|`-J` | _Optional_. The URL to the job's build logs. |\n\n\n### An example command\n\nIn this an example, the command uploads a build record from a pipeline job.\n\n```shell\nidra --publishbuildrecord --branch=master --repositoryurl=\"https://github.com/oic/dlms.git\" --commitid=dff7884b9168168d91cb9e5aec78e93db0fa80d9 --status=pass\n```\n\n## Upload Test Results\n\nUse the `--publishtestresult` command (alias `-p`) to upload results from these test types to DevOps Insights:\n\n* Unit tests\n* Code coverage tests\n* Functional verification tests (FVT)\n* Static security scans from IBM Application Security on Cloud\n* Dynamic app scans from IBM Application Security on Cloud\n* [SonarQube results](#uploading-sonarqube-results)\n\n\n### Command syntax and options\n\n```shell\nidra --publishtestresult --filelocation= --type= [--tool=] [--drilldownurl=] [--env=] [--token=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--filelocation`| `-F` |**Required.** The location of the test results that you want to upload. This can be a single file, an entire directory, or multiple files that match a wildcard expression.|\n|`--type`| `-T` |**Required.** The type of test results that you want to upload. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, and `sonarqube` for SonarQube scans. In addition to these types you can also use a custom quality data set tag to upload test results of different type.|\n|`--tool`| `-L` |_Optional_. The name for the test tool. |\n|`--drilldownurl`| `-U` |_Optional._ A URL where more information about the test results can be found. If this URL is invalid, the option is ignored. |\n|`--env`| `-E` |_Optional._ The environment name to associate with the test results. This option is ignored for unit tests, code coverage tests, and static security scans. |\n|`--token`| `-K` |_Optional_. This is a SonarQube token. This flag is valid only if the type specified is `sonarqube`. It is used by the CLI to pull additional information from the SonarQube server. |\n\n### An example command\n\nIn this example, the command uploads all JSON-formatted FVT results from a directory to DevOps Insights. Additionally, a test tool is declared, a test result URL is given, and a logical staging environment is provided. Specifying an environment is especially important when you want your results to be analyzed alongside other activities that take place in that same environment.\n\n```shell\nidra --publishtestresult --filelocation=\"tests/fvt/*.json\" --type=fvt --tool=\"your-test-runner\" -drilldownurl=\"https://example.com/testinfo\" --env=\"staging\"\n```\n\n### Supported Test Formats\n|Type of Test|tag|Supported Formats|\n|-----|-----|-----|\n|Unit Test|`unittest`|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Test Case|`fvt`|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Code Coverage|`code`|Cobertura (xml), lcov, Istanbul, JaCoCo|\n|SonarQube|`sonarqube`|SonarQube|\n|Static Security Scan|`staticsecurityscan`|IBM Application Security|\n|Dynamic Security Scan|`dynamicsecurityscan`|IBM Application Security|\n|Vulnerability Advisor|`vulnerabilityadvisor`|Vulnerability Advisor|\n\nFor golang [gocov](https://github.com/axw/gocov/) users, please convert to Cobertura using [gocov XML(Cobertura) export](https://github.com/yaoyaozong/gocov-xml)\n\n## Upload SonarQube Results\nTo upload data from SonarQube, you must provide the SonarQube server token using ```--token```. Your SonarQube server is not required to be accessible from your CI/CD tool.\n\nAfter you run a scan using SonarQube, you can upload SonarQube results by running this command.\n\n```idra --publishtestresult --filelocation=.scannerwork/report-task.txt --type=sonarqube --token=234234434```\n\nIn the above command, report-task.txt is a file generated during the SonarQube scan.\n\nIf this command fails for some reason, you can enable logs by setting IDRA_DEBUG environment variable to true.\n\nIf you are using self-signed certificates for SonarQube server, you will need to set ```export NODE_TLS_REJECT_UNAUTHORIZED=0```\n\n\n## Uploading Vulnerability Scan Results\n\nUse the `--publishvulnerabilityresult` command (alias `-v`) to upload [vulnerability advisor](https://console.bluemix.net/docs/containers/va/va_index.html) results to DevOps Insights:\n\n### Command syntax and options\n\n```shell\nidra --publishvulnerabilityresult --image= --account=\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--image`| `-M` |**Required.** Name of image including the repository and the tag.|\n|`--account`| `-O` |**Required.** The unique ID for your IBM Cloud account. Run 'bx cr info' to get the ID of the target account. |\n\n### An example command\n\nIn this example, the command uploads the vulnerability scan details of the image specified, to DevOps Insights. It gets the details by querying the relevant image repository.\n\n```shell\nidra --publishvulnerabilityresult --image=\"registry.ng.bluemix.net/auser/hello-containers-auser-1129:1\" --account=65fc31e13b143434540bcb495\n```\n## Upload Deployment Records\nUse the `--publishdeployrecord` command (alias `-d`) to upload deployment records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishdeployrecord --env= --status= [--joburl=] [--appurl=] [--deployableid=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--env`|`-E` | **Required.** The environment where the pipeline job deployed the app. |\n|`--status`|`-S` | **Required.** The deployment status. This value must be either `pass` or `fail`. |\n|`--joburl`|`-J` | _Optional_. The URL to the job's deployment logs. |\n|`--appurl`|`-A` | _Optional._ The URL where the deployed app is running. |\n|`--deployableid`| `-I` | _Optional._ The deployed app's application ID. You can get the ID by running the Cloud Foundry CLI's `cf env` command. The application ID is listed under `VCAP_APPLICATION`. |\n\n### An example command\n\nIn this an example, the command uploads a deployment record from a pipeline job. The deployment is to the \"staging\" environment. The deployment is successful and the app is running at a specified URL.\n\n```shell\nidra --publishdeployrecord --env=\"staging\" --status=pass --appurl=\"https://app.staging.example.com\"\n```\n\n## Making Decisions about Build Quality using Gate Policies\n\nTo use this feature, create a quality policy by using the user interface. Navigate to your toolchain, click on **DevOps Insights** card. Then on the left menu, click on **Deployment Risk**->**Policies**.\n\nUse the `--evaluategate` command (alias `-g`) to request a gate decision for a DevOps Insights policy in your pipeline. If the policy is satisfied, the pipeline continues running. If not, and you use the `--forcedecision` flag, the pipeline stops running.\n\n### Command syntax and options\n\n```shell\nidra --evaluategate --policy= [--forcedecision] [--env=] [--type=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--policy`|`-P` | **Required.** The name of the policy that the gate uses to make its decision. |\n|`--forcedecision`|`-D` | _Optional._ This flag causes the process to exit with an error code if the policy evaluation fails. If you do not include it, the pipeline will run regardless of the gate's decision. |\n|`--type`|`-E` | _Optional_. A rule type to consider. If you include this option, only rules of this type are considered in the decision-making process. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, and `sonarqube` for SonarQube scans. |\n|`--env`|`-T` | _Optional._ The environment that is considered in the decision-making process. Test results that are not associated with this environment are excluded from the process. |\n\n\n\n## Release History\n_(Nothing yet)_\n","readmeFilename":"README.md","_id":"grunt-idra3@0.1.23","_shasum":"8e0a6996f8af1866dd1f6d5f234dd78817a40fab","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.2","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"8e0a6996f8af1866dd1f6d5f234dd78817a40fab","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.23.tgz","fileCount":54,"unpackedSize":247323,"integrity":"sha512-Dp2I9rnuAJvYkEE/S5fTiD0XpypoRuh0wtwSuu03CkhNRWrSys4gYLPcV+P6osXyF/VBuajgUO66FrjNWR9VJA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDZEr8/j/o27NUpztlPU2iR+o2Om8sCjIp0a4JNt8KC4wIgfC5iCcfxFxfAoatJ33vz9sUp65HT76THkqbMWh89dkg="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.23_1529526637736_0.9082790591218617"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.24":{"name":"grunt-idra3","version":"0.1.24","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.2.5","sonar-scanner":"^1.0.1"},"dependencies":{"async":"2.1.4","command-line-args":"4.0.6","extend":"3.0.1","glob":"7.1.2","inquirer":"^3.0.0","mime":"1.3.4","request":"2.83.0","url":"0.11.0","valid-url":"1.0.9","xml2js":"0.4.16"},"_id":"grunt-idra3@0.1.24","_shasum":"68919e19ce13c2bb8b90d65992006f7d162ecc4b","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.2","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"68919e19ce13c2bb8b90d65992006f7d162ecc4b","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.24.tgz","fileCount":54,"unpackedSize":247544,"integrity":"sha512-lBn6i3HKeAsjL+NncpmK/g1v0V87FVxTiSjxkNVvp1NHudBm8iDN/75Kt4O4li8+C9K9vG4b8KtuDeJlEVfitg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIBFSm3tZUxbGXB5jiVWLTlyTCm3jvCUkI3WtiErXDPvVAiBYV078l14jO+rWl6t81nF4+yh/+4+lJlUlF+G/5tafzw=="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.24_1529599287870_0.2699157342656351"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.25":{"name":"grunt-idra3","version":"0.1.25","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.1","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^2.2.5","sonar-scanner":"^1.0.1"},"dependencies":{"async":"2.1.4","command-line-args":"4.0.6","extend":"3.0.1","glob":"7.1.2","inquirer":"^3.0.0","mime":"1.3.4","request":"2.83.0","url":"0.11.0","valid-url":"1.0.9","xml2js":"0.4.16"},"_id":"grunt-idra3@0.1.25","_shasum":"8297d083550424a82cad02728b7ad91d50fa0260","_from":".","_npmVersion":"3.10.10","_nodeVersion":"6.11.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"8297d083550424a82cad02728b7ad91d50fa0260","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.25.tgz","fileCount":59,"unpackedSize":246021,"integrity":"sha512-2xGXnZWOoAUJC151hRzocsJJb7mFquDUhnCXoIKmafOW0FoBzHL/lpBkw7Vtmo/r8/446lhZtOilbzE0wvf4hw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDxgSawfeo2Lm40jOkfd7GckSz407dntz6R9Bz5FJ7fWwIgaz5m/Pvvg8WA22GoAcM8OKatmcsedZVPwhMPmZczSW8="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.25_1531518261290_0.29424584468407744"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.26":{"name":"grunt-idra3","version":"0.1.26","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.3","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^5.2.0","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","inquirer":"^3.0.0","mime":"^1.4.1","request":"^2.87.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.1.26","_shasum":"eb2cc5c890d3448739a55337b8fd3cab879f3381","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.2","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"eb2cc5c890d3448739a55337b8fd3cab879f3381","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.26.tgz","fileCount":53,"unpackedSize":164447,"integrity":"sha512-0EF8nLHo0pcV47BbrlFITjhNzexDwJUOa/h26wRosSFUhKgBl+mkeuYALJHBm3Th7TvrIXQbAbcALTg5XCPs/g==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIGQZW/fwLTD+eupfJuAzqfiu2mVZyvwBqQp4G4JNcW2mAiEAse/5WwCrLjlkHcK71Tkf6d8u6/uezQPmUc/kEi2MJ/A="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.26_1533325813500_0.9337029968247281"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.27":{"name":"grunt-idra3","version":"0.1.27","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.3","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-mocha-test":"^0.12.7","mocha":"^5.2.0","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","inquirer":"^3.0.0","mime":"^1.4.1","request":"^2.87.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.1.27","_shasum":"f2679bfe0a1d70013a3216f5a392d51b851b957e","_from":".","_npmVersion":"2.14.7","_nodeVersion":"4.2.2","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"f2679bfe0a1d70013a3216f5a392d51b851b957e","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.27.tgz","integrity":"sha512-pu8Kae+yXtdaSBkzLqyM2fEtJ9RpSQlBCgtUKJStC/q6ouE617MNgsQLxwpyHG0VweWOXVST5dIZhj5cMyTS2w==","fileCount":53,"unpackedSize":164448,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbahY8CRA9TVsSAnZWagAAd/IP/iMxXFeZZR7fzj1atbu8\nl6h3ZXE0D9vx9CqN2KJ4bhR3h9WorDDSKr2RcNHQER+5Y7K+OtJCVXky5jsm\nlnaYjB7frT1Oisp2d6NbgTVUUChDbjpgNkh4SenWM3417D58VlJa2/O64h0R\nl+XBuJbc3+EOi5s0FPKPfLzIHj6FHOzlltHuJM64D2k20kcAEVWalbVBQrPq\nSWpaA/izoFAmG0QO2IJF72qnMa2cpYKnt7To9bikwwxstrQUiRrrTe3mmMDR\na5x1VpfOI2YS+C31OAMv/VaOPUJIMkwas18yHXAyrloT46tgpfuIYOjjjXSY\nD2A0KawgZJOMEnU4vfIBSUXJL5d40R3+8a/GOoUo5m/h+DE/GDlq70onQqum\nM7q6gJA+VPa9PosI34mmltLFc54qTAGtSbry0GLMMZ2KW/z0WX6UTIuEu5wn\nWT4x/j7NZx2It05FvP5oKJM2cV25SjRXw518gzbp4HUFuEhpOdZU83WqgzDL\nMPzH5b9hXn2XxhxydHiKOWEHNbD93wCpuXurCvi7Zc33XtiNyvmDmyZtcWVe\nt6maMzIOopVVwuziFBm66macx/NhUWYPpsq0WQbbP02KLQb0u13V6NyrEk07\nsJBbWwkCC6u5StQi0t9GN+YJdHRt73ArZfuQgLI6pjLtUgGnKaCGvxOzeLOW\nWHFG\r\n=KwYE\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCJVrpe6fbz44kyv2wFL3lvEIi5bcI+VT7pbGST/hZS0wIhALYRfcogU5+UXpPlQ70bq5nqDbgC3K9jy1rhDbhS50A/"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.27_1533679164374_0.09863070111949224"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.28":{"name":"grunt-idra3","version":"0.1.28","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.3","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-eslint":"^21.0.0","grunt-mocha-test":"^0.12.7","mocha":"^5.2.0","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","inquirer":"^3.0.0","mime":"^1.4.1","request":"^2.87.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.1.28","_shasum":"034aa70e1681f080a889ebcf3b72d1633cf6e200","_from":".","_npmVersion":"3.10.3","_nodeVersion":"6.7.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"034aa70e1681f080a889ebcf3b72d1633cf6e200","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.28.tgz","integrity":"sha512-j1X7owY3DPAoYLkts4pG6Gl4osp7EHCQOI2RiDyrPa1GM9dEC8cZMReqzEY0oB69BStfpJCBuGULJPKGwPYCow==","fileCount":54,"unpackedSize":163210,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbcx76CRA9TVsSAnZWagAAmskP/1roHzYZRZokWux/vVxF\nYRUBJwU/w/IUBfh1XdaMb4VsgEY4szOGDqAdt8WLDeAP9Ee20pfyvrTO7v5y\nAGk6o7JJoGAVCJeY9UvB79oiSjMI7bgaxBAZK4T7LOydUpMib84ZORonzcvW\nyDelOtbmPlUP0QMwJtb5rncXO+cBvOBTgbwTsi7PS46Le+5UMCxgwWKudUsQ\neVY9HSIwWZ+vpYgW+QSVoe/pF3d8pa04Uo/NCHUUcrA882agfc5YUeJMjqmj\n5UDQcvESfJzxpM4uCJTjqb+bgYoqzdu8J9JakxUVr3J6K4/GdArXxHYp1uS+\nXVbT5w951X2brVsH5YE7eqp+QIoKKFAhdcgbx5q+mCoeFqtfJhmysShiHE7g\neYnfn+hmmdAS+kzX7bc9XqL1B0APhnyMp5Bmh9gzxy/+jmwOKQJ3T8XqvVnf\nHy6Zg0gW1ghhXWOw0lO8bmEM0jVYJzRnCzc6ZRHuquQ6L4QvqlkHCQ0GRkkj\nw/KeXQSEkXb+zzFctnyuCfdVGL1GpDlqgPXB93/6ocnIRN/LJR8GaxLmAyBh\nYo629ny0qxUordy/bV9r0wmK7Gtkp4KWz2sM4AdnhjYERS+Z0W2nSTdsK7y5\nmmA9SVZfjyGprwUaw4GsVczEYaA6YKJoEp+0EEP8pL2LQOESxVcXrAbBhWwu\n5QN/\r\n=RZ0U\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQD4z6wypaBpgG+cZW4dryW/XlJlrHfGhL3cqWWSKnh+0QIgEgds5+B6M1MUvsqHexclZvE1PcfO+q99A2lLyWGSIeo="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.28_1534271225511_0.44328827929339476"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.29":{"name":"grunt-idra3","version":"0.1.29","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.3","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-eslint":"^21.0.0","grunt-mocha-test":"^0.12.7","mocha":"^5.2.0","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","inquirer":"^3.0.0","mime":"^1.4.1","request":"^2.87.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.1.29","_shasum":"17ac35e55476145bfa39fac26bab9f961bd8764b","_from":".","_npmVersion":"3.10.3","_nodeVersion":"6.7.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"17ac35e55476145bfa39fac26bab9f961bd8764b","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.29.tgz","integrity":"sha512-gdaOLED6edYwNlLTUd5m1jmz0xX3NNYoQ2xHWQ/pmupcYioso+9BUWiN0FWu1jt36dZYu9/0OZjn7l5BX7vStw==","fileCount":54,"unpackedSize":163211,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbczgCCRA9TVsSAnZWagAA1wEP/1DkY16zj9OnvxPIzTMD\nBXeSDyXX6CRz4Gi9hNJw41p+zzQi8161YqRNaoPndJrUURHvn1EpOKuosaTU\nIRcm4FO9kDwklf3qD6fH9zyDu1jwCelZrJRM8gYqrFoLp5ElUnTyJtZvgQxO\nTsu1rMqL1aLKorqFiwMPCMK0wx+iTd0RK9dS9jlJDtYmwjqmBfQjYDw1Z/34\nG7Vm2/QO7VoUWWTtFYg7sCKb0R29rkj4TPfj3MunppmJSCru8VkdbaX27SGP\nc0J9pXooYbxcodRSAZLbXabdhqdGvNWwTagOSjHpcAzmt9LAVacDxMfyX8Eh\nlOBbAq3wV8xFhLy80y8HkDJVOedGoSKH5LmMiPj+HfMj2N11kuFYXta9G+2A\nAy/jfe8nRFYZWlr5krSqK9VfUgphgJcPLxPdYKlNw4oImeq9WRIKQ92Tx2ZQ\nk/7ZrvZ9dc3To/I815YIEV0B3M47pOjI0eClbLZgt+XizY30sDWYy/ui7KOW\nbyZQjfD0mp4I2qZZVLf5fMk1eYF/8em1pKPjJepcdA+AixioaHuFiEP09mln\nmvtE030WAhKbpEyPInoQrGsJUsByjUZltIaGZhqEYOYTiXPl1oABLpnubnQB\n7rjEXQPfAPFOKUz/EOvggkbCBn5j6OcFXwyFHtRaKar964KjO5AhlsfnQLoJ\n6xzG\r\n=4z9r\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDl6+3HOaSYrrFVROTuXE0yS7AcGnIr1jR/L3UylU5ERgIgDri03khadxw1wAYgO62rjNpDAZs55cEhllVujdWLods="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.29_1534277633777_0.21136239724942096"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.30":{"name":"grunt-idra3","version":"0.1.30","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.3","grunt-contrib-clean":"^1.0.0","grunt-contrib-jshint":"^1.0.0","grunt-eslint":"^21.0.0","grunt-mocha-test":"^0.12.7","mocha":"^5.2.0","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","inquirer":"^3.0.0","mime":"^1.4.1","request":"^2.87.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.1.30","_shasum":"b78b628b0dc22fca2e583a755d636e644bdaa379","_from":".","_npmVersion":"3.10.3","_nodeVersion":"6.7.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"b78b628b0dc22fca2e583a755d636e644bdaa379","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.30.tgz","integrity":"sha512-ewK08F/tkmKV4w7hG/M4DffeVNTEJKpuQ3OBrtrq8w5JzvBDp9B6J/0bOzY217rt2WyX92m1JSYcmDQ5oqCuuA==","fileCount":54,"unpackedSize":162229,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbfG8gCRA9TVsSAnZWagAAib4QAIGF04YraKMuT9FfJTYO\nnqhP81fIgt7Pl0EFaG/dyXEWNAgv9tZUJDWxziDm5oohjskhkP0RxSLvk8tm\nwKSl+g/A+hddiiwAaCPurkZe1WJ826PpnfSqw+lXZxIuy2CXnxAawh18+Q3A\n59omw+RiVKbmr4DG4mdgf9elgLkE3x4ih6Pthr/AUqQZX+WySSZnDsFEf6fd\n5HxBYWRpgle/9EICt4f4/D5XZOJaXvtEHdl5PSR/Ts7BFMaCdLzuiCGLEh6X\nMBj6Ym6Mvsml955F9i2RxHA9NZMFZiHWqbDO9SAthovh9TSYeib7ng5ngOTe\nSxXOC9BwG4L1ZJVxgLv/7g61NO5zx7QwxMYQE1TSXxyiVcGLdhg3U4imE1B1\nNSNUxzrYNdNetIWZ0zWkAmLxXtX+C4p5gtKtLJBH7vT928FzUXsYsnoLOYXN\nINDXshveUnejNUxD0sC9Hb9k0AUhlm+jZsnwSGv08YrTTeoFY2Z4S6VrttQ/\n8JdINhUoALM1ijEl+zanWkoErY2DG/ypqzSYo5dqMQUJOXMM37gRXUpnmp7Q\nD/x4IBVzdq8MpmWK9/mgQEL0K61Hh16RpablW9QUoNl6ZJibhiQMPRj/CBI5\np4iFctvjAEjFnF9PgPyUE8YtY8PoqUK+6xLP8qvJ683Vf7K+bJw1M4fQpwlY\nrNYa\r\n=l3JP\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIA7aJgWw1nHHmPIzmXq331LDJ78lHpOWzbkylkESI1GKAiA2xikalcVy0GMft7fVP5bRAu/qcy3b7uM8+BYc/VmZpA=="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.30_1534881565411_0.13249499584974633"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.31":{"name":"grunt-idra3","version":"0.1.31","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.3","grunt-contrib-clean":"^1.0.0","grunt-eslint":"^21.0.0","grunt-mocha-test":"^0.12.7","mocha":"^5.2.0","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","inquirer":"^3.0.0","mime":"^1.4.1","request":"^2.87.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.1.31","_shasum":"14eb4bdd09fe0f4ba987875962c5ed318731c800","_from":".","_npmVersion":"3.10.3","_nodeVersion":"6.7.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"14eb4bdd09fe0f4ba987875962c5ed318731c800","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.31.tgz","integrity":"sha512-t/RT0bMQhZLzTjQReiJ9miXbALTQ0yRBWDuryH1uNnHKDFo/OfVAekn/pGsuRF68tqgaClAvhxE5DbHDlMW7yA==","fileCount":48,"unpackedSize":167309,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJboB2WCRA9TVsSAnZWagAAsmEP/RGwBH3+eZGXPR4iAX0b\nErZJkpJdbONvx17jJv5tjqqiZx+/zTYUprrP6Yc/TC9XNkWiWxy5TGyhB8Vl\nEFJOvuXhz6TZybYyRTE2mNCtj9UAEBqHe3zlWy2wOZQusGfmJQsd7gI1QJKa\nbzQsbXmUtScZaH03ruzclPk6B9cWf46OWkBBC2Josv6VYYJRHKRmCKtVYPKA\nctx1K+sNDd3zAV9qIKep1jbV6cAIk+MKfDhkdpDHj+JgkSrCqzSFSWGDozC/\ng6AfKRwEuIDccDT1ugJVt1g74RPtqNXGerpL2ISxpfFAepRYjNMiNu2CZ9De\nMV9yPsaAQaBUwxTJtI1ElfhoeUPGFdZmjDIItAtnQIg7eutGGF/Fy3PXEoJd\nDYahgBWO0I8vmnMrf48MnxIw1Lzjs5iLNxgEconrxbyW8jK34XFuB6x26PkB\nlMv1lU2k/+Ael1lPwjEHNGDGIpdqGCor/lJJsV7TfY0ae4Q2MzStq9QjEptJ\njdeVRrtORGEdMOn4RZaQVJftRuGnKAzOBQuwl3wwrZJRiTXWtl6HPH/qQCHS\n0C36TsxWDP/bo2ZbrI785dvavnKe1wAqlYB40i7DotdmNxaSpOFB+NiOzdqO\nrAM0BZGblmK4JmYmzV5k4IIj2on3PZ3j8zjajTYO80UuuOASI2tWrgZ7zVKc\nQqYl\r\n=133a\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCICbRQLCpXZRvUeLdXcRt+wN8IJ3R46zLofErKdrSrSbnAiBV1yW8GtDwBhZniVxhwSNSgtD9hU7m97fmkhgZqjR/vQ=="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.31_1537219989036_0.14397821036848613"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.34":{"name":"grunt-idra3","version":"0.1.34","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.3","grunt-contrib-clean":"^1.0.0","grunt-eslint":"^21.0.0","grunt-mocha-test":"^0.12.7","mocha":"^5.2.0","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","inquirer":"^3.0.0","mime":"^1.4.1","request":"^2.87.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"readme":"# idra\n\n> Command Line utility for integrating with IBM® DevOps Insights\n\nTo install this utility\n```\nnpm install -g grunt-idra3\n```\n\n# Table of Contents\n1. [Concepts](#concepts)\n2. [Getting Started](#getting-started)\n 1. [Scenarios](#scenarios)\n 2. [Prerequisites](#prerequisites)\n 3. [Environment Variables](#environment-variables)\n 4. [Enabling Debug Logs](#enabling-debug-logs)\n 5. [Using the CLI](#using-the-cli)\n3. [Upload Build Records](#upload-build-records)\n4. [Upload Test Results](#upload-test-results)\n 1. [Upload SonarQube Results](#upload-sonarqube-results)\n5. [Upload Deployment Records](#upload-deployment-records)\n6. [Making decisions about build quality using gate policies](#making-decisions-about-build-quality-using-gate-policies)\n\n## Concepts\nIBM® DevOps Insights is a tool that provides insights into your DevOps projects. Use it to learn how compliant your team is with DevOps and developer practices, to manage risk in your codebase, and to automatically enforce quality standards in continuous delivery projects.\n\nUnderstanding of the following concepts will help in faster adoption of IBM® DevOps Insights for your projects.\n\n##### Toolchain\nToolchains are part of [IBM® DevOps Continuous Delivery](https://console.bluemix.net/docs/services/ContinuousDelivery/cd_overview.html#cd_overview). Toolchains provide an integrated set of tools to build, deploy and manage your apps. You can create toolchains that include IBM Cloud services, open source tools, and third party tools that make development and operations repeatable and easier to manage. It is required that the IBM DevOps Insights should be added as one of the tool to your toolchain.\n\n##### Integrating your build tool with IBM DevOps Insights\nThis means instrumenting your build tool with this CLI or DevOps Insights Jenkins plugin to send build, test and deployment records to IBM DevOps Insights.\n\n##### Build record\nIBM DevOps Insights needs to know when a build is complete. This record contains application name, branch, build id, reference to git repo and other fields. This CLI and Jenkins plugin has a command to publish the build record to DevOps Insights.\n\n##### Test record\nIBM DevOps Insights needs to know about the tests performed during the build process. It is necessary that the tests should generate some kind of JSON or XML based file. Here are the list of supported [format](supported-test-formats). The generated test file is published as a test record. Along with the test file this record contains application name, build id, type of tests and other fields. It is required that the application name and build id in the test record matches the one used in the build record for a given build. This CLI and Jenkins plugin has a command to publish test record to DevOps Insights.\n\n##### Deployment records\nIBM DevOps Insights needs to know about the deployments made during the deployment process. This record contains the application name, build id, environment name, status of the deployment and other fields. It is required that the application name and build id in the deployment record matches the one used in the build record for a given build. This CLI and Jenkins plugin has a command to publish a deployment to DevOps Insights.\n\n##### Build Id (or Number)\nThis is an arbitrary length string uniquely identifying each build. This id is used to tie the build, test and deployment records together so it is important to publish those records with the same id for a given build.\n\n##### Policy\nA policy is set of rules specified by the user that collectively defines what is considered a good set of test records for a given application build. Typically, one rule is added for each test record published to DevOps Insights. The policy rules are evaluated by the gate.\n\n##### Branch\nThis is the name of the branch in the source control system.\n\n##### Environment\nThis is the name of environment to which deployments are made during the build process.\n\n##### Data set\nThis is an arbitrary string that identifies the type of tests performed during the build process. Besides the standard names such as \"unit test\", \"fvt\". The tool allows the user to define a custom name.\n\n## Getting Started\n\nUse this utility to integrate IBM® DevOps Insights with Travis CI, Concourse, IBM Urban Code Deploy, IBM Continuous Delivery Pipelines and other CI/CD tools. If you are using Jenkins, use this [Jenkins plugin](https://plugins.jenkins.io/ibm-cloud-devops) instead.\n\nUsing this utility, you can\n - Publish build records, test records and deploy records to IBM® DevOps Insights \n - Make go/no-go decisions about a build's quality by using a Gate policy\n\nFor samples of dashboards in IBM® DevOps Insights, see [Value Proposition](https://plugins.jenkins.io/ibm-cloud-devops).\n\nFor more information about IBM DevOps Insights, see [the official documentation](https://console.bluemix.net/docs/services/DevOpsInsights/index.html).\n\n### Scenarios\nThis document covers two scenarios:\n1. You are integrating DevOps Insights with IBM Continuous Delivery tool.\n2. You are integrating DevOps Insights with other CI/CD tools (e.g., Travis CI, Concourse, IBM Urban Code Deploy, others)\n\n### Prerequisites\n\nTo use the CLI, you need to do the following. These steps should take about 10 minutes.\n\n1. A valid IBM Cloud account. If you don't have one, [register here](https://console.bluemix.net/registration).\n\n2. Once you have an account, you can create an API Key. Log in to [IBM Cloud](https://console.bluemix.net). Click on **Manage**->**Security**->**Platform API Key**. On that screen, create an API Key.\n\n3. An IBM Continuous Delivery toolchain. To create a toolchain:\n - Go to https://console.bluemix.net/devops\n - Click on **Create a Toolchain** button and then select **Build Your Own Toolchain** template. \n - In the next screen, click **Create**.\n - From the URL displayed in the browser, make note of your toolchain id. For example, if your URL is https://console.bluemix.net/devops/toolchains/05572df3-01dc-441b-911d-b2202fe33f96, the toolchain id is the long string after **toolchains/**\n - You can always navigate to your toolchain by [clicking here](https://console.bluemix.net/devops)\n\n4. Add DevOps Insights tool to your toolchain\n - Go to your toolchain\n - Click on **Add a Tool** button\n - Select DevOps Insights tool and click **Create Integration** button\n\n5. Your CI/CD tool must have Node.js® 4.x or greater.\n\n### Environment Variables\n\nIf you are using Travis, Concourse or any CI/CD tool other than the IBM Continuous Delivery pipeline, then set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|TOOLCHAIN_ID| **Required.** The toolchain's GUID |\n|IBM_CLOUD_API_KEY| **Required.** The Bluemix user's Api key|\n|BUILD_NUMBER| **Required.** Any string that identifies the build |\n|LOGICAL_APP_NAME| **Required.** The application's name.|\n\nIf you are using IBM Continuous Delivery pipeline, you need to set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|IBM_CLOUD_API_KEY| **Required** The Bluemix user's Api key|\n|BUILD_PREFIX| **Required.** Any string. For example, the Git branch name. |\n|LOGICAL_APP_NAME| **Required.** The application's name.|\n|PATH|**Required.** In order to have required version of Node.js in your path, set the PATH variable before invoking the utility: `export PATH=/opt/IBM/node-v4.2/bin:$PATH`|\n\nIf you are using IBM Continuous Delivery pipeline and if you want to publish Insights data to another toolchain, then set the following environment variables. \n\n|Name|Description|\n|-----|-----|\n|TOOLCHAIN_ID| **Required.** The target toolchain's GUID. If the target toolchain is owned by different user then provide the target toolchain owner's Bluemix Api key in the `IBM_CLOUD_API_KEY` variable.|\n\n\nIf you are using IBM UrbanCode Deploy, DevOps Insights relies on the previous set of variables, and this one:\n\n|Name|Description|\n|-----|-----|\n|UCD_REQUEST_ID| This maps to the ${p:request.id} property value. |\n\n### Enabling Debug logs\nIf you want to enable debug logs for the DevOps Insights CLI, set the `IDRA_DEBUG` environment variable to `true`. This works in all environments.\n\n|Name|Description|\n|-----|-----|\n|IDRA_DEBUG| When this value is `true`, the DevOps Insights CLI's debugging mode is enabled. By default, the value is `false`. |\n\n\n### Using the CLI\n\nSet [environment details](#environment-details) as described above. Ensure that Node.js 4.2 or higher is avaialble in your CI/CD tool.\n\nTo install this utility, use `npm install -g grunt-idra3`\n\nThen you can invoke the CLI with the `idra` command. You can run the CLI in any pipeline job's command script. For example, this command uploads functional verification test results to DevOps Insights:\n\n```\n# Upload test results\nidra --publishtestresult --filelocation=\"results.json\" --type=fvt\n```\n\n\n## Upload Build Records\nUse the `--publishbuildrecord` command (alias `-b`) to upload build records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishbuildrecord --branch= --repositoryurl= --commitid= --status= [--joburl=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--branch`|`-B` | **Required.** The repository branch on which the build is being performed. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--repositoryurl`|`-R` | **Required.** The url of the git repository. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--commitid`|`-C` | **Required.** The git commit id. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--status`|`-S` | **Required.** The build status. This value must be either `pass` or `fail`. |\n|`--joburl`|`-J` | _Optional_. The URL to the job's build logs. |\n\n\n### An example command\n\nIn this an example, the command uploads a build record from a pipeline job.\n\n```shell\nidra --publishbuildrecord --branch=master --repositoryurl=\"https://github.com/oic/dlms.git\" --commitid=dff7884b9168168d91cb9e5aec78e93db0fa80d9 --status=pass\n```\n\n## Upload Test Results\n\nUse the `--publishtestresult` command (alias `-p`) to upload results from these test types to DevOps Insights:\n\n* Unit tests\n* Code coverage tests\n* Functional verification tests (FVT)\n* Static security scans from IBM Application Security on Cloud\n* Dynamic app scans from IBM Application Security on Cloud\n* [SonarQube results](#upload-sonarqube-results)\n\n\n### Command syntax and options\n\n```shell\nidra --publishtestresult --filelocation= --type= [--drilldownurl=] [--env=] [--token=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--filelocation`| `-F` |**Required.** The location of the test results that you want to upload. This can be a single file, an entire directory, or multiple files that match a wildcard expression.|\n|`--type`| `-T` |**Required.** The type of test results that you want to upload. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, and `sonarqube` for SonarQube scans. In addition to these types you can also use a custom quality data set tag to upload test results of different type.|\n|`--drilldownurl`| `-U` |_Optional._ A URL where more information about the test results can be found. If this URL is invalid, the option is ignored. |\n|`--env`| `-E` |_Optional._ The environment name to associate with the test results. This option is ignored for unit tests, code coverage tests, and static security scans. |\n|`--token`| `-K` |_Optional_. This is a SonarQube token. This flag is valid only if the type specified is `sonarqube`. It is used by the CLI to pull additional information from the SonarQube server. |\n\n### An example command\n\nIn this example, the command uploads all JSON-formatted FVT results from a directory to DevOps Insights. Additionally, a test tool is declared, a test result URL is given, and a logical staging environment is provided. Specifying an environment is especially important when you want your results to be analyzed alongside other activities that take place in that same environment.\n\n```shell\nidra --publishtestresult --filelocation=\"tests/fvt/*.json\" --type=fvt --tool=\"your-test-runner\" -drilldownurl=\"https://example.com/testinfo\" --env=\"staging\"\n```\n\n### Supported Test Formats\n|Type of Test|tag|Supported Formats|\n|-----|-----|-----|\n|Unit Test|`unittest`|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Test Case|`fvt`|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Code Coverage|`code`|Cobertura (xml), lcov, Istanbul, JaCoCo|\n|SonarQube|`sonarqube`|SonarQube|\n|Static Security Scan|`staticsecurityscan`|IBM Application Security on Cloud|\n|Dynamic Security Scan|`dynamicsecurityscan`|IBM Application Security on Cloud|\n|Custom Data Sets - Tests|Custom Tag*|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Custom Data Sets - Code Coverage|Custom Tag*|Cobertura (xml), lcov, Istanbul, JaCoCo|\n\nFor golang [gocov](https://github.com/axw/gocov/) users, please convert to Cobertura using [gocov XML(Cobertura) export](https://github.com/yaoyaozong/gocov-xml)\n\n\\* For custom tags create a quality data set by using the user interface. Navigate to your toolchain, click on DevOps Insights card. Navigate to quality dashboard. Click on the Kebab menu which is to the top-right of the quality dashboard. Click on **Configure Quality Data Sets**\n\n### Upload SonarQube Results\nTo upload data from SonarQube, you must provide the SonarQube server token using `--token`. Your SonarQube server is not required to be accessible from your CI/CD tool.\n\nAfter you run a scan using SonarQube, you can upload SonarQube results by running this command.\n\n```\nidra --publishtestresult --filelocation=.scannerwork/report-task.txt --type=sonarqube --token=234234434\n```\n\nIn the above command, report-task.txt is a file generated during the SonarQube scan.\n\nIf this command fails for some reason, you can enable logs by setting IDRA_DEBUG environment variable to true.\n\nIf you are using self-signed certificates for SonarQube server, you will need to set `export NODE_TLS_REJECT_UNAUTHORIZED=0`\n\n## Upload Deployment Records\nUse the `--publishdeployrecord` command (alias `-d`) to upload deployment records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishdeployrecord --env= --status= [--joburl=] [--appurl=] [--deployableid=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--env`|`-E` | **Required.** The environment where the pipeline job deployed the app. |\n|`--status`|`-S` | **Required.** The deployment status. This value must be either `pass` or `fail`. |\n|`--joburl`|`-J` | _Optional_. The URL to the job's deployment logs. |\n|`--appurl`|`-A` | _Optional._ The URL where the deployed app is running. |\n|`--deployableid`| `-I` | _Optional._ The deployed app's application ID. You can get the ID by running the Cloud Foundry CLI's `cf env` command. The application ID is listed under `VCAP_APPLICATION`. |\n\n### An example command\n\nIn this an example, the command uploads a deployment record from a pipeline job. The deployment is to the \"staging\" environment. The deployment is successful and the app is running at a specified URL.\n\n```shell\nidra --publishdeployrecord --env=\"staging\" --status=pass --appurl=\"https://app.staging.example.com\"\n```\n\n## Making decisions about build quality using gate policies\n\nTo use this feature, create a quality policy by using the user interface. Navigate to your toolchain, click on **DevOps Insights** card. Then on the left menu, click on **Policies**.\n\nUse the `--evaluategate` command (alias `-g`) to request a gate decision for a DevOps Insights policy in your pipeline. If the policy is satisfied, the pipeline continues running. If not, and you use the `--forcedecision` flag, the pipeline stops running.\n\n### Command syntax and options\n\n```shell\nidra --evaluategate --policy= [--forcedecision] [--type=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--policy`|`-P` | **Required.** The name of the policy that the gate uses to make its decision. |\n|`--forcedecision`|`-D` | _Optional._ Set the value to `true` to cause the process to exit with an error code, if the policy evaluation fails. The value defaults to `false` if this option is not specified. |\n|`--type`|`-E` | _Optional_. A rule type to consider. If you include this option, only rules of this type are considered in the decision-making process. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, and `sonarqube` for SonarQube scans. |\n\n\n\n## Release History\n_(Nothing yet)_\n","readmeFilename":"README.md","_id":"grunt-idra3@0.1.34","_shasum":"0017f7bbde894fce767897dfbbb329eea627f77a","_from":".","_npmVersion":"3.10.3","_nodeVersion":"6.7.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"0017f7bbde894fce767897dfbbb329eea627f77a","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.34.tgz","integrity":"sha512-blJJxgyzeNewV5AvtI1MaeuAGEHgtoPVwNQFxaMvi/XpNAmNzzdgpF6v8097kJ6UNOeHAUwNtiBbTP+YSlAsLw==","fileCount":48,"unpackedSize":165237,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbrPuBCRA9TVsSAnZWagAAhLkQAJsGQitDgp0VAgw0UAqq\nW2pkIm94l7eUDnqrA+ByNcpImiDhK8oiBB8bGIQCJkNOXL/LqHo/oVRqbh/Q\ncfe6JEiSU5iRfG0X0xzgv9+s4X1eBObttwNiH7xk1o2Uke7aWLMkdZoC7WxN\ns+f6A422WhEse42MvQkRDdDmnYOOByi7R1hRhbKhYT4XOKIcFRiRNSaAKAqc\nu6OZkDEd5YY5HTOIWSrBNwWHo8DumTQNQc+EwXb+oW0hk5idi3V5WTU1+nwk\nVu9fsBc7SpEh5bugZ9Dl5nSRcFZhHy5WBhv8X5/O2A5rhWYbKvMuQEgoijVt\n3cGvx5eBLJdcjdvpXApMbtqmtQpFhecIDiKBnzV194Dt2qUWPs1RggKBmCQ0\n7W3DurM9s/Rm4/ihOwu6YbAwznMs7yNJVkVX7HPumRLzEeLcmbv5aBmYf3ZP\nYYfTY0TDQYCtvN3WHKNQi0fQIB55CEDfmmEppi4QZC1BkvK9tdHd538weMny\nMIY8IcT4JDql8N5kq7tSs0ETXKhKamhloR/NPv2xdsA5Ubab7Gwtv4wiXnG3\n8z1LIKznL3FXuolF4f9QcMs16bTXXGaHIr6NknodrFAsNbM4c4qsEtSB5Eyj\nIiYZYqu2gclHmp36ZAWG78rk+C++Dd+4zZfM9J3xvONc0Fer6BpGnVLltQxM\nuQZV\r\n=e1T1\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCH9803VwdA1pce8ZA/zVqKT3Whhw6mRP8oVxSPX3jpyAIgQAfeRuyw66epDvfZph5pe9mbWxXc+i2XJKP25qY21qw="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.34_1538063232489_0.9221813718650484"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.35":{"name":"grunt-idra3","version":"0.1.35","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.3","grunt-contrib-clean":"^1.0.0","grunt-eslint":"^21.0.0","grunt-mocha-test":"^0.12.7","mocha":"^5.2.0","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","inquirer":"^3.0.0","mime":"^1.4.1","request":"^2.87.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.16"},"_id":"grunt-idra3@0.1.35","_shasum":"5bab9c586ecaea897931b292c83d15d28a6c2fa1","_from":".","_npmVersion":"3.10.3","_nodeVersion":"6.7.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"5bab9c586ecaea897931b292c83d15d28a6c2fa1","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.35.tgz","integrity":"sha512-XVbLJm94ci+d5GYbvlDq4fHM7BlnVoq5io09gTRDTPWYCn5k0F++EZkR0ZWGOSJBMNypj6w6QxBWHQTAuSG3Fw==","fileCount":48,"unpackedSize":165211,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJbrP5kCRA9TVsSAnZWagAAlRAP/02h8ufhgeWlBPIJF7iR\n8oa4+NraSKzzqwdHdt50AtOxjD7eLZqMALG194aSrIkk3cz/vcNovEeIusRm\nuPcTmGWlJIDm6dArpind416t4EM2D2yqb7IQkPAFOTKBZkpCPggdxtNjBKDH\ns3q1I7AqHd340Bte1MpGON28UOdfFgFXZOsPHJOnrgyB3tHcXUL4eNeAIFDF\n+qsrT3wQHdaOi7dVT2PJYBgt2SqM3USj8zLXDc6l94NWtgv/D/1I5Gx4MfVj\nptP07iLbDoLCCHPhH4niMYuDRBH5tlkz4UrzGJaAPcUuKrwsIFIyrKPugQc+\nXoJEqOCE2uGUQUdZP1td2ukOL+4rlH1fhRYRG2LGV97sNfAjgZmQqK5EgGV6\nQwd5T46L3vlo75LRk2IjtRKCzrwP3mKDUBCbrXnTEeF52ppP2smEqna6mEKF\nj2HGRihL8p0STq+cwZnAhv09JZdLQ18+5sXY4sJ5QihCUHQCh6XcMFYSA9go\nlc3A5MlLCfHO8FMPNwQLjyE9wy/CPsyxJfBL7SXPLNOt7kuixBTCdvw5o+lj\n+HuiSY4bdOwEk5r4EXcvJBJ53kqe9hHRqgHNRd3Z6qhf5K9nkD7WTrYPhNvt\nYkcexivSEHr4s+rvYDUQ0ATGWuH7fH7++cqNghuAfF+KL3nvEz0zIDx6M59H\nz00g\r\n=TRML\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCICNhN+BEQjLfzP71yAqQrZvYn+v/y1Ey3k1Fs6yisdZEAiB2y3yb74VgRNlFo+3c/UtOSf7zJWs50dK8SqAA0apz0A=="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.35_1538063972175_0.8288564234038969"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.36":{"name":"grunt-idra3","version":"0.1.36","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.3","grunt-contrib-clean":"^1.0.0","grunt-eslint":"^21.0.0","grunt-mocha-test":"^0.12.7","mocha":"^5.2.0","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","inquirer":"^3.0.0","mime":"^1.4.1","request":"^2.87.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.19"},"readme":"# idra\n\n> Command Line utility for integrating with IBM® DevOps Insights\n\nTo install this utility\n```\nnpm install -g grunt-idra3\n```\n\n# Table of Contents\n1. [Concepts](#concepts)\n2. [Getting Started](#getting-started)\n 1. [Scenarios](#scenarios)\n 2. [Prerequisites](#prerequisites)\n 3. [Environment Variables](#environment-variables)\n 4. [Enabling Debug Logs](#enabling-debug-logs)\n 5. [Using the CLI](#using-the-cli)\n3. [Upload Build Records](#upload-build-records)\n4. [Upload Test Results](#upload-test-results)\n 1. [Upload SonarQube Results](#upload-sonarqube-results)\n5. [Upload Deployment Records](#upload-deployment-records)\n6. [Making decisions about build quality using gate policies](#making-decisions-about-build-quality-using-gate-policies)\n\n## Concepts\nIBM® DevOps Insights is a tool that provides insights into your DevOps projects. Use it to learn how compliant your team is with DevOps and developer practices, to manage risk in your codebase, and to automatically enforce quality standards in continuous delivery projects.\n\nUnderstanding of the following concepts will help in faster adoption of IBM® DevOps Insights for your projects.\n\n##### Toolchain\nToolchains are part of [IBM® DevOps Continuous Delivery](https://console.bluemix.net/docs/services/ContinuousDelivery/cd_overview.html#cd_overview). Toolchains provide an integrated set of tools to build, deploy and manage your apps. You can create toolchains that include IBM Cloud services, open source tools, and third party tools that make development and operations repeatable and easier to manage. It is required that the IBM DevOps Insights should be added as one of the tool to your toolchain.\n\n##### Integrating your build tool with IBM DevOps Insights\nThis means instrumenting your build tool with this CLI or DevOps Insights Jenkins plugin to send build, test and deployment records to IBM DevOps Insights.\n\n##### Build record\nIBM DevOps Insights needs to know when a build is complete. This record contains application name, branch, build id, reference to git repo and other fields. This CLI and Jenkins plugin has a command to publish the build record to DevOps Insights.\n\n##### Test record\nIBM DevOps Insights needs to know about the tests performed during the build process. It is necessary that the tests should generate some kind of JSON or XML based file. Here are the list of supported [format](supported-test-formats). The generated test file is published as a test record. Along with the test file this record contains application name, build id, type of tests and other fields. It is required that the application name and build id in the test record matches the one used in the build record for a given build. This CLI and Jenkins plugin has a command to publish test record to DevOps Insights.\n\n##### Deployment records\nIBM DevOps Insights needs to know about the deployments made during the deployment process. This record contains the application name, build id, environment name, status of the deployment and other fields. It is required that the application name and build id in the deployment record matches the one used in the build record for a given build. This CLI and Jenkins plugin has a command to publish a deployment to DevOps Insights.\n\n##### Build Id (or Number)\nThis is an arbitrary length string uniquely identifying each build. This id is used to tie the build, test and deployment records together so it is important to publish those records with the same id for a given build.\n\n##### Policy\nA policy is set of rules specified by the user that collectively defines what is considered a good set of test records for a given application build. Typically, one rule is added for each test record published to DevOps Insights. The policy rules are evaluated by the gate.\n\n##### Branch\nThis is the name of the branch in the source control system.\n\n##### Environment\nThis is the name of environment to which deployments are made during the build process.\n\n##### Data set\nThis is an arbitrary string that identifies the type of tests performed during the build process. Besides the standard names such as \"unit test\", \"fvt\". The tool allows the user to define a custom name.\n\n## Getting Started\n\nUse this utility to integrate IBM® DevOps Insights with Travis CI, Concourse, IBM Urban Code Deploy, IBM Continuous Delivery Pipelines and other CI/CD tools. If you are using Jenkins, use this [Jenkins plugin](https://plugins.jenkins.io/ibm-cloud-devops) instead.\n\nUsing this utility, you can\n - Publish build records, test records and deploy records to IBM® DevOps Insights \n - Make go/no-go decisions about a build's quality by using a Gate policy\n\nFor samples of dashboards in IBM® DevOps Insights, see [Value Proposition](https://plugins.jenkins.io/ibm-cloud-devops).\n\nFor more information about IBM DevOps Insights, see [the official documentation](https://console.bluemix.net/docs/services/DevOpsInsights/index.html).\n\n### Scenarios\nThis document covers two scenarios:\n1. You are integrating DevOps Insights with IBM Continuous Delivery tool.\n2. You are integrating DevOps Insights with other CI/CD tools (e.g., Travis CI, Concourse, IBM Urban Code Deploy, others)\n\n### Prerequisites\n\nTo use the CLI, you need to do the following. These steps should take about 10 minutes.\n\n1. A valid IBM Cloud account. If you don't have one, [register here](https://console.bluemix.net/registration).\n\n2. Once you have an account, you can create an API Key. Log in to [IBM Cloud](https://console.bluemix.net). Click on **Manage**->**Security**->**Platform API Key**. On that screen, create an API Key.\n\n3. An IBM Continuous Delivery toolchain. To create a toolchain:\n - Go to https://console.bluemix.net/devops\n - Click on **Create a Toolchain** button and then select **Build Your Own Toolchain** template. \n - In the next screen, click **Create**.\n - From the URL displayed in the browser, make note of your toolchain id. For example, if your URL is https://console.bluemix.net/devops/toolchains/05572df3-01dc-441b-911d-b2202fe33f96, the toolchain id is the long string after **toolchains/**\n - You can always navigate to your toolchain by [clicking here](https://console.bluemix.net/devops)\n\n4. Add DevOps Insights tool to your toolchain\n - Go to your toolchain\n - Click on **Add a Tool** button\n - Select DevOps Insights tool and click **Create Integration** button\n\n5. Your CI/CD tool must have Node.js® 4.x or greater.\n\n### Environment Variables\n\nIf you are using Travis, Concourse or any CI/CD tool other than the IBM Continuous Delivery pipeline, then set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|TOOLCHAIN_ID| **Required.** The toolchain's GUID |\n|IBM_CLOUD_API_KEY| **Required.** The Bluemix user's Api key|\n|BUILD_NUMBER| **Required.** Any string that identifies the build |\n|LOGICAL_APP_NAME| **Required.** The application's name.|\n\nIf you are using IBM Continuous Delivery pipeline, you need to set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|IBM_CLOUD_API_KEY| **Required** The Bluemix user's Api key|\n|BUILD_PREFIX| **Required.** Any string. For example, the Git branch name. |\n|LOGICAL_APP_NAME| **Required.** The application's name.|\n|PATH|**Required.** In order to have required version of Node.js in your path, set the PATH variable before invoking the utility: `export PATH=/opt/IBM/node-v4.2/bin:$PATH`|\n\nIf you are using IBM Continuous Delivery pipeline and if you want to publish Insights data to another toolchain, then set the following environment variables. \n\n|Name|Description|\n|-----|-----|\n|TOOLCHAIN_ID| **Required.** The target toolchain's GUID. If the target toolchain is owned by different user then provide the target toolchain owner's Bluemix Api key in the `IBM_CLOUD_API_KEY` variable.|\n\n\nIf you are using IBM UrbanCode Deploy, DevOps Insights relies on the previous set of variables, and this one:\n\n|Name|Description|\n|-----|-----|\n|UCD_REQUEST_ID| This maps to the ${p:request.id} property value. |\n\n### Enabling Debug logs\nIf you want to enable debug logs for the DevOps Insights CLI, set the `IDRA_DEBUG` environment variable to `true`. This works in all environments.\n\n|Name|Description|\n|-----|-----|\n|IDRA_DEBUG| When this value is `true`, the DevOps Insights CLI's debugging mode is enabled. By default, the value is `false`. |\n\n\n### Using the CLI\n\nSet [environment details](#environment-details) as described above. Ensure that Node.js 4.2 or higher is avaialble in your CI/CD tool.\n\nTo install this utility, use `npm install -g grunt-idra3`\n\nThen you can invoke the CLI with the `idra` command. You can run the CLI in any pipeline job's command script. For example, this command uploads functional verification test results to DevOps Insights:\n\n```\n# Upload test results\nidra --publishtestresult --filelocation=\"results.json\" --type=fvt\n```\n\n\n## Upload Build Records\nUse the `--publishbuildrecord` command (alias `-b`) to upload build records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishbuildrecord --branch= --repositoryurl= --commitid= --status= [--joburl=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--branch`|`-B` | **Required.** The repository branch on which the build is being performed. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--repositoryurl`|`-R` | **Required.** The url of the git repository. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--commitid`|`-C` | **Required.** The git commit id. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--status`|`-S` | **Required.** The build status. This value must be either `pass` or `fail`. |\n|`--joburl`|`-J` | _Optional_. The URL to the job's build logs. |\n\n\n### An example command\n\nIn this an example, the command uploads a build record from a pipeline job.\n\n```shell\nidra --publishbuildrecord --branch=master --repositoryurl=\"https://github.com/oic/dlms.git\" --commitid=dff7884b9168168d91cb9e5aec78e93db0fa80d9 --status=pass\n```\n\n## Upload Test Results\n\nUse the `--publishtestresult` command (alias `-p`) to upload results from these test types to DevOps Insights:\n\n* Unit tests\n* Code coverage tests\n* Functional verification tests (FVT)\n* Static security scans from IBM Application Security on Cloud\n* Dynamic app scans from IBM Application Security on Cloud\n* [SonarQube results](#upload-sonarqube-results)\n\n\n### Command syntax and options\n\n```shell\nidra --publishtestresult --filelocation= --type= [--drilldownurl=] [--env=] [--token=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--filelocation`| `-F` |**Required.** The location of the test results that you want to upload. This can be a single file, an entire directory, or multiple files that match a wildcard expression.|\n|`--type`| `-T` |**Required.** The type of test results that you want to upload. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, and `sonarqube` for SonarQube scans. In addition to these types you can also use a custom quality data set tag to upload test results of different type.|\n|`--drilldownurl`| `-U` |_Optional._ A URL where more information about the test results can be found. If this URL is invalid, the option is ignored. |\n|`--env`| `-E` |_Optional._ The environment name to associate with the test results. This option is ignored for unit tests, code coverage tests, and static security scans. |\n|`--token`| `-K` |_Optional_. This is a SonarQube token. This flag is valid only if the type specified is `sonarqube`. It is used by the CLI to pull additional information from the SonarQube server. |\n\n### An example command\n\nIn this example, the command uploads all JSON-formatted FVT results from a directory to DevOps Insights. Additionally, a test tool is declared, a test result URL is given, and a logical staging environment is provided. Specifying an environment is especially important when you want your results to be analyzed alongside other activities that take place in that same environment.\n\n```shell\nidra --publishtestresult --filelocation=\"tests/fvt/*.json\" --type=fvt -drilldownurl=\"https://example.com/testinfo\" --env=\"staging\"\n```\n\n### Supported Test Formats\n|Type of Test|tag|Supported Formats|\n|-----|-----|-----|\n|Unit Test|`unittest`|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Test Case|`fvt`|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Code Coverage|`code`|Cobertura (xml), lcov, Istanbul, JaCoCo|\n|SonarQube|`sonarqube`|SonarQube|\n|Static Security Scan|`staticsecurityscan`|IBM Application Security on Cloud|\n|Dynamic Security Scan|`dynamicsecurityscan`|IBM Application Security on Cloud|\n|Custom Data Sets - Tests|Custom Tag*|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Custom Data Sets - Code Coverage|Custom Tag*|Cobertura (xml), lcov, Istanbul, JaCoCo|\n\nFor golang [gocov](https://github.com/axw/gocov/) users, please convert to Cobertura using [gocov XML(Cobertura) export](https://github.com/yaoyaozong/gocov-xml)\n\n\\* For custom tags create a quality data set by using the user interface. Navigate to your toolchain, click on DevOps Insights card. Navigate to quality dashboard. Click on the Kebab menu which is to the top-right of the quality dashboard. Click on **Configure Quality Data Sets**\n\n### Upload SonarQube Results\nTo upload data from SonarQube, you must provide the SonarQube server token using `--token`. Your SonarQube server is not required to be accessible from your CI/CD tool.\n\nAfter you run a scan using SonarQube, you can upload SonarQube results by running this command.\n\n```\nidra --publishtestresult --filelocation=.scannerwork/report-task.txt --type=sonarqube --token=234234434\n```\n\nIn the above command, report-task.txt is a file generated during the SonarQube scan.\n\nIf this command fails for some reason, you can enable logs by setting IDRA_DEBUG environment variable to true.\n\nIf you are using self-signed certificates for SonarQube server, you will need to set `export NODE_TLS_REJECT_UNAUTHORIZED=0`\n\n## Upload Deployment Records\nUse the `--publishdeployrecord` command (alias `-d`) to upload deployment records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishdeployrecord --env= --status= [--joburl=] [--appurl=] [--deployableid=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--env`|`-E` | **Required.** The environment where the pipeline job deployed the app. |\n|`--status`|`-S` | **Required.** The deployment status. This value must be either `pass` or `fail`. |\n|`--joburl`|`-J` | _Optional_. The URL to the job's deployment logs. |\n|`--appurl`|`-A` | _Optional._ The URL where the deployed app is running. |\n|`--deployableid`| `-I` | _Optional._ The deployed app's application ID. You can get the ID by running the Cloud Foundry CLI's `cf env` command. The application ID is listed under `VCAP_APPLICATION`. |\n\n### An example command\n\nIn this an example, the command uploads a deployment record from a pipeline job. The deployment is to the \"staging\" environment. The deployment is successful and the app is running at a specified URL.\n\n```shell\nidra --publishdeployrecord --env=\"staging\" --status=pass --appurl=\"https://app.staging.example.com\"\n```\n\n## Making decisions about build quality using gate policies\n\nTo use this feature, create a quality policy by using the user interface. Navigate to your toolchain, click on **DevOps Insights** card. Then on the left menu, click on **Policies**.\n\nUse the `--evaluategate` command (alias `-g`) to request a gate decision for a DevOps Insights policy in your pipeline. If the policy is satisfied, the pipeline continues running. If not, and you use the `--forcedecision` flag, the pipeline stops running.\n\n### Command syntax and options\n\n```shell\nidra --evaluategate --policy= [--forcedecision] [--type=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--policy`|`-P` | **Required.** The name of the policy that the gate uses to make its decision. |\n|`--forcedecision`|`-D` | _Optional._ Set the value to `true` to cause the process to exit with an error code, if the policy evaluation fails. The value defaults to `false` if this option is not specified. |\n|`--type`|`-E` | _Optional_. A rule type to consider. If you include this option, only rules of this type are considered in the decision-making process. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, and `sonarqube` for SonarQube scans. |\n\n\n\n## Release History\n_(Nothing yet)_\n","readmeFilename":"README.md","_id":"grunt-idra3@0.1.36","_shasum":"d8161197ee84844ce84217a37a14e684d143cd47","_from":".","_npmVersion":"3.10.3","_nodeVersion":"6.7.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"d8161197ee84844ce84217a37a14e684d143cd47","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.36.tgz","integrity":"sha512-LeM5rzWUBe/Ipl6zcqKzBDhm4mm3GKW9Ulm3nnP4rS7SVJmhxhjuqRGJZo8w1F5PwokpG89vDQgzDVJD0PC7kg==","fileCount":48,"unpackedSize":165620,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJb1NRqCRA9TVsSAnZWagAAfisP/RY3SdyY00Y3Chxk41nK\n6aosuI/F+BPViQvhVs63wPd3FteFZADH9+KsCAf8kK0DqYlpx3xkXLCVyZF2\nTR8YPTOlS3veEfMVfGKQP6lDI0XUhhkcjkAVKKkLqROQ6YbY16GYRm7KfI2p\nyMe+L7FAOzpWFqad4OEao3FTYe07OpqcYQ/jw11/HNN6It1tkXDCcmuVx7Ra\nLFel03BMWJsckNf7iomhkfatM2cURGBLH6i2ztLr5O9xGSBpDNMkbKAGDauK\n9LdGxpCxu1bjDPQV0XjDFC5Tb4E8Xmhk4HjDFLjn6VhjV+FgAr4m+eZpMIw8\nIuQa6vrS7gLxzRUor2StDoRZTxM9Vc7AsQDScLuVbSqZa22RjkPyqoJRaOjq\nAXrVmG5PjNKUiZvXsRmTgayDdQXTpaduXJl12d9q6oYLs+/ys7W8m3jvEaKY\n712bh1auT/njGCGcI37RkdATsnLb8tWdGC+aB2r+yydEpcz189v1ZVe9lpQA\nuymo0oIIsoKgaf91o8juwQixcG5pOG3QHSZyKwndP5qE5oWyFqq/CR99dj9b\nw7jQBEZ2mZRbtrk2VndYNnoVOk+OvPMnvA75edi3Htw8ej/wP8P8VIaMMWaP\nA0mc2sHp4ia3tPCfiJJbfTRpfLPipfsQqgZfv8rmnGvoZATf0rUbATzYpMOJ\nAPXx\r\n=ULVn\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDfOb5Nj0A5POSdAYuwlk8WH1fFg24/XcQwQ3OQCpES8wIhAKxBsi33p/heC4oJDAZR+v/ZkjXBuhV9I3SnjB17RYBc"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.36_1540674665036_0.9677336836377346"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.37":{"name":"grunt-idra3","version":"0.1.37","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.3","grunt-contrib-clean":"^1.0.0","grunt-eslint":"^21.0.0","grunt-mocha-test":"^0.12.7","mocha":"^5.2.0","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","inquirer":"^3.0.0","mime":"^1.4.1","request":"^2.87.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.19"},"_id":"grunt-idra3@0.1.37","_shasum":"cab439b2bdf54304029154b4ca78948254bbd08b","_from":".","_npmVersion":"3.10.3","_nodeVersion":"6.7.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"cab439b2bdf54304029154b4ca78948254bbd08b","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.37.tgz","integrity":"sha512-qN6j8TurHZ7ucCZTg/1D9/BlxbLExVjL7NsTYb1tYuWgxOe0Di0L6nv5D6ycUosjCpWw2eTHQbjW/qczSd9+jg==","fileCount":48,"unpackedSize":165573,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJb1NolCRA9TVsSAnZWagAA10IP/23h+4YlzHKZ3d6CyiCX\nxAIAPk4y4Xfz6MHzYSK68J/vSFFEd/L39ybR9+HJ5hZTtEaVeeQndH+D3Hl4\n8aPAaavfstF3BSp4SpbpL/z3YnwMX1Nk+ZBoe6PiLT6gQldm8biCZ1GJrcUG\nzS7MtS5QV2Ubw37PNiNChe5nPv8YdQEbzLGEJXbIE22IfQ3gxXiDpaeszEY4\nQ8X9RGNvBBjrwsKv2Vqc3FPP8SLA1s4TNn9vMLSZC6P6iuZBDEtgqz76gccx\neInuMmucM9CBtasqgBs4LuGCFfCbkLj4PILZN/WSJ+4HPbp4kpNyPTRTIBw5\nvQqrTGMSNoIRMBm+Sgc8uhVdQZ2NIS2fiK85PI9K9WkHBNuQiA+I4kMmXp1V\n4lgxMqjk5afUcgrj5tTM6tLSP2occnnYWMgtW+zVnJoR7QioqySiKKUkwqQr\n3kDy6ibLAQwnzSkvnGmANEFwVvBHGSze5Q5hqfgd4qRxd2OiNIxuFroOLc86\nI3PyQQrYJV9ywKAoszBojoksTQzSzIdmAKdFtASExplh7PElN+PTSuE1llhq\nluPD2QxKKFcIis0efRdINKgICptl7EJ9SvH6Ubs6jXlh73nI2okj6tm1R3QN\npWeQJCPR9T5HRMlR793PzMFHaWUCgZtTnqfms1g5Hsm7pdw0dZ+fNIqNduBP\nwf5M\r\n=s/7Q\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIDv5fvoscYOrz1k7dXoij77c417uqv3KuZFqfCID5IgsAiEA7kLDsluQZOJbwxakqc9yuy2bUdYjjpmBgNGQTlUlA3g="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.37_1540676132694_0.7551125792335569"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.38":{"name":"grunt-idra3","version":"0.1.38","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.3","grunt-contrib-clean":"^1.0.0","grunt-eslint":"^21.0.0","grunt-mocha-test":"^0.12.7","mocha":"^5.2.0","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","inquirer":"^3.0.0","mime":"^1.4.1","request":"^2.87.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.19"},"readme":"# idra\n\n> Command Line utility for integrating with IBM® DevOps Insights\n\nTo install this utility\n```\nnpm install -g grunt-idra3\n```\n\n# Table of Contents\n1. [Concepts](#concepts)\n2. [Getting Started](#getting-started)\n 1. [Scenarios](#scenarios)\n 2. [Prerequisites](#prerequisites)\n 3. [Environment Variables](#environment-variables)\n 4. [Enabling Debug Logs](#enabling-debug-logs)\n 5. [Using the CLI](#using-the-cli)\n3. [Upload Build Records](#upload-build-records)\n4. [Upload Test Results](#upload-test-results)\n 1. [Upload SonarQube Results](#upload-sonarqube-results)\n5. [Upload Deployment Records](#upload-deployment-records)\n6. [Making decisions about build quality using gate policies](#making-decisions-about-build-quality-using-gate-policies)\n\n## Concepts\nIBM® DevOps Insights is a tool that provides insights into your DevOps projects. Use it to learn how compliant your team is with DevOps and developer practices, to manage risk in your codebase, and to automatically enforce quality standards in continuous delivery projects.\n\nUnderstanding of the following concepts will help in faster adoption of IBM® DevOps Insights for your projects.\n\n##### Toolchain\nToolchains are part of [IBM® DevOps Continuous Delivery](https://console.bluemix.net/docs/services/ContinuousDelivery/cd_overview.html#cd_overview). Toolchains provide an integrated set of tools to build, deploy and manage your apps. You can create toolchains that include IBM Cloud services, open source tools, and third party tools that make development and operations repeatable and easier to manage. It is required that the IBM DevOps Insights should be added as one of the tool to your toolchain.\n\n##### Integrating your build tool with IBM DevOps Insights\nThis means instrumenting your build tool with this CLI or DevOps Insights Jenkins plugin to send build, test and deployment records to IBM DevOps Insights.\n\n##### Build record\nIBM DevOps Insights needs to know when a build is complete. This record contains application name, branch, build id, reference to git repo and other fields. This CLI and Jenkins plugin has a command to publish the build record to DevOps Insights.\n\n##### Test record\nIBM DevOps Insights needs to know about the tests performed during the build process. It is necessary that the tests should generate some kind of JSON or XML based file. Here are the list of supported [format](supported-test-formats). The generated test file is published as a test record. Along with the test file this record contains application name, build id, type of tests and other fields. It is required that the application name and build id in the test record matches the one used in the build record for a given build. This CLI and Jenkins plugin has a command to publish test record to DevOps Insights.\n\n##### Deployment records\nIBM DevOps Insights needs to know about the deployments made during the deployment process. This record contains the application name, build id, environment name, status of the deployment and other fields. It is required that the application name and build id in the deployment record matches the one used in the build record for a given build. This CLI and Jenkins plugin has a command to publish a deployment to DevOps Insights.\n\n##### Build Id (or Number)\nThis is an arbitrary length string uniquely identifying each build. This id is used to tie the build, test and deployment records together so it is important to publish those records with the same id for a given build.\n\n##### Policy\nA policy is set of rules specified by the user that collectively defines what is considered a good set of test records for a given application build. Typically, one rule is added for each test record published to DevOps Insights. The policy rules are evaluated by the gate.\n\n##### Branch\nThis is the name of the branch in the source control system.\n\n##### Environment\nThis is the name of environment to which deployments are made during the build process.\n\n##### Data set\nThis is an arbitrary string that identifies the type of tests performed during the build process. Besides the standard names such as \"unit test\", \"fvt\". The tool allows the user to define a custom name.\n\n## Getting Started\n\nUse this utility to integrate IBM® DevOps Insights with Travis CI, Concourse, IBM Urban Code Deploy, IBM Continuous Delivery Pipelines and other CI/CD tools. If you are using Jenkins, use this [Jenkins plugin](https://plugins.jenkins.io/ibm-cloud-devops) instead.\n\nUsing this utility, you can\n - Publish build records, test records and deploy records to IBM® DevOps Insights \n - Make go/no-go decisions about a build's quality by using a Gate policy\n\nFor samples of dashboards in IBM® DevOps Insights, see [Value Proposition](https://plugins.jenkins.io/ibm-cloud-devops).\n\nFor more information about IBM DevOps Insights, see [the official documentation](https://console.bluemix.net/docs/services/DevOpsInsights/index.html).\n\n### Scenarios\nThis document covers two scenarios:\n1. You are integrating DevOps Insights with IBM Continuous Delivery tool.\n2. You are integrating DevOps Insights with other CI/CD tools (e.g., Travis CI, Concourse, IBM Urban Code Deploy, others)\n\n### Prerequisites\n\nTo use the CLI, you need to do the following. These steps should take about 10 minutes.\n\n1. A valid IBM Cloud account. If you don't have one, [register here](https://console.bluemix.net/registration).\n\n2. Once you have an account, you can create an API Key. Log in to [IBM Cloud](https://console.bluemix.net). Click on **Manage**->**Security**->**Platform API Key**. On that screen, create an API Key.\n\n3. An IBM Continuous Delivery toolchain. To create a toolchain:\n - Go to https://console.bluemix.net/devops\n - Click on **Create a Toolchain** button and then select **Build Your Own Toolchain** template. \n - In the next screen, click **Create**.\n - From the URL displayed in the browser, make note of your toolchain id. For example, if your URL is https://console.bluemix.net/devops/toolchains/05572df3-01dc-441b-911d-b2202fe33f96, the toolchain id is the long string after **toolchains/**\n - You can always navigate to your toolchain by [clicking here](https://console.bluemix.net/devops)\n\n4. Add DevOps Insights tool to your toolchain\n - Go to your toolchain\n - Click on **Add a Tool** button\n - Select DevOps Insights tool and click **Create Integration** button\n\n5. Your CI/CD tool must have Node.js® 4.x or greater.\n\n### Environment Variables\n\nIf you are using Travis, Concourse or any CI/CD tool other than the IBM Continuous Delivery pipeline, then set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|TOOLCHAIN_ID| **Required.** The toolchain's GUID |\n|IBM_CLOUD_API_KEY| **Required.** The Bluemix user's Api key|\n|BUILD_NUMBER| **Required.** Any string that identifies the build |\n|LOGICAL_APP_NAME| **Required.** The application's name.|\n\nIf you are using IBM Continuous Delivery pipeline, you need to set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|IBM_CLOUD_API_KEY| **Required** The Bluemix user's Api key|\n|BUILD_PREFIX| **Required.** Any string. For example, the Git branch name. |\n|LOGICAL_APP_NAME| **Required.** The application's name.|\n|PATH|**Required.** In order to have required version of Node.js in your path, set the PATH variable before invoking the utility: `export PATH=/opt/IBM/node-v4.2/bin:$PATH`|\n\nIf you are using IBM Continuous Delivery pipeline and if you want to publish Insights data to another toolchain, then set the following environment variables. \n\n|Name|Description|\n|-----|-----|\n|TOOLCHAIN_ID| **Required.** The target toolchain's GUID. If the target toolchain is owned by different user then provide the target toolchain owner's Bluemix Api key in the `IBM_CLOUD_API_KEY` variable.|\n\n\nIf you are using IBM UrbanCode Deploy, DevOps Insights relies on the previous set of variables, and this one:\n\n|Name|Description|\n|-----|-----|\n|UCD_REQUEST_ID| This maps to the ${p:request.id} property value. |\n\n### Enabling Debug logs\nIf you want to enable debug logs for the DevOps Insights CLI, set the `IDRA_DEBUG` environment variable to `true`. This works in all environments.\n\n|Name|Description|\n|-----|-----|\n|IDRA_DEBUG| When this value is `true`, the DevOps Insights CLI's debugging mode is enabled. By default, the value is `false`. |\n\n\n### Using the CLI\n\nSet [environment details](#environment-details) as described above. Ensure that Node.js 4.2 or higher is avaialble in your CI/CD tool.\n\nTo install this utility, use `npm install -g grunt-idra3`\n\nThen you can invoke the CLI with the `idra` command. You can run the CLI in any pipeline job's command script. For example, this command uploads functional verification test results to DevOps Insights:\n\n```\n# Upload test results\nidra --publishtestresult --filelocation=\"results.json\" --type=fvt\n```\n\n\n## Upload Build Records\nUse the `--publishbuildrecord` command (alias `-b`) to upload build records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishbuildrecord --branch= --repositoryurl= --commitid= --status= [--joburl=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--branch`|`-B` | **Required.** The repository branch on which the build is being performed. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--repositoryurl`|`-R` | **Required.** The url of the git repository. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--commitid`|`-C` | **Required.** The git commit id. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--status`|`-S` | **Required.** The build status. This value must be either `pass` or `fail`. |\n|`--joburl`|`-J` | _Optional_. The URL to the job's build logs. |\n\n\n### An example command\n\nIn this an example, the command uploads a build record from a pipeline job.\n\n```shell\nidra --publishbuildrecord --branch=master --repositoryurl=\"https://github.com/oic/dlms.git\" --commitid=dff7884b9168168d91cb9e5aec78e93db0fa80d9 --status=pass\n```\n\n## Upload Test Results\n\nUse the `--publishtestresult` command (alias `-p`) to upload results from these test types to DevOps Insights:\n\n* Unit tests\n* Code coverage tests\n* Functional verification tests (FVT)\n* Static security scans from IBM Application Security on Cloud\n* Dynamic app scans from IBM Application Security on Cloud\n* [SonarQube results](#upload-sonarqube-results)\n\n\n### Command syntax and options\n\n```shell\nidra --publishtestresult --filelocation= --type= [--drilldownurl=] [--env=] [--token=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--filelocation`| `-F` |**Required.** The location of the test results that you want to upload. This can be a single file, an entire directory, or multiple files that match a wildcard expression.|\n|`--type`| `-T` |**Required.** The type of test results that you want to upload. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, and `sonarqube` for SonarQube scans. In addition to these types you can also use a custom quality data set tag to upload test results of different type.|\n|`--drilldownurl`| `-U` |_Optional._ A URL where more information about the test results can be found. If this URL is invalid, the option is ignored. |\n|`--env`| `-E` |_Optional._ The environment name to associate with the test results. This option is ignored for unit tests, code coverage tests, and static security scans. |\n|`--token`| `-K` |_Optional_. This is a SonarQube token. This flag is valid only if the type specified is `sonarqube`. It is used by the CLI to pull additional information from the SonarQube server. |\n\n### An example command\n\nIn this example, the command uploads all JSON-formatted FVT results from a directory to DevOps Insights. Additionally, a test tool is declared, a test result URL is given, and a logical staging environment is provided. Specifying an environment is especially important when you want your results to be analyzed alongside other activities that take place in that same environment.\n\n```shell\nidra --publishtestresult --filelocation=\"tests/fvt/*.json\" --type=fvt -drilldownurl=\"https://example.com/testinfo\" --env=\"staging\"\n```\n\n### Supported Test Formats\n|Type of Test|tag|Supported Formats|\n|-----|-----|-----|\n|Unit Test|`unittest`|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Test Case|`fvt`|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Code Coverage|`code`|Cobertura (xml), lcov, Istanbul, JaCoCo|\n|SonarQube|`sonarqube`|SonarQube|\n|Static Security Scan|`staticsecurityscan`|IBM Application Security on Cloud|\n|Dynamic Security Scan|`dynamicsecurityscan`|IBM Application Security on Cloud|\n|Custom Data Sets - Tests|Custom Tag*|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Custom Data Sets - Code Coverage|Custom Tag*|Cobertura (xml), lcov, Istanbul, JaCoCo|\n\nFor golang [gocov](https://github.com/axw/gocov/) users, please convert to Cobertura using [gocov XML(Cobertura) export](https://github.com/yaoyaozong/gocov-xml)\n\n\\* For custom tags create a quality data set by using the user interface. Navigate to your toolchain, click on DevOps Insights card. Navigate to quality dashboard. Click on the Kebab menu which is to the top-right of the quality dashboard. Click on **Configure Quality Data Sets**\n\n### Upload SonarQube Results\nTo upload data from SonarQube, you must provide the SonarQube server token using `--token`. Your SonarQube server is not required to be accessible from your CI/CD tool.\n\nAfter you run a scan using SonarQube, you can upload SonarQube results by running this command.\n\n```\nidra --publishtestresult --filelocation=.scannerwork/report-task.txt --type=sonarqube --token=234234434\n```\n\nIn the above command, report-task.txt is a file generated during the SonarQube scan.\n\nIf this command fails for some reason, you can enable logs by setting IDRA_DEBUG environment variable to true.\n\nIf you are using self-signed certificates for SonarQube server, you will need to set `export NODE_TLS_REJECT_UNAUTHORIZED=0`\n\n## Upload Deployment Records\nUse the `--publishdeployrecord` command (alias `-d`) to upload deployment records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishdeployrecord --env= --status= --joburl= [--appurl=] [--deployableid=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--env`|`-E` | **Required.** The environment where the pipeline job deployed the app. |\n|`--status`|`-S` | **Required.** The deployment status. This value must be either `pass` or `fail`. |\n|`--joburl`|`-J` | **Required.** The URL to the job's deployment logs. |\n|`--appurl`|`-A` | _Optional._ The URL where the deployed app is running. |\n|`--deployableid`| `-I` | _Optional._ The deployed app's application ID. You can get the ID by running the Cloud Foundry CLI's `cf env` command. The application ID is listed under `VCAP_APPLICATION`. |\n\n### An example command\n\nIn this an example, the command uploads a deployment record from a pipeline job. The deployment is to the \"staging\" environment. The deployment is successful and the app is running at a specified URL.\n\n```shell\nidra --publishdeployrecord --env=\"staging\" --status=pass --appurl=\"https://app.staging.example.com\"\n```\n\n## Making decisions about build quality using gate policies\n\nTo use this feature, create a quality policy by using the user interface. Navigate to your toolchain, click on **DevOps Insights** card. Then on the left menu, click on **Policies**.\n\nUse the `--evaluategate` command (alias `-g`) to request a gate decision for a DevOps Insights policy in your pipeline. If the policy is satisfied, the pipeline continues running. If not, and you use the `--forcedecision` flag, the pipeline stops running.\n\n### Command syntax and options\n\n```shell\nidra --evaluategate --policy= [--forcedecision] [--type=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--policy`|`-P` | **Required.** The name of the policy that the gate uses to make its decision. |\n|`--forcedecision`|`-D` | _Optional._ Set the value to `true` to cause the process to exit with an error code, if the policy evaluation fails. The value defaults to `false` if this option is not specified. |\n|`--type`|`-E` | _Optional_. A rule type to consider. If you include this option, only rules of this type are considered in the decision-making process. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, and `sonarqube` for SonarQube scans. |\n\n\n\n## Release History\n_(Nothing yet)_\n","readmeFilename":"README.md","_id":"grunt-idra3@0.1.38","_shasum":"129b3f13b195d338849552767cd611cfd5981deb","_from":".","_npmVersion":"3.10.3","_nodeVersion":"6.7.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"129b3f13b195d338849552767cd611cfd5981deb","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.38.tgz","integrity":"sha512-ad++KcgT2XOJKMLAsu6RlWBT2khHOqod/b6xSB56qY4lQ4NRAsSrw+SZ83rUjWhA37UltTMTOVYY5FYuu426LQ==","fileCount":48,"unpackedSize":165831,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJcNiSQCRA9TVsSAnZWagAA3Z4P/2dTIFQ/NhGsRd6dRXT1\nbRaRwXf+8+qricYjiUZqaNCqh88FJh2IwiI9eZsTuRE80XSWoVq8bNvV9Bpz\neNhif8RTJQO0VUauG087sdxyTaBbsvyQuuXuZKsC+Jr53xSLfvScXabA3tRL\nh+sCRuQx272RQp5AUl3orzluWv5JAu6KuyPjXq50xUue8cgOXrJbWYThaizB\n+yMa6azvZmmBof4Dfuob8OXuehgNIdFLyTguUTqLwl+YIImgKOP7XBZjMYEM\npoKj7DMpFuXNnFhaNcaLx+mnzKZ7JzqKe/FtSaxTrWjFOdTzQvAnVB7FaHCr\nWZfxB/Bfy9dOX6qTynkYyMKdBF1JqdRe0ZfJLcZ7OXRyKbbB3qSDWR8Dc1eD\nuC3tX1V354f/wSSUOkhHEQPfOjGpUaWgsuRN8Wnh7z+6A9Qkm04cNsU/JK4f\n3Hmq/YO1zfeZYvsrbw9LKwQNwdg7SsKZqrfgMjh96VS4eEY1d9S2jivAx8GY\ngbrYZoZmf9/ZVbjNqQbZbgdawfRhVqoL0Y35pbY1sRTFtZozs6vyqySoytvv\nXbZ+L+GuuQByHIicJ3vWas+hJVna7uYNHm9EZN2ojMXgMWYGINeAWWACUzZH\nr+7+pAlEUtpYfJ5gzUpoLRKTMlzJIXw9fVFG+w37zYdoHE1jKTZdaxMG7Cih\nNkOu\r\n=lHb4\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDVeanR3GoQCF+Z9HxMCO2A5LNFg0N3Z0ZQg/BzedBOWgIhALg7PDlQ0p03tlmNsjFjWQ6ktMs0RHY7sg4SFdULbrIZ"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.38_1547052175894_0.09929399029108232"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.39":{"name":"grunt-idra3","version":"0.1.39","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.3","grunt-contrib-clean":"^1.0.0","grunt-eslint":"^21.0.0","grunt-mocha-test":"^0.12.7","mocha":"^5.2.0","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","inquirer":"^3.0.0","mime":"^1.4.1","request":"^2.87.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.19"},"readme":"# idra\n\n> Command Line utility for integrating with IBM® DevOps Insights\n\nTo install this utility\n```\nnpm install -g grunt-idra3\n```\n\n# Table of Contents\n1. [Concepts](#concepts)\n2. [Getting Started](#getting-started)\n 1. [Scenarios](#scenarios)\n 2. [Prerequisites](#prerequisites)\n 3. [Environment Variables](#environment-variables)\n 4. [Enabling Debug Logs](#enabling-debug-logs)\n 5. [Using the CLI](#using-the-cli)\n3. [Upload Build Records](#upload-build-records)\n4. [Upload Test Results](#upload-test-results)\n 1. [Upload SonarQube Results](#upload-sonarqube-results)\n5. [Upload Deployment Records](#upload-deployment-records)\n6. [Making decisions about build quality using gate policies](#making-decisions-about-build-quality-using-gate-policies)\n\n## Concepts\nIBM® DevOps Insights is a tool that provides insights into your DevOps projects. Use it to learn how compliant your team is with DevOps and developer practices, to manage risk in your codebase, and to automatically enforce quality standards in continuous delivery projects.\n\nUnderstanding of the following concepts will help in faster adoption of IBM® DevOps Insights for your projects.\n\n##### Toolchain\nToolchains are part of [IBM® DevOps Continuous Delivery](https://console.bluemix.net/docs/services/ContinuousDelivery/cd_overview.html#cd_overview). Toolchains provide an integrated set of tools to build, deploy and manage your apps. You can create toolchains that include IBM Cloud services, open source tools, and third party tools that make development and operations repeatable and easier to manage. It is required that the IBM DevOps Insights should be added as one of the tool to your toolchain.\n\n##### Integrating your build tool with IBM DevOps Insights\nThis means instrumenting your build tool with this CLI or DevOps Insights Jenkins plugin to send build, test and deployment records to IBM DevOps Insights.\n\n##### Build record\nIBM DevOps Insights needs to know when a build is complete. This record contains application name, branch, build id, reference to git repo and other fields. This CLI and Jenkins plugin has a command to publish the build record to DevOps Insights.\n\n##### Test record\nIBM DevOps Insights needs to know about the tests performed during the build process. It is necessary that the tests should generate some kind of JSON or XML based file. Here are the list of supported [format](supported-test-formats). The generated test file is published as a test record. Along with the test file this record contains application name, build id, type of tests and other fields. It is required that the application name and build id in the test record matches the one used in the build record for a given build. This CLI and Jenkins plugin has a command to publish test record to DevOps Insights.\n\n##### Deployment records\nIBM DevOps Insights needs to know about the deployments made during the deployment process. This record contains the application name, build id, environment name, status of the deployment and other fields. It is required that the application name and build id in the deployment record matches the one used in the build record for a given build. This CLI and Jenkins plugin has a command to publish a deployment to DevOps Insights.\n\n##### Build Id (or Number)\nThis is an arbitrary length string uniquely identifying each build. This id is used to tie the build, test and deployment records together so it is important to publish those records with the same id for a given build.\n\n##### Policy\nA policy is set of rules specified by the user that collectively defines what is considered a good set of test records for a given application build. Typically, one rule is added for each test record published to DevOps Insights. The policy rules are evaluated by the gate.\n\n##### Branch\nThis is the name of the branch in the source control system.\n\n##### Environment\nThis is the name of environment to which deployments are made during the build process.\n\n##### Data set\nThis is an arbitrary string that identifies the type of tests performed during the build process. Besides the standard names such as \"unit test\", \"fvt\". The tool allows the user to define a custom name.\n\n## Getting Started\n\nUse this utility to integrate IBM® DevOps Insights with Travis CI, Concourse, IBM Urban Code Deploy, IBM Continuous Delivery Pipelines and other CI/CD tools. If you are using Jenkins, use this [Jenkins plugin](https://plugins.jenkins.io/ibm-cloud-devops) instead.\n\nUsing this utility, you can\n - Publish build records, test records and deploy records to IBM® DevOps Insights \n - Make go/no-go decisions about a build's quality by using a Gate policy\n\nFor samples of dashboards in IBM® DevOps Insights, see [Value Proposition](https://plugins.jenkins.io/ibm-cloud-devops).\n\nFor more information about IBM DevOps Insights, see [the official documentation](https://console.bluemix.net/docs/services/DevOpsInsights/index.html).\n\n### Scenarios\nThis document covers two scenarios:\n1. You are integrating DevOps Insights with IBM Continuous Delivery tool.\n2. You are integrating DevOps Insights with other CI/CD tools (e.g., Travis CI, Concourse, IBM Urban Code Deploy, others)\n\n### Prerequisites\n\nTo use the CLI, you need to do the following. These steps should take about 10 minutes.\n\n1. A valid IBM Cloud account. If you don't have one, [register here](https://console.bluemix.net/registration).\n\n2. Once you have an account, you can create an API Key. Log in to [IBM Cloud](https://console.bluemix.net). Click on **Manage**->**Security**->**Platform API Key**. On that screen, create an API Key.\n\n3. An IBM Continuous Delivery toolchain. To create a toolchain:\n - Go to https://console.bluemix.net/devops\n - Click on **Create a Toolchain** button and then select **Build Your Own Toolchain** template. \n - In the next screen, click **Create**.\n - From the URL displayed in the browser, make note of your toolchain id. For example, if your URL is https://console.bluemix.net/devops/toolchains/05572df3-01dc-441b-911d-b2202fe33f96, the toolchain id is the long string after **toolchains/**\n - You can always navigate to your toolchain by [clicking here](https://console.bluemix.net/devops)\n\n4. Add DevOps Insights tool to your toolchain\n - Go to your toolchain\n - Click on **Add a Tool** button\n - Select DevOps Insights tool and click **Create Integration** button\n\n5. Your CI/CD tool must have Node.js® 4.x or greater.\n\n### Environment Variables\n\nIf you are using Travis, Concourse or any CI/CD tool other than the IBM Continuous Delivery pipeline, then set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|TOOLCHAIN_ID| **Required.** The toolchain's GUID |\n|IBM_CLOUD_API_KEY| **Required.** The Bluemix user's Api key|\n|BUILD_NUMBER| **Required.** Any string that identifies the build |\n|LOGICAL_APP_NAME| **Required.** The application's name.|\n\nIf you are using IBM Continuous Delivery pipeline, you need to set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|IBM_CLOUD_API_KEY| **Required** The Bluemix user's Api key|\n|BUILD_PREFIX| **Required.** Any string. For example, the Git branch name. |\n|LOGICAL_APP_NAME| **Required.** The application's name.|\n|PATH|**Required.** In order to have required version of Node.js in your path, set the PATH variable before invoking the utility: `export PATH=/opt/IBM/node-v4.2/bin:$PATH`|\n\nIf you are using IBM Continuous Delivery pipeline and if you want to publish Insights data to another toolchain, then set the following environment variables. \n\n|Name|Description|\n|-----|-----|\n|TOOLCHAIN_ID| **Required.** The target toolchain's GUID. If the target toolchain is owned by different user then provide the target toolchain owner's Bluemix Api key in the `IBM_CLOUD_API_KEY` variable.|\n\n\nIf you are using IBM UrbanCode Deploy, DevOps Insights relies on the previous set of variables, and this one:\n\n|Name|Description|\n|-----|-----|\n|UCD_REQUEST_ID| This maps to the ${p:request.id} property value. |\n\n### Enabling Debug logs\nIf you want to enable debug logs for the DevOps Insights CLI, set the `IDRA_DEBUG` environment variable to `true`. This works in all environments.\n\n|Name|Description|\n|-----|-----|\n|IDRA_DEBUG| When this value is `true`, the DevOps Insights CLI's debugging mode is enabled. By default, the value is `false`. |\n\n\n### Using the CLI\n\nSet [environment details](#environment-details) as described above. Ensure that Node.js 4.2 or higher is avaialble in your CI/CD tool.\n\nTo install this utility, use `npm install -g grunt-idra3`\n\nThen you can invoke the CLI with the `idra` command. You can run the CLI in any pipeline job's command script. For example, this command uploads functional verification test results to DevOps Insights:\n\n```\n# Upload test results\nidra --publishtestresult --filelocation=\"results.json\" --type=fvt\n```\n\n\n## Upload Build Records\nUse the `--publishbuildrecord` command (alias `-b`) to upload build records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishbuildrecord --branch= --repositoryurl= --commitid= --status= [--joburl=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--branch`|`-B` | **Required.** The repository branch on which the build is being performed. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--repositoryurl`|`-R` | **Required.** The url of the git repository. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--commitid`|`-C` | **Required.** The git commit id. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--status`|`-S` | **Required.** The build status. This value must be either `pass` or `fail`. |\n|`--joburl`|`-J` | _Optional_. The URL to the job's build logs. |\n\n\n### An example command\n\nIn this an example, the command uploads a build record from a pipeline job.\n\n```shell\nidra --publishbuildrecord --branch=master --repositoryurl=\"https://github.com/oic/dlms.git\" --commitid=dff7884b9168168d91cb9e5aec78e93db0fa80d9 --status=pass\n```\n\n## Upload Test Results\n\nUse the `--publishtestresult` command (alias `-p`) to upload results from these test types to DevOps Insights:\n\n* Unit tests\n* Code coverage tests\n* Functional verification tests (FVT)\n* Static security scans from IBM Application Security on Cloud\n* Dynamic app scans from IBM Application Security on Cloud\n* [SonarQube results](#upload-sonarqube-results)\n\n\n### Command syntax and options\n\n```shell\nidra --publishtestresult --filelocation= --type= [--drilldownurl=] [--env=] [--token=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--filelocation`| `-F` |**Required.** The location of the test results that you want to upload. This can be a single file, an entire directory, or multiple files that match a wildcard expression.|\n|`--type`| `-T` |**Required.** The type of test results that you want to upload. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, and `sonarqube` for SonarQube scans. In addition to these types you can also use a custom quality data set tag to upload test results of different type.|\n|`--drilldownurl`| `-U` |_Optional._ A URL where more information about the test results can be found. If this URL is invalid, the option is ignored. |\n|`--env`| `-E` |_Optional._ The environment name to associate with the test results. This option is ignored for unit tests, code coverage tests, and static security scans. |\n|`--token`| `-K` |_Optional_. This is a SonarQube token. This flag is valid only if the type specified is `sonarqube`. It is used by the CLI to pull additional information from the SonarQube server. |\n\n### An example command\n\nIn this example, the command uploads all JSON-formatted FVT results from a directory to DevOps Insights. Additionally, a test tool is declared, a test result URL is given, and a logical staging environment is provided. Specifying an environment is especially important when you want your results to be analyzed alongside other activities that take place in that same environment.\n\n```shell\nidra --publishtestresult --filelocation=\"tests/fvt/*.json\" --type=fvt -drilldownurl=\"https://example.com/testinfo\" --env=\"staging\"\n```\n\n### Supported Test Formats\n|Type of Test|tag|Supported Formats|\n|-----|-----|-----|\n|Unit Test|`unittest`|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Test Case|`fvt`|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Code Coverage|`code`|Cobertura (xml), lcov, Istanbul, JaCoCo|\n|SonarQube|`sonarqube`|SonarQube|\n|Static Security Scan|`staticsecurityscan`|IBM Application Security on Cloud|\n|Dynamic Security Scan|`dynamicsecurityscan`|IBM Application Security on Cloud|\n|Custom Data Sets - Tests|Custom Tag*|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Custom Data Sets - Code Coverage|Custom Tag*|Cobertura (xml), lcov, Istanbul, JaCoCo|\n\nFor golang [gocov](https://github.com/axw/gocov/) users, please convert to Cobertura using [gocov XML(Cobertura) export](https://github.com/yaoyaozong/gocov-xml)\n\n\\* For custom tags create a quality data set by using the user interface. Navigate to your toolchain, click on DevOps Insights card. Navigate to quality dashboard. Click on the Kebab menu which is to the top-right of the quality dashboard. Click on **Configure Quality Data Sets**\n\n### Upload SonarQube Results\nTo upload data from SonarQube, you must provide the SonarQube server token using `--token`. Your SonarQube server is not required to be accessible from your CI/CD tool.\n\nAfter you run a scan using SonarQube, you can upload SonarQube results by running this command.\n\n```\nidra --publishtestresult --filelocation=.scannerwork/report-task.txt --type=sonarqube --token=234234434\n```\n\nIn the above command, report-task.txt is a file generated during the SonarQube scan.\n\nIf this command fails for some reason, you can enable logs by setting IDRA_DEBUG environment variable to true.\n\nIf you are using self-signed certificates for SonarQube server, you will need to set `export NODE_TLS_REJECT_UNAUTHORIZED=0`\n\n## Upload Deployment Records\nUse the `--publishdeployrecord` command (alias `-d`) to upload deployment records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishdeployrecord --env= --status= --joburl= [--appurl=] [--deployableid=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--env`|`-E` | **Required.** The environment where the pipeline job deployed the app. |\n|`--status`|`-S` | **Required.** The deployment status. This value must be either `pass` or `fail`. |\n|`--joburl`|`-J` | **Required.** The URL to the job's deployment logs. |\n|`--appurl`|`-A` | _Optional._ The URL where the deployed app is running. |\n|`--deployableid`| `-I` | _Optional._ The deployed app's application ID. You can get the ID by running the Cloud Foundry CLI's `cf env` command. The application ID is listed under `VCAP_APPLICATION`. |\n\n### An example command\n\nIn this an example, the command uploads a deployment record from a pipeline job. The deployment is to the \"staging\" environment. The deployment is successful and the app is running at a specified URL.\n\n```shell\nidra --publishdeployrecord --env=\"staging\" --status=pass --appurl=\"https://app.staging.example.com\"\n```\n\n## Making decisions about build quality using gate policies\n\nTo use this feature, create a quality policy by using the user interface. Navigate to your toolchain, click on **DevOps Insights** card. Then on the left menu, click on **Policies**.\n\nUse the `--evaluategate` command (alias `-g`) to request a gate decision for a DevOps Insights policy in your pipeline. If the policy is satisfied, the pipeline continues running. If not, and you use the `--forcedecision` flag, the pipeline stops running.\n\n### Command syntax and options\n\n```shell\nidra --evaluategate --policy= [--forcedecision] [--type=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--policy`|`-P` | **Required.** The name of the policy that the gate uses to make its decision. |\n|`--forcedecision`|`-D` | _Optional._ Set the value to `true` to cause the process to exit with an error code, if the policy evaluation fails. The value defaults to `false` if this option is not specified. |\n|`--type`|`-E` | _Optional_. A rule type to consider. If you include this option, only rules of this type are considered in the decision-making process. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, and `sonarqube` for SonarQube scans. |\n\n\n\n## Release History\n_(Nothing yet)_\n","readmeFilename":"README.md","_id":"grunt-idra3@0.1.39","_shasum":"02a1d17e4d36a9425facdbfb2d14c02e8a29ebf3","_from":".","_npmVersion":"3.10.3","_nodeVersion":"6.7.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"02a1d17e4d36a9425facdbfb2d14c02e8a29ebf3","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.39.tgz","integrity":"sha512-Lg3Tpbj5PbghXyeKTkttpXv7opJ+/gVN5GFEcPtvL65Uv1LCjFn6/qgtDVtYdY2U48wXJRw7dvvTNLK4VKPESg==","fileCount":48,"unpackedSize":165573,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJcNn1uCRA9TVsSAnZWagAAHPwP/0uOEMvxft2eTDnxeAeZ\nbudwDyEhwKClPVXkX4YGnSGK9eeC49lwfEZzGgnQA7NKBnd9nXfiyW2WIgZf\n8Ygg+hyzouB8soaIMffoCXBgRLSRn30hCQDARxJtMU+pI6+ITIlva33/Afv3\nVDuHmdkU4LznG9bZ33K3ofdATH8si/C8mDdNa+VGpWXeVmOP8i0mdlTq4jI7\nF0szi0JQJ9ixAcbvyW0389+Y8WkyaOArUaxhDW9aCknED/0wQjF9XZFXty8x\nk+gBCd3DcRsc9+OBEqZ3Kj9dzQQnd/sR+iSM+05obpHESXHM1kYVBExAo5Gw\n5QfCGvFkTfq7ZI62ovHa9MFqtBf2TQhOaTfBR5fjXtBf8aAXjjddsjB+ziir\nvbOVFMooxQ46wNVTNFY4iw427+mmSSqYHMwP9ImK3jK1FWJLrmupdIw5rRZZ\nPDRTr0F4aCgP0ZBdcO/+MFRb5aamj2QB2jcTe/Ny+WWu9diyj1APRqSK6Ro4\n3RE+sbfajmd6yTyiwQcQbYEtyDnwkm+0oSX3MEP+fD4YkSieZu3HwI1TKXgY\nQ/a1xZk9XwDRHXQ+AHoE6XN3SrT1FmdFVbvi2ZQVAPKAzlp69qMS7F+8Sa0g\ninvYGen6GVfREUcOSv2Tj3f5/fAdDHxqBCvSaFa9zKFWj0HsEVht+XP9dVj+\npUxF\r\n=NYWf\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIElclKrQv2Kg+gbpVXC0t1Z3+oFm4yPlRS92jXO56uAUAiEA94ocKyeYQAm5aeUWenzYS49xy09eOGlJcnvBfmM4+NY="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.39_1547074925469_0.9970195665932777"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.40":{"name":"grunt-idra3","version":"0.1.40","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.3","grunt-contrib-clean":"^1.0.0","grunt-eslint":"^21.0.0","grunt-mocha-test":"^0.12.7","mocha":"^5.2.0","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","inquirer":"^3.0.0","mime":"^1.4.1","request":"^2.87.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.19"},"_id":"grunt-idra3@0.1.40","_shasum":"192ca6a64493e847fd349ccecc97a73e18a7ba06","_from":".","_npmVersion":"3.10.3","_nodeVersion":"6.7.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"192ca6a64493e847fd349ccecc97a73e18a7ba06","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.40.tgz","integrity":"sha512-SRT6Ay9w2s1GcBCE19yi6iiWwbnZVF86mwfz2Qjbz8FbDoIRITxDfLbQnnwnWFghrzpfwHp65EKqvF9ACbSkmQ==","fileCount":49,"unpackedSize":166704,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJcbxjNCRA9TVsSAnZWagAALFcQAJ9ZeP0yVNmq2lIPm3ad\nhsEDue8CH+zs4kr/QkM18Wy+SO9XS70zIEBMWkvem3DQFePLlyTYgNO/BtDE\nfsVtMvOqednnmM7jRIbDq5lYtsgAIkeYe2jgxVDd3XJi5EITY/M4ZfuzLCDa\nS1cH5mdRdOeoHZd3TZh4BZh07HUmuysUDndAVRdsuwVLbs1CT8PPIl3AWf76\nyMyLN5VZsApP79dTknEMGxhJFIoNVz7AB3BlcksLptHn47dRGuQ73ILrJY4e\nY9ShofRGklB3SqX0Mn7jEsNZtyuZHeSK1kLm8Fqg1K7OjcKXaHi92B8OTurq\nn6By5KVh9bX2e+N1UuGY5ZxKp97/QbY8HhrFXHOr8j6y+/qz9Je09FJAal3R\nCiAjHNYRJMhYKb1VnF9jB9I8quNReuVKLqTGB1dhC13Zz4VK4SXRL6eznTBI\nctwQb3wMTuugBm5STD9WhgU+cxyunsyfEILE/tR409Y79KDzDstdMuC3Nqi+\nNUfM19UazjtuT9XAyyba6yPyQddg/2/Pf0HzWqpyV4WzkeE5BeZ16M+2mTIa\nHhByV2BPQP1V4BBF6jP+N1Bau5h+VOpsAR9i2TqEcbIugPJmsIOODVRAaCXp\nc5UR9aT3SSoA/65zbeIwYN7yhjVY4PB+nE5GaYyGG0IGIFmSiRWIHp+rpZ6B\nK5CW\r\n=OWbs\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIBJS3JqOF4RU7s/ftp1BDw0n6SjprTvoAHxmlipl7eukAiEAj9vl/foHBjsbZaGxDeEUxXOjDzVMooD5j94jF5wVJzY="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.40_1550784716879_0.9121027994584192"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.41":{"name":"grunt-idra3","version":"0.1.41","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.3","grunt-contrib-clean":"^1.0.0","grunt-eslint":"^21.0.0","grunt-mocha-test":"^0.12.7","mocha":"^5.2.0","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","inquirer":"^3.0.0","mime":"^1.4.1","request":"^2.87.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.19"},"readme":"# idra\n\n> Command Line utility for integrating with IBM® DevOps Insights\n\nTo install this utility\n```\nnpm install -g grunt-idra3\n```\n\n# Table of Contents\n1. [Concepts](#concepts)\n2. [Getting Started](#getting-started)\n 1. [Scenarios](#scenarios)\n 2. [Prerequisites](#prerequisites)\n 3. [Environment Variables](#environment-variables)\n 4. [Enabling Debug Logs](#enabling-debug-logs)\n 5. [Using the CLI](#using-the-cli)\n3. [Upload Build Records](#upload-build-records)\n4. [Upload Test Results](#upload-test-results)\n 1. [Upload SonarQube Results](#upload-sonarqube-results)\n5. [Upload Deployment Records](#upload-deployment-records)\n6. [Making decisions about build quality using gate policies](#making-decisions-about-build-quality-using-gate-policies)\n\n## Concepts\nIBM® DevOps Insights is a tool that provides insights into your DevOps projects. Use it to learn how compliant your team is with DevOps and developer practices, to manage risk in your codebase, and to automatically enforce quality standards in continuous delivery projects.\n\nUnderstanding of the following concepts will help in faster adoption of IBM® DevOps Insights for your projects.\n\n##### Toolchain\nToolchains are part of [IBM® DevOps Continuous Delivery](https://console.bluemix.net/docs/services/ContinuousDelivery/cd_overview.html#cd_overview). Toolchains provide an integrated set of tools to build, deploy and manage your apps. You can create toolchains that include IBM Cloud services, open source tools, and third party tools that make development and operations repeatable and easier to manage. It is required that the IBM DevOps Insights should be added as one of the tool to your toolchain.\n\n##### Integrating your build tool with IBM DevOps Insights\nThis means instrumenting your build tool with this CLI or DevOps Insights Jenkins plugin to send build, test and deployment records to IBM DevOps Insights.\n\n##### Build record\nIBM DevOps Insights needs to know when a build is complete. This record contains application name, branch, build id, reference to git repo and other fields. This CLI and Jenkins plugin has a command to publish the build record to DevOps Insights.\n\n##### Test record\nIBM DevOps Insights needs to know about the tests performed during the build process. It is necessary that the tests should generate some kind of JSON or XML based file. Here are the list of supported [format](supported-test-formats). The generated test file is published as a test record. Along with the test file this record contains application name, build id, type of tests and other fields. It is required that the application name and build id in the test record matches the one used in the build record for a given build. This CLI and Jenkins plugin has a command to publish test record to DevOps Insights.\n\n##### Deployment records\nIBM DevOps Insights needs to know about the deployments made during the deployment process. This record contains the application name, build id, environment name, status of the deployment and other fields. It is required that the application name and build id in the deployment record matches the one used in the build record for a given build. This CLI and Jenkins plugin has a command to publish a deployment to DevOps Insights.\n\n##### Build Id (or Number)\nThis is an arbitrary length string uniquely identifying each build. This id is used to tie the build, test and deployment records together so it is important to publish those records with the same id for a given build.\n\n##### Policy\nA policy is set of rules specified by the user that collectively defines what is considered a good set of test records for a given application build. Typically, one rule is added for each test record published to DevOps Insights. The policy rules are evaluated by the gate.\n\n##### Branch\nThis is the name of the branch in the source control system.\n\n##### Environment\nThis is the name of environment to which deployments are made during the build process.\n\n##### Data set\nThis is an arbitrary string that identifies the type of tests performed during the build process. Besides the standard names such as \"unit test\", \"fvt\". The tool allows the user to define a custom name.\n\n## Getting Started\n\nUse this utility to integrate IBM® DevOps Insights with Travis CI, Concourse, IBM Urban Code Deploy, IBM Continuous Delivery Pipelines and other CI/CD tools. If you are using Jenkins, use this [Jenkins plugin](https://plugins.jenkins.io/ibm-cloud-devops) instead.\n\nUsing this utility, you can\n - Publish build records, test records and deploy records to IBM® DevOps Insights \n - Make go/no-go decisions about a build's quality by using a Gate policy\n\nFor samples of dashboards in IBM® DevOps Insights, see [Value Proposition](https://plugins.jenkins.io/ibm-cloud-devops).\n\nFor more information about IBM DevOps Insights, see [the official documentation](https://console.bluemix.net/docs/services/DevOpsInsights/index.html).\n\n### Scenarios\nThis document covers two scenarios:\n1. You are integrating DevOps Insights with IBM Continuous Delivery tool.\n2. You are integrating DevOps Insights with other CI/CD tools (e.g., Travis CI, Concourse, IBM Urban Code Deploy, others)\n\n### Prerequisites\n\nTo use the CLI, you need to do the following. These steps should take about 10 minutes.\n\n1. A valid IBM Cloud account. If you don't have one, [register here](https://console.bluemix.net/registration).\n\n2. Once you have an account, you can create an API Key. Log in to [IBM Cloud](https://console.bluemix.net). Click on **Manage**->**Security**->**Platform API Key**. On that screen, create an API Key.\n\n3. An IBM Continuous Delivery toolchain. To create a toolchain:\n - Go to https://console.bluemix.net/devops\n - Click on **Create a Toolchain** button and then select **Build Your Own Toolchain** template. \n - In the next screen, click **Create**.\n - From the URL displayed in the browser, make note of your toolchain id. For example, if your URL is https://console.bluemix.net/devops/toolchains/05572df3-01dc-441b-911d-b2202fe33f96, the toolchain id is the long string after **toolchains/**\n - You can always navigate to your toolchain by [clicking here](https://console.bluemix.net/devops)\n\n4. Add DevOps Insights tool to your toolchain\n - Go to your toolchain\n - Click on **Add a Tool** button\n - Select DevOps Insights tool and click **Create Integration** button\n\n5. Your CI/CD tool must have Node.js® 4.x or greater.\n\n### Environment Variables\n\nIf you are using Travis, Concourse or any CI/CD tool other than the IBM Continuous Delivery pipeline, then set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|TOOLCHAIN_ID| **Required.** The toolchain's GUID |\n|IBM_CLOUD_API_KEY| **Required.** The Bluemix user's Api key|\n|BUILD_NUMBER| **Required.** Any string that identifies the build |\n|LOGICAL_APP_NAME| **Required.** The application's name.|\n\nIf you are using IBM Continuous Delivery pipeline, you need to set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|IBM_CLOUD_API_KEY| **Required** The Bluemix user's Api key|\n|BUILD_PREFIX| **Required.** Any string. For example, the Git branch name. |\n|LOGICAL_APP_NAME| **Required.** The application's name.|\n|PATH|**Required.** In order to have required version of Node.js in your path, set the PATH variable before invoking the utility: `export PATH=/opt/IBM/node-v4.2/bin:$PATH`|\n\nIf you are using IBM Continuous Delivery pipeline and if you want to publish Insights data to another toolchain, then set the following environment variables. \n\n|Name|Description|\n|-----|-----|\n|TOOLCHAIN_ID| **Required.** The target toolchain's GUID. If the target toolchain is owned by different user then provide the target toolchain owner's Bluemix Api key in the `IBM_CLOUD_API_KEY` variable.|\n\n\nIf you are using IBM UrbanCode Deploy, DevOps Insights relies on the previous set of variables, and this one:\n\n|Name|Description|\n|-----|-----|\n|UCD_REQUEST_ID| This maps to the ${p:request.id} property value. |\n\n### Enabling Debug logs\nIf you want to enable debug logs for the DevOps Insights CLI, set the `IDRA_DEBUG` environment variable to `true`. This works in all environments.\n\n|Name|Description|\n|-----|-----|\n|IDRA_DEBUG| When this value is `true`, the DevOps Insights CLI's debugging mode is enabled. By default, the value is `false`. |\n\n\n### Using the CLI\n\nSet [environment details](#environment-details) as described above. Ensure that Node.js 4.2 or higher is avaialble in your CI/CD tool.\n\nTo install this utility, use `npm install -g grunt-idra3`\n\nThen you can invoke the CLI with the `idra` command. You can run the CLI in any pipeline job's command script. For example, this command uploads functional verification test results to DevOps Insights:\n\n```\n# Upload test results\nidra --publishtestresult --filelocation=\"results.json\" --type=fvt\n```\n\n\n## Upload Build Records\nUse the `--publishbuildrecord` command (alias `-b`) to upload build records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishbuildrecord --branch= --repositoryurl= --commitid= --status= [--joburl=] [--buildnumber=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--branch`|`-B` | **Required.** The repository branch on which the build is being performed. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--repositoryurl`|`-R` | **Required.** The url of the git repository. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--commitid`|`-C` | **Required.** The git commit id. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--status`|`-S` | **Required.** The build status. This value must be either `pass` or `fail`. |\n|`--joburl`|`-J` | _Optional_. The URL to the job's build logs. |\n|`--buildnumber`|`-N` | _Optional_. Any string that identifies the build. This option overrides the value provided by **BUILD_NUMBER** or **BUILD_PREFIX** environment variables |\n\n\n### An example command\n\nIn this an example, the command uploads a build record from a pipeline job.\n\n```shell\nidra --publishbuildrecord --branch=master --repositoryurl=\"https://github.com/oic/dlms.git\" --commitid=dff7884b9168168d91cb9e5aec78e93db0fa80d9 --status=pass\n```\n\n## Upload Test Results\n\nUse the `--publishtestresult` command (alias `-p`) to upload results from these test types to DevOps Insights:\n\n* Unit tests\n* Code coverage tests\n* Functional verification tests (FVT)\n* Static security scans from IBM Application Security on Cloud\n* Dynamic app scans from IBM Application Security on Cloud\n* [SonarQube results](#upload-sonarqube-results)\n\n\n### Command syntax and options\n\n```shell\nidra --publishtestresult --filelocation= --type= [--drilldownurl=] [--env=] [--token=] [--buildnumber=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--filelocation`| `-F` |**Required.** The location of the test results that you want to upload. This can be a single file, an entire directory, or multiple files that match a wildcard expression.|\n|`--type`| `-T` |**Required.** The type of test results that you want to upload. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, and `sonarqube` for SonarQube scans. In addition to these types you can also use a custom quality data set tag to upload test results of different type.|\n|`--drilldownurl`| `-U` |_Optional._ A URL where more information about the test results can be found. If this URL is invalid, the option is ignored. |\n|`--env`| `-E` |_Optional._ The environment name to associate with the test results. This option is ignored for unit tests, code coverage tests, and static security scans. |\n|`--token`| `-K` |_Optional_. This is a SonarQube token. This flag is valid only if the type specified is `sonarqube`. It is used by the CLI to pull additional information from the SonarQube server. |\n|`--buildnumber`|`-N` | _Optional_. Any string that identifies the build. This option overrides the value provided by **BUILD_NUMBER** or **BUILD_PREFIX** environment variables |\n\n### An example command\n\nIn this example, the command uploads all JSON-formatted FVT results from a directory to DevOps Insights. Additionally, a test tool is declared, a test result URL is given, and a logical staging environment is provided. Specifying an environment is especially important when you want your results to be analyzed alongside other activities that take place in that same environment.\n\n```shell\nidra --publishtestresult --filelocation=\"tests/fvt/*.json\" --type=fvt -drilldownurl=\"https://example.com/testinfo\" --env=\"staging\" \n```\n\n### Supported Test Formats\n|Type of Test|tag|Supported Formats|\n|-----|-----|-----|\n|Unit Test|`unittest`|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Test Case|`fvt`|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Code Coverage|`code`|Cobertura (xml), lcov, Istanbul, JaCoCo|\n|SonarQube|`sonarqube`|SonarQube|\n|Static Security Scan|`staticsecurityscan`|IBM Application Security on Cloud|\n|Dynamic Security Scan|`dynamicsecurityscan`|IBM Application Security on Cloud|\n|Custom Data Sets - Tests|Custom Tag*|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Custom Data Sets - Code Coverage|Custom Tag*|Cobertura (xml), lcov, Istanbul, JaCoCo|\n\nFor golang [gocov](https://github.com/axw/gocov/) users, please convert to Cobertura using [gocov XML(Cobertura) export](https://github.com/yaoyaozong/gocov-xml)\n\n\\* For custom tags create a quality data set by using the user interface. Navigate to your toolchain, click on DevOps Insights card. Navigate to quality dashboard. Click on the Kebab menu which is to the top-right of the quality dashboard. Click on **Configure Quality Data Sets**\n\n### Upload SonarQube Results\nTo upload data from SonarQube, you must provide the SonarQube server token using `--token`. Your SonarQube server is not required to be accessible from your CI/CD tool.\n\nAfter you run a scan using SonarQube, you can upload SonarQube results by running this command.\n\n```\nidra --publishtestresult --filelocation=.scannerwork/report-task.txt --type=sonarqube --token=234234434\n```\n\nIn the above command, report-task.txt is a file generated during the SonarQube scan.\n\nIf this command fails for some reason, you can enable logs by setting IDRA_DEBUG environment variable to true.\n\nIf you are using self-signed certificates for SonarQube server, you will need to set `export NODE_TLS_REJECT_UNAUTHORIZED=0`\n\n## Upload Deployment Records\nUse the `--publishdeployrecord` command (alias `-d`) to upload deployment records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishdeployrecord --env= --status= --joburl= [--appurl=] [--deployableid=] [--buildnumber=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--env`|`-E` | **Required.** The environment where the pipeline job deployed the app. |\n|`--status`|`-S` | **Required.** The deployment status. This value must be either `pass` or `fail`. |\n|`--joburl`|`-J` | **Required.** The URL to the job's deployment logs. |\n|`--appurl`|`-A` | _Optional._ The URL where the deployed app is running. |\n|`--deployableid`| `-I` | _Optional._ The deployed app's application ID. You can get the ID by running the Cloud Foundry CLI's `cf env` command. The application ID is listed under `VCAP_APPLICATION`. |\n|`--buildnumber`|`-N` | _Optional_. Any string that identifies the build. This option overrides the value provided by **BUILD_NUMBER** or **BUILD_PREFIX** environment variables |\n\n### An example command\n\nIn this an example, the command uploads a deployment record from a pipeline job. The deployment is to the \"staging\" environment. The deployment is successful and the app is running at a specified URL.\n\n```shell\nidra --publishdeployrecord --env=\"staging\" --status=pass --appurl=\"https://app.staging.example.com\"\n```\n\n## Making decisions about build quality using gate policies\n\nTo use this feature, create a quality policy by using the user interface. Navigate to your toolchain, click on **DevOps Insights** card. Then on the left menu, click on **Policies**.\n\nUse the `--evaluategate` command (alias `-g`) to request a gate decision for a DevOps Insights policy in your pipeline. If the policy is satisfied, the pipeline continues running. If not, and you use the `--forcedecision` flag, the pipeline stops running.\n\n### Command syntax and options\n\n```shell\nidra --evaluategate --policy= [--forcedecision] [--type=] [--buildnumber=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--policy`|`-P` | **Required.** The name of the policy that the gate uses to make its decision. |\n|`--forcedecision`|`-D` | _Optional._ Set the value to `true` to cause the process to exit with an error code, if the policy evaluation fails. The value defaults to `false` if this option is not specified. |\n|`--type`|`-E` | _Optional_. A rule type to consider. If you include this option, only rules of this type are considered in the decision-making process. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, and `sonarqube` for SonarQube scans. |\n|`--buildnumber`|`-N` | _Optional_. Any string that identifies the build. This option overrides the value provided by **BUILD_NUMBER** or **BUILD_PREFIX** environment variables |\n\n\n\n## Release History\n_(Nothing yet)_\n","readmeFilename":"README.md","_id":"grunt-idra3@0.1.41","_shasum":"34cc7b435d0624a789da2397c96a7e330fbf8bcf","_from":".","_npmVersion":"3.10.3","_nodeVersion":"6.7.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"34cc7b435d0624a789da2397c96a7e330fbf8bcf","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.41.tgz","integrity":"sha512-rX3DaWiw+t9/0bSH650K3nIs0phDZCV3ZI80V3aVGxPkB7BSWV0TzWnPOfH38TW7RX7oZRd2UYqMWS+aFQdoig==","fileCount":49,"unpackedSize":166859,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJchoGlCRA9TVsSAnZWagAAFN8QAJaIIcT4ZdOyPIASHlpP\nk86mQnjQZS1cUmNxgZt5bE/cv9C4Wp3ikhMmAmY+D15RHzIP8nhVcjVqWpCz\naO1De7jDBTc0kOToErkQxvv4qj1eefm7KBBpqyK6XrucLfiI9CdDFLfam9g7\nGBqDB7ptqTFx7k0gRlB+4OTNuK2C/MqA7zBCLhowbcnouEXk6+VyvfPbhrW5\niT34VP/ASxn2ckaCPRu1u1iydG6PkSusTzBF808liht+QLs4u1KiytH6+INU\nd/LAss1FZoE8jsqcZaVYmzYo1h96TEemWaTjBZ3J5kHYPR1z4an7MotddWux\nSAqj6RiJNXhYONgtqQT2FPNr2ESlkUMkYkuhq6lPXJ7aLDhrfT93iRUe5vcs\nHFI4Mj6ib+ZfLbsdGm77M9GerwXh1+IPHK2XwfjCrRGoxTopSjGqH8DB04AW\n/RZoRhEuQ5+xqlFNAkK2yJFARe2Dy3xWG0me/otzZqrPnlzvbZQjveR7ae8W\nGlgoUVKkDd27yM95ODSGmQ32dHslec4mRhfa6IyjDV9OM/IdeXLDomFytQmT\nEQtCN9qj+9WqoNcZ1xTNaln9ZVWtQz7nzOYxbhMdS2VK/isAbI+zkSSWPGAg\nCZLEiX1TS60BundTmNLiUM/OZdOYEZWJabsU8ZHQj/mwReiZaNvw5mo9h7Uv\nyxh5\r\n=l2FH\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDKIm1tgG0ZienvWme9uHpvuus4rfH2+5eICOPTO694ngIhAKqeOJTnQ7IQmNwwNtTVbnvpu3++ViqdXColdAMD2xnp"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.41_1552318884617_0.22963681409183634"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.42":{"name":"grunt-idra3","version":"0.1.42","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.3","grunt-contrib-clean":"^1.0.0","grunt-eslint":"^21.0.0","grunt-mocha-test":"^0.12.7","mocha":"^5.2.0","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","inquirer":"^3.0.0","mime":"^1.4.1","request":"^2.87.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.19"},"_id":"grunt-idra3@0.1.42","_shasum":"e2018122e866f1d2f87d5e182eb85636724c43a5","_from":".","_npmVersion":"3.10.3","_nodeVersion":"6.7.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"e2018122e866f1d2f87d5e182eb85636724c43a5","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.42.tgz","integrity":"sha512-0ETpNgXmc3pyRA5vFZmFjx4DPyQfeDeuZzDJA35NB/Wbsp9Pb6QqrEQZmlJrxjkBS8HWeZfW1gk6CVGdO5U2jQ==","fileCount":49,"unpackedSize":166784,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJciAanCRA9TVsSAnZWagAAWMgQAJUpdQ2N9+OKhmbya9v5\n5Yyy8kW5INUYPZ1JmcCXt1UFbjBBKXkbilqu5XGeddoMbZFlSiRno5yKMJ0c\n+f0cxkgQz1RIruTYglNPl/NyuvM0zIv4c+acEtEmb6I1Etd/vE3wLV2y3cD3\ntmIsvCN697dQpNiCjNnZrGL0TL8eivgJa06//YI0DLYSIFokbYuHkTyAeDSW\nw5vYi2Me6EDCbqyGjmino/GAQMp8wVf2ShCLl3J0NiWh8ThFSmOqc+TTQi6u\n17OQSJ5nhkrci+EiaBRHbkkphQOj9uZ5jdNBbeGQ3heo/IVcwtIWk+sWtXmO\nYwmq2vrWt2HGsiva59eNq/2Yjts9U2+meRsV2wEDwjJBAUscFWIw9r89O7uk\nlgbjp4AAWjz9BPH0dVkpAX5QBAeWl0/pAF3idtwfcFuyIjMMb5H0rRGZoxau\nFKJtXW9ObtsHFd1PyDKlTLbcAkCrtyQv8Hr48nMZuj6OdOFp21GyxT8kmO1B\nZWKE8S6uKbeWQoAhP+QikXE0+eF0J0mpc4/d9GHIjLQNCzSgwwzwNH0i1vIY\nJJ5ecocqP9UpD5T6gqO3icWROCI8TqrO9fOl0qzYUSfWjmTbFCEIzaQmjUc6\n1o8TjXFz2hmLqxvJRnxXHGke24Y9Ho8vS0//G0AVzML/Anxd5/W/T+j+lPk8\nygjW\r\n=0PMO\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDVuEhJro/oBtAYsdpkHXXpVOlx9LJmneK/YUiW0LFOoAIgBf9/lXCJafLjYAWap5MqQRbyqqTiZASfTPrU/ictvik="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.42_1552418470730_0.6830565882121551"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.43":{"name":"grunt-idra3","version":"0.1.43","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.3","grunt-contrib-clean":"^1.0.0","grunt-eslint":"^21.0.0","grunt-mocha-test":"^0.12.7","mocha":"^5.2.0","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","inquirer":"^3.0.0","mime":"^1.4.1","request":"^2.87.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.19"},"readme":"# idra\n\n> Command Line utility for integrating with IBM® DevOps Insights\n\nTo install this utility\n```\nnpm install -g grunt-idra3\n```\n\n# Table of Contents\n1. [Concepts](#concepts)\n2. [Getting Started](#getting-started)\n 1. [Scenarios](#scenarios)\n 2. [Prerequisites](#prerequisites)\n 3. [Environment Variables](#environment-variables)\n 4. [Enabling Debug Logs](#enabling-debug-logs)\n 5. [Using the CLI](#using-the-cli)\n3. [Upload Build Records](#upload-build-records)\n4. [Upload Test Results](#upload-test-results)\n 1. [Upload SonarQube Results](#upload-sonarqube-results)\n5. [Upload Deployment Records](#upload-deployment-records)\n6. [Making decisions about build quality using gate policies](#making-decisions-about-build-quality-using-gate-policies)\n\n## Concepts\nIBM® DevOps Insights is a tool that provides insights into your DevOps projects. Use it to learn how compliant your team is with DevOps and developer practices, to manage risk in your codebase, and to automatically enforce quality standards in continuous delivery projects.\n\nUnderstanding of the following concepts will help in faster adoption of IBM® DevOps Insights for your projects.\n\n##### Toolchain\nToolchains are part of [IBM® DevOps Continuous Delivery](https://console.bluemix.net/docs/services/ContinuousDelivery/cd_overview.html#cd_overview). Toolchains provide an integrated set of tools to build, deploy and manage your apps. You can create toolchains that include IBM Cloud services, open source tools, and third party tools that make development and operations repeatable and easier to manage. It is required that the IBM DevOps Insights should be added as one of the tool to your toolchain.\n\n##### Integrating your build tool with IBM DevOps Insights\nThis means instrumenting your build tool with this CLI or DevOps Insights Jenkins plugin to send build, test and deployment records to IBM DevOps Insights.\n\n##### Build record\nIBM DevOps Insights needs to know when a build is complete. This record contains application name, branch, build id, reference to git repo and other fields. This CLI and Jenkins plugin has a command to publish the build record to DevOps Insights.\n\n##### Test record\nIBM DevOps Insights needs to know about the tests performed during the build process. It is necessary that the tests should generate some kind of JSON or XML based file. Here are the list of supported [format](supported-test-formats). The generated test file is published as a test record. Along with the test file this record contains application name, build id, type of tests and other fields. It is required that the application name and build id in the test record matches the one used in the build record for a given build. This CLI and Jenkins plugin has a command to publish test record to DevOps Insights.\n\n##### Deployment records\nIBM DevOps Insights needs to know about the deployments made during the deployment process. This record contains the application name, build id, environment name, status of the deployment and other fields. It is required that the application name and build id in the deployment record matches the one used in the build record for a given build. This CLI and Jenkins plugin has a command to publish a deployment to DevOps Insights.\n\n##### Build Id (or Number)\nThis is an arbitrary length string uniquely identifying each build. This id is used to tie the build, test and deployment records together so it is important to publish those records with the same id for a given build.\n\n##### Policy\nA policy is set of rules specified by the user that collectively defines what is considered a good set of test records for a given application build. Typically, one rule is added for each test record published to DevOps Insights. The policy rules are evaluated by the gate.\n\n##### Branch\nThis is the name of the branch in the source control system.\n\n##### Environment\nThis is the name of environment to which deployments are made during the build process.\n\n##### Data set\nThis is an arbitrary string that identifies the type of tests performed during the build process. Besides the standard names such as \"unit test\", \"fvt\". The tool allows the user to define a custom name.\n\n## Getting Started\n\nUse this utility to integrate IBM® DevOps Insights with Travis CI, Concourse, IBM Urban Code Deploy, IBM Continuous Delivery Pipelines and other CI/CD tools. If you are using Jenkins, use this [Jenkins plugin](https://plugins.jenkins.io/ibm-cloud-devops) instead.\n\nUsing this utility, you can\n - Publish build records, test records and deploy records to IBM® DevOps Insights \n - Make go/no-go decisions about a build's quality by using a Gate policy\n\nFor samples of dashboards in IBM® DevOps Insights, see [Value Proposition](https://plugins.jenkins.io/ibm-cloud-devops).\n\nFor more information about IBM DevOps Insights, see [the official documentation](https://console.bluemix.net/docs/services/DevOpsInsights/index.html).\n\n### Scenarios\nThis document covers two scenarios:\n1. You are integrating DevOps Insights with IBM Continuous Delivery tool.\n2. You are integrating DevOps Insights with other CI/CD tools (e.g., Travis CI, Concourse, IBM Urban Code Deploy, others)\n\n### Prerequisites\n\nTo use the CLI, you need to do the following. These steps should take about 10 minutes.\n\n1. A valid IBM Cloud account. If you don't have one, [register here](https://console.bluemix.net/registration).\n\n2. Once you have an account, you can create an API Key. Log in to [IBM Cloud](https://console.bluemix.net). Click on **Manage**->**Security**->**Platform API Key**. On that screen, create an API Key.\n\n3. An IBM Continuous Delivery toolchain. To create a toolchain:\n - Go to https://console.bluemix.net/devops\n - Click on **Create a Toolchain** button and then select **Build Your Own Toolchain** template. \n - In the next screen, click **Create**.\n - From the URL displayed in the browser, make note of your toolchain id. For example, if your URL is https://console.bluemix.net/devops/toolchains/05572df3-01dc-441b-911d-b2202fe33f96, the toolchain id is the long string after **toolchains/**\n - You can always navigate to your toolchain by [clicking here](https://console.bluemix.net/devops)\n\n4. Add DevOps Insights tool to your toolchain\n - Go to your toolchain\n - Click on **Add a Tool** button\n - Select DevOps Insights tool and click **Create Integration** button\n\n5. Your CI/CD tool must have Node.js® 4.x or greater.\n\n### Environment Variables\n\nIf you are using Travis, Concourse or any CI/CD tool other than the IBM Continuous Delivery pipeline, then set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|TOOLCHAIN_ID| **Required.** The toolchain's GUID |\n|IBM_CLOUD_API_KEY| **Required.** The Bluemix user's Api key|\n|BUILD_NUMBER| **Required.** Any string that identifies the build. This value can be passed to the command using the `--buildnumber` parameter, in which case this environment variable is not required. |\n|LOGICAL_APP_NAME| **Required.** The application's name. This value can be passed to the command using the `--logicalappname` parameter, in which case this environment variable should not be set. It is an error to set both the environment variable and the parameter.|\n\nIf you are using IBM Continuous Delivery pipeline, you need to set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|IBM_CLOUD_API_KEY| **Required** The Bluemix user's Api key|\n|BUILD_PREFIX| **Required.** Any string. For example, the Git branch name. If the `--buildnumber` parameter is used to pass a build number then this environment variable is not required.|\n|LOGICAL_APP_NAME| **Required.** The application's name. This value can be passed to the command using the `--logicalappname` parameter, in which case this environment variable should not be set. It is an error to set both the environment variable and the parameter.|\n|PATH|**Required.** In order to have required version of Node.js in your path, set the PATH variable before invoking the utility: `export PATH=/opt/IBM/node-v4.2/bin:$PATH`|\n\nIf you are using IBM Continuous Delivery pipeline and if you want to publish Insights data to another toolchain, then set the following environment variables. \n\n|Name|Description|\n|-----|-----|\n|TOOLCHAIN_ID| **Required.** The target toolchain's GUID. If the target toolchain is owned by different user then provide the target toolchain owner's Bluemix Api key in the `IBM_CLOUD_API_KEY` variable.|\n\n\nIf you are using IBM UrbanCode Deploy, DevOps Insights relies on the previous set of variables, and this one:\n\n|Name|Description|\n|-----|-----|\n|UCD_REQUEST_ID| This maps to the ${p:request.id} property value. |\n\n### Enabling Debug logs\nIf you want to enable debug logs for the DevOps Insights CLI, set the `IDRA_DEBUG` environment variable to `true`. This works in all environments.\n\n|Name|Description|\n|-----|-----|\n|IDRA_DEBUG| When this value is `true`, the DevOps Insights CLI's debugging mode is enabled. By default, the value is `false`. |\n\n\n### Using the CLI\n\nSet [environment details](#environment-details) as described above. Ensure that Node.js 4.2 or higher is avaialble in your CI/CD tool.\n\nTo install this utility, use `npm install -g grunt-idra3`\n\nThen you can invoke the CLI with the `idra` command. You can run the CLI in any pipeline job's command script. For example, this command uploads functional verification test results to DevOps Insights:\n\n```\n# Upload test results\nidra --publishtestresult --filelocation=\"results.json\" --type=fvt\n```\n\n\n## Upload Build Records\nUse the `--publishbuildrecord` command (alias `-b`) to upload build records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishbuildrecord --branch= --repositoryurl= --commitid= --status= --logicalappname= --buildnumber= [--joburl=] [--buildnumber=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--branch`|`-B` | **Required.** The repository branch on which the build is being performed. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--repositoryurl`|`-R` | **Required.** The url of the git repository. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--commitid`|`-C` | **Required.** The git commit id. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--status`|`-S` | **Required.** The build status. This value must be either `pass` or `fail`. |\n|`--logicalappname`|`-L` | **Required.**. The application's name. Specifying this value along with the environment variable **LOGICAL_APP_NAME** is not allowed. |\n|`--buildnumber`|`-N` | **Required.**. Any string that identifies the build. This option overrides the value provided by **BUILD_NUMBER** or **BUILD_PREFIX** environment variables. |\n|`--joburl`|`-J` | _Optional_. The URL to the job's build logs. |\n\n\n\n### An example command\n\nIn this an example, the command uploads a build record from a pipeline job.\n\n```shell\nidra --publishbuildrecord --branch=master --repositoryurl=\"https://github.com/oic/dlms.git\" --commitid=dff7884b9168168d91cb9e5aec78e93db0fa80d9 --status=pass --logicalappname=appname --buildnumber=release:17\n```\n\n## Upload Test Results\n\nUse the `--publishtestresult` command (alias `-p`) to upload results from these test types to DevOps Insights:\n\n* Unit tests\n* Code coverage tests\n* Functional verification tests (FVT)\n* Static security scans from IBM Application Security on Cloud\n* Dynamic app scans from IBM Application Security on Cloud\n* [SonarQube results](#upload-sonarqube-results)\n* [Vulnerability Advisor](https://cloud.ibm.com/docs/services/va)\n\n\n### Command syntax and options\n\n```shell\nidra --publishtestresult --filelocation= --type= --logicalappname= --buildnumber= [--drilldownurl=] [--env=] [--token=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--filelocation`| `-F` |**Required.** The location of the test results that you want to upload. This can be a single file, an entire directory, or multiple files that match a wildcard expression.|\n|`--type`| `-T` |**Required.** The type of test results that you want to upload. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, `sonarqube` for SonarQube scans, and `vulnerabilityadvisor` for Vulnerability Advisor scans. In addition to these types you can also use a custom quality data set tag to upload test results of different type.|\n|`--logicalappname`|`-L` | **Required.**. The application's name. Specifying this value along with the environment variable **LOGICAL_APP_NAME** is not allowed. |\n|`--buildnumber`|`-N` | **Required.**. Any string that identifies the build. This option overrides the value provided by **BUILD_NUMBER** or **BUILD_PREFIX** environment variables. |\n|`--drilldownurl`| `-U` |_Optional._ A URL where more information about the test results can be found. If this URL is invalid, the option is ignored. |\n|`--env`| `-E` |_Optional._ The environment name to associate with the test results. This option is ignored for unit tests, code coverage tests, and static security scans. |\n|`--token`| `-K` |_Optional_. This is a SonarQube token. This flag is valid only if the type specified is `sonarqube`. It is used by the CLI to pull additional information from the SonarQube server. |\n\n### An example command\n\nIn this example, the command uploads all JSON-formatted FVT results from a directory to DevOps Insights. Additionally, a test tool is declared, a test result URL is given, and a logical staging environment is provided. Specifying an environment is especially important when you want your results to be analyzed alongside other activities that take place in that same environment.\n\n```shell\nidra --publishtestresult --filelocation=\"tests/fvt/*.json\" --type=fvt --logicalappname=appname --buildnumber=release:17 -drilldownurl=\"https://example.com/testinfo\" --env=\"staging\" \n```\n\n### Supported Test Formats\n|Type of Test|tag|Supported Formats|\n|-----|-----|-----|\n|Unit Test|`unittest`|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Test Case|`fvt`|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Code Coverage|`code`|Cobertura (xml), lcov, Istanbul, JaCoCo|\n|SonarQube|`sonarqube`|SonarQube|\n|Static Security Scan|`staticsecurityscan`|IBM Application Security on Cloud|\n|Dynamic Security Scan|`dynamicsecurityscan`|IBM Application Security on Cloud|\n|Vulnerability Advisor|`vulnerabilityadvisor`|Output of the command [ibmcloud cr va](https://cloud.ibm.com/docs/cli?topic=container-registry-cli-plugin-containerregcli#bx_cr_va)|\n|Custom Data Sets - Tests|Custom Tag*|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Custom Data Sets - Code Coverage|Custom Tag*|Cobertura (xml), lcov, Istanbul, JaCoCo|\n\nFor golang [gocov](https://github.com/axw/gocov/) users, please convert to Cobertura using [gocov XML(Cobertura) export](https://github.com/yaoyaozong/gocov-xml)\n\n\\* For custom tags create a quality data set by using the user interface. Navigate to your toolchain, click on DevOps Insights card. Navigate to quality dashboard. Click on the Kebab menu which is to the top-right of the quality dashboard. Click on **Configure Quality Data Sets**\n\n### Upload SonarQube Results\nTo upload data from SonarQube, you must provide the SonarQube server token using `--token`. Your SonarQube server is not required to be accessible from your CI/CD tool.\n\nAfter you run a scan using SonarQube, you can upload SonarQube results by running this command.\n\n```\nidra --publishtestresult --filelocation=.scannerwork/report-task.txt --type=sonarqube --token=234234434\n```\n\nIn the above command, report-task.txt is a file generated during the SonarQube scan.\n\nIf this command fails for some reason, you can enable logs by setting IDRA_DEBUG environment variable to true.\n\nIf you are using self-signed certificates for SonarQube server, you will need to set `export NODE_TLS_REJECT_UNAUTHORIZED=0`\n\n## Upload Deployment Records\nUse the `--publishdeployrecord` command (alias `-d`) to upload deployment records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishdeployrecord --env= --status= --joburl= --logicalappname= --buildnumber= [--appurl=] [--deployableid=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--env`|`-E` | **Required.** The environment where the pipeline job deployed the app. |\n|`--status`|`-S` | **Required.** The deployment status. This value must be either `pass` or `fail`. |\n|`--joburl`|`-J` | **Required.** The URL to the job's deployment logs. |\n|`--logicalappname`|`-L` | **Required.**. The application's name. Specifying this value along with the environment variable **LOGICAL_APP_NAME** is not allowed. |\n|`--buildnumber`|`-N` | **Required.**. Any string that identifies the build. This option overrides the value provided by **BUILD_NUMBER** or **BUILD_PREFIX** environment variables. |\n|`--appurl`|`-A` | _Optional._ The URL where the deployed app is running. |\n|`--deployableid`| `-I` | _Optional._ The deployed app's application ID. You can get the ID by running the Cloud Foundry CLI's `cf env` command. The application ID is listed under `VCAP_APPLICATION`. |\n\n### An example command\n\nIn this an example, the command uploads a deployment record from a pipeline job. The deployment is to the \"staging\" environment. The deployment is successful and the app is running at a specified URL.\n\n```shell\nidra --publishdeployrecord --env=\"staging\" --status=pass --joburl=\"https://app.staging.example.com\" --logicalappname=appname --buildnumber=release:17\n```\n\n## Making decisions about build quality using gate policies\n\nTo use this feature, create a quality policy by using the user interface. Navigate to your toolchain, click on **DevOps Insights** card. Then on the left menu, click on **Policies**.\n\nUse the `--evaluategate` command (alias `-g`) to request a gate decision for a DevOps Insights policy in your pipeline. If the policy is satisfied, the pipeline continues running. If not, and you use the `--forcedecision` flag, the pipeline stops running.\n\n### Command syntax and options\n\n```shell\nidra --evaluategate --policy= --logicalappname= --buildnumber= [--forcedecision] [--type=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--policy`|`-P` | **Required.** The name of the policy that the gate uses to make its decision. |\n|`--logicalappname`|`-L` | **Required.**. The application's name. Specifying this value along with the environment variable **LOGICAL_APP_NAME** is not allowed. |\n|`--buildnumber`|`-N` | **Required.**. Any string that identifies the build. This option overrides the value provided by **BUILD_NUMBER** or **BUILD_PREFIX** environment variables. |\n|`--forcedecision`|`-D` | _Optional._ Set the value to `true` to cause the process to exit with an error code, if the policy evaluation fails. The value defaults to `false` if this option is not specified. |\n|`--type`|`-E` | _Optional_. A rule type to consider. If you include this option, only rules of this type are considered in the decision-making process. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, and `sonarqube` for SonarQube scans. |\n\n### An example command\n\n```shell\nidra --evaluategate --policy=\"somepolicy\" --logicalappname=appname --buildnumber=release:17\n```\n\n## Release History\n_(Nothing yet)_\n","readmeFilename":"README.md","_id":"grunt-idra3@0.1.43","_shasum":"8c3482dff9c2ca7183b12ae93990c26c511fc29b","_from":".","_npmVersion":"3.10.3","_nodeVersion":"6.7.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"8c3482dff9c2ca7183b12ae93990c26c511fc29b","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.43.tgz","integrity":"sha512-9hMaa3iLzTlWLvPGwj8VxzjCxV0iBcSTtfW2EVKGa/HmMkbkiVka6EI5svRdK9ljlhVLOBpCAACwNnxvOboB8A==","fileCount":48,"unpackedSize":164969,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJck/wKCRA9TVsSAnZWagAA8bQQAIBuaxu6caY6WUNsiEIy\neGkq2JZ1KoMvI4rmhfDHhoPKtYG0M5EohNW1+dvUWPQyC15lan5KGE2QtjJb\nhiFYQM8rqWzmk5Usah0mp+oVPzLi/nHTnwvX2WxM4iA8VJgO4SM8eBIa/Mm4\nzkgqm3GFIb2n5YDPGMuctwPv6YgQ8NYpmZB8KnnETVI6W5U4SkmiddmJXhe1\nVm4g1s5NIzsfRsZoFnSvnfauh6g+LYGk8ysK/Dvkg35rD942zL0o/E9s2rOk\nWMu8O0V95dJfhXMftM87cjA3xbiz/XKSA+cwz/jKwBNGu2yk1d6ZLh1cMKH9\nwrKWo/NcRifU65NiBIyJ3/C/hR3vbWGcy+Y9fiPnPsIvEKLVr/09H7RIiS8v\n722XX+JTyQZNBjKK3Qm4thbUuEfexwieAYPIcZo0eF0o472Z862WhdnbhAEd\noLk+9Fk2qRs/ijq18zqWSh4DFV7Fmo8jugGslSYYnhhbodEmUUvAy3eA1beS\nsCbZUQHx/UbX8em0FWuvaeeL919sI+1D8QTrU9geUkDKgfguUDIZS5fgMuOI\n+Wh/KIV1NUNNeTbYmC53+K7WjkF7/lXOC83zR0WhdWiTKmySKxpNWZvpbyfq\nwYQ2ih/elYDLnM7rGFcxjb5+InrY//4wa/ZcC/3pqS/4hhRWIs6LA1F+aVYy\nAHZ1\r\n=6g6l\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIF4C9uVLZKwIiqyUzA3sAwFppKvLTB+tbeXFt6oIp/x9AiEAps5SewzzkPhDnF6r6FJdZIlOcerx8kFBsX1W59SjI8E="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.43_1553202185424_0.26617491090209455"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.45":{"name":"grunt-idra3","version":"0.1.45","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.3","grunt-contrib-clean":"^1.0.0","grunt-eslint":"^21.0.0","grunt-mocha-test":"^0.12.7","mocha":"^5.2.0","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","inquirer":"^3.0.0","mime":"^1.4.1","request":"^2.87.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.19"},"_id":"grunt-idra3@0.1.45","_shasum":"e28f8736bb81f20e53aac172c4bd9c424d314867","_from":".","_npmVersion":"3.10.3","_nodeVersion":"6.7.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"e28f8736bb81f20e53aac172c4bd9c424d314867","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.45.tgz","integrity":"sha512-V50pxoKOLmNfvGS3kxanGg8S8fvs9z4j2W+ihmppVqm3hlTQGiNCIE+BWjkdUgnKBm0V73mU4ulNR27TiOxJYQ==","fileCount":48,"unpackedSize":164917,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJclBaECRA9TVsSAnZWagAAtIUP/jjq1DQwHju3uk8KUJXR\nQuH3JDjK2/Rjou3lD5z36SersqyMIlikwwOqbeIbqNc/c9tRNo7JkewoePjr\n3AX8+7pSfdi38I0g1Syo5hop3JKTEUnT9/QFiSLHp2BDGbUHF3JR9fGm2uxL\n6T2Lluw0aN2ZcYViNnHU+rPunDpngDaYD/obe9SV+DPkJmmtUiTZxnhq6ZLN\nmLx3B6EkxS5FvmGfSYi2mKv/MMNZhoN9f3jywHQjgUTe47IGvU901k5jqsXR\nNkoTRIQirsJRrE9ajtDtFuD92eA1OFvr+0iX1OG2MZ94F+0TFDuqyCdgq04E\n388Lc6RUEblbS1yplifg6lOPAf9Y0kPscXaCdF2lQQ8c4vmCzZNNgLb4M8Nf\nNuFsNR7w3Cq/UXp3Ax/a2AFXpkfnAUiaw7QPQDrWRPXKEZWTD9Qk4Pn899H3\nyfVV/fHWifHZB1csoIZJ0NIvhaErzJfsuLOObyF7Ax1imUdWqPD9BYF36+Sl\nc8ElawZeiftcSOsxJw8wdcl9zYhZfz1hTcv34JUJLm1FFQ3maokLkTlqGGzx\nMyOACfz2Aa9xwmq5Wep3FVDNis15DHAgVZiH+pKYwtRb6o8Aq9QaZPTFgs24\nddDxCeBmQ4+a/Oj4za72pUK3kqRk9si39zyq2Y1CcEJs1vJL9M9B7+IS6tEm\nnZ7w\r\n=M9Gm\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIEshykyGx66+R7KH+wrmtQPZ/fjf6qWJVmIuwOJVa9k8AiEAkyf6RIGOVvwgV52mjcUvfeDj0Qol0nPr//2XLxcjgTI="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.45_1553208964090_0.7664875721435755"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.46":{"name":"grunt-idra3","version":"0.1.46","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.3","grunt-contrib-clean":"^1.0.0","grunt-eslint":"^21.0.0","grunt-mocha-test":"^0.12.7","mocha":"^5.2.0","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","inquirer":"^3.0.0","mime":"^1.4.1","request":"^2.87.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.19"},"_id":"grunt-idra3@0.1.46","_shasum":"4245802c6c8842c9c48167232fc2a446c4669587","_from":".","_npmVersion":"3.10.3","_nodeVersion":"6.7.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"4245802c6c8842c9c48167232fc2a446c4669587","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.46.tgz","integrity":"sha512-wTGDurviq6MDvyRAa79USfsdMp7TQ1zAQP1MValB/RKyifCzSuIJg/Is7Tls9w9jLiiRU3I10fQjZscv/oi2OQ==","fileCount":48,"unpackedSize":171746,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJcsQj2CRA9TVsSAnZWagAAAEsP/1FW9BxbGh7uoiWmZfXX\nWzMgt5fze9UvfE8Z86hb+Akn5d51eWFEEfKwp6B0XtBhJoERy9nJuGQZIymT\nSwAvthkHEkHqyKmP+eXRgMyIXVowNaFMmTFBJHYBnpYp7+u2a8JBW7xDk/XI\nvCUHNuHod+svcSCTo3mcCUwS8f4L6yB8uBl4n9mEqYFMA8Yoq1FDImm+zE2M\noOFjebzRfhI3RQ2k+/LvmPG3RHAVuOqGE5c2u49Lh9RSOuXIZdMVwbTJwHD0\nvsiVKFQJ+uRa/fkoXlf0pYDwIy6UaCbHhI9zFRgmxiE0pzKekAoDiucVlXxe\n6cmlDzJlYT/oymtd+lstCXwV6ks3FMJa4DUVDA+BawEBHXVTv2vir06DKeOq\nXHJjjfNhFHK6PkSqYri0ps7wzmMyKKelcuPi9QzL+EQBkEPqKQBMH8hU3mJU\nfIcOaLQinbSRwovJc7doIEdqzPzf2xBOHTaQVI4oLuR+71oNW5aqB8gpj/7w\nEukLaFgNrJAXh90jH4GEGiuZtR165nWTwujnyrXwZEZTuCn6FOVnnhe0KrQM\ndQrAkwcT/x5y8y2hInztX33/3fIYNdwMsrA7+wHw23734F8XodMKk/q2EwT+\nYA/hpSzuSzT7zF5aI8uophlxk8+vJdE/uVxmjb7S6uzTS/7xpwZkvViGcva1\n5Ds4\r\n=xY7/\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDb4jGuNBZJTvnYECb1vGIR0NTQaPJGksJMT8t2+ZssGAIgIDFLU0yTXXiw9sj3yZy3T4W6jQnv3DuoAY9Xzk6eybU="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.46_1555106037719_0.1269797602532199"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.47":{"name":"grunt-idra3","version":"0.1.47","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.3","grunt-contrib-clean":"^1.0.0","grunt-eslint":"^21.0.0","grunt-mocha-test":"^0.12.7","mocha":"^5.2.0","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","inquirer":"^3.0.0","mime":"^1.4.1","request":"^2.87.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.19"},"readme":"# idra\n\n> Command Line utility for integrating with IBM® DevOps Insights\n\nTo install this utility\n```\nnpm install -g grunt-idra3\n```\n\n# Table of Contents\n1. [Concepts](#concepts)\n2. [Getting Started](#getting-started)\n 1. [Scenarios](#scenarios)\n 2. [Prerequisites](#prerequisites)\n 3. [Environment Variables](#environment-variables)\n 4. [Enabling Debug Logs](#enabling-debug-logs)\n 5. [Using the CLI](#using-the-cli)\n3. [Upload Build Records](#upload-build-records)\n4. [Upload Test Results](#upload-test-results)\n 1. [Upload SonarQube Results](#upload-sonarqube-results)\n5. [Upload Deployment Records](#upload-deployment-records)\n6. [Making decisions about build quality using gate policies](#making-decisions-about-build-quality-using-gate-policies)\n\n## Concepts\nIBM® DevOps Insights is a tool that provides insights into your DevOps projects. Use it to learn how compliant your team is with DevOps and developer practices, to manage risk in your codebase, and to automatically enforce quality standards in continuous delivery projects.\n\nUnderstanding of the following concepts will help in faster adoption of IBM® DevOps Insights for your projects.\n\n##### Toolchain\nToolchains are part of [IBM® DevOps Continuous Delivery](https://console.bluemix.net/docs/services/ContinuousDelivery/cd_overview.html#cd_overview). Toolchains provide an integrated set of tools to build, deploy and manage your apps. You can create toolchains that include IBM Cloud services, open source tools, and third party tools that make development and operations repeatable and easier to manage. It is required that the IBM DevOps Insights should be added as one of the tool to your toolchain.\n\n##### Integrating your build tool with IBM DevOps Insights\nThis means instrumenting your build tool with this CLI or DevOps Insights Jenkins plugin to send build, test and deployment records to IBM DevOps Insights.\n\n##### Build record\nIBM DevOps Insights needs to know when a build is complete. This record contains application name, branch, build id, reference to git repo and other fields. This CLI and Jenkins plugin has a command to publish the build record to DevOps Insights.\n\n##### Test record\nIBM DevOps Insights needs to know about the tests performed during the build process. It is necessary that the tests should generate some kind of JSON or XML based file. Here are the list of supported [format](supported-test-formats). The generated test file is published as a test record. Along with the test file this record contains application name, build id, type of tests and other fields. It is required that the application name and build id in the test record matches the one used in the build record for a given build. This CLI and Jenkins plugin has a command to publish test record to DevOps Insights.\n\n##### Deployment records\nIBM DevOps Insights needs to know about the deployments made during the deployment process. This record contains the application name, build id, environment name, status of the deployment and other fields. It is required that the application name and build id in the deployment record matches the one used in the build record for a given build. This CLI and Jenkins plugin has a command to publish a deployment to DevOps Insights.\n\n##### Build Id (or Number)\nThis is an arbitrary length string uniquely identifying each build. This id is used to tie the build, test and deployment records together so it is important to publish those records with the same id for a given build.\n\n##### Policy\nA policy is set of rules specified by the user that collectively defines what is considered a good set of test records for a given application build. Typically, one rule is added for each test record published to DevOps Insights. The policy rules are evaluated by the gate.\n\n##### Branch\nThis is the name of the branch in the source control system.\n\n##### Environment\nThis is the name of environment to which deployments are made during the build process.\n\n##### Data set\nThis is an arbitrary string that identifies the type of tests performed during the build process. Besides the standard names such as \"unit test\", \"fvt\". The tool allows the user to define a custom name.\n\n## Getting Started\n\nUse this utility to integrate IBM® DevOps Insights with Travis CI, Concourse, IBM Urban Code Deploy, IBM Continuous Delivery Pipelines and other CI/CD tools. If you are using Jenkins, use this [Jenkins plugin](https://plugins.jenkins.io/ibm-cloud-devops) instead.\n\nUsing this utility, you can\n - Publish build records, test records and deploy records to IBM® DevOps Insights \n - Make go/no-go decisions about a build's quality by using a Gate policy\n\nFor samples of dashboards in IBM® DevOps Insights, see [Value Proposition](https://plugins.jenkins.io/ibm-cloud-devops).\n\nFor more information about IBM DevOps Insights, see [the official documentation](https://console.bluemix.net/docs/services/DevOpsInsights/index.html).\n\n### Scenarios\nThis document covers two scenarios:\n1. You are integrating DevOps Insights with IBM Continuous Delivery tool.\n2. You are integrating DevOps Insights with other CI/CD tools (e.g., Travis CI, Concourse, IBM Urban Code Deploy, others)\n\n### Prerequisites\n\nTo use the CLI, you need to do the following. These steps should take about 10 minutes.\n\n1. A valid IBM Cloud account. If you don't have one, [register here](https://console.bluemix.net/registration).\n\n2. Once you have an account, you can create an API Key. Log in to [IBM Cloud](https://console.bluemix.net). Click on **Manage**->**Security**->**Platform API Key**. On that screen, create an API Key.\n\n3. An IBM Continuous Delivery toolchain. To create a toolchain:\n - Go to https://console.bluemix.net/devops\n - Click on **Create a Toolchain** button and then select **Build Your Own Toolchain** template. \n - In the next screen, click **Create**.\n - From the URL displayed in the browser, make note of your toolchain id. For example, if your URL is https://console.bluemix.net/devops/toolchains/05572df3-01dc-441b-911d-b2202fe33f96, the toolchain id is the long string after **toolchains/**\n - You can always navigate to your toolchain by [clicking here](https://console.bluemix.net/devops)\n\n4. Add DevOps Insights tool to your toolchain\n - Go to your toolchain\n - Click on **Add a Tool** button\n - Select DevOps Insights tool and click **Create Integration** button\n\n5. Your CI/CD tool must have Node.js® 4.x or greater.\n\n### Environment Variables\n\nIf you are using Travis, Concourse or any CI/CD tool other than the IBM Continuous Delivery pipeline, then set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|TOOLCHAIN_ID| **Required.** The toolchain's GUID |\n|IBM_CLOUD_API_KEY| **Required.** The Bluemix user's Api key|\n|BUILD_NUMBER| **Required.** Any string that identifies the build. You also have the option of specifying build number using the `--buildnumber` parameter, in which case this environment variable is not required. |\n|LOGICAL_APP_NAME| **Required.** The application's name. You also have the option of specifying application's name using the `--logicalappname` parameter, in which case this environment variable must not be set. It is an error to set both the environment variable and the parameter.|\n\nIf you are using IBM Continuous Delivery pipeline, you need to set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|IBM_CLOUD_API_KEY| **Required** The Bluemix user's Api key|\n|BUILD_PREFIX| **Required.** Any string. For example, the Git branch name. If the `--buildnumber` parameter is used to pass a build number then this environment variable is not required.|\n|LOGICAL_APP_NAME| **Required.** The application's name. You also have the option of specifying application's name using the `--logicalappname` parameter, in which case this environment variable must not be set. It is an error to set both the environment variable and the parameter.|\n|PATH|**Required.** In order to have required version of Node.js in your path, set the PATH variable before invoking the utility: `export PATH=/opt/IBM/node-v4.2/bin:$PATH`|\n\nIf you are using IBM Continuous Delivery pipeline and if you want to publish Insights data to another toolchain, then set the following environment variables. \n\n|Name|Description|\n|-----|-----|\n|TOOLCHAIN_ID| **Required.** The target toolchain's GUID. If the target toolchain is owned by different user then provide the target toolchain owner's Bluemix Api key in the `IBM_CLOUD_API_KEY` variable.|\n\n\nIf you are using IBM UrbanCode Deploy, DevOps Insights relies on the previous set of variables, and this one:\n\n|Name|Description|\n|-----|-----|\n|UCD_REQUEST_ID| This maps to the ${p:request.id} property value. |\n\n### Enabling Debug logs\nIf you want to enable debug logs for the DevOps Insights CLI, set the `IDRA_DEBUG` environment variable to `true`. This works in all environments.\n\n|Name|Description|\n|-----|-----|\n|IDRA_DEBUG| When this value is `true`, the DevOps Insights CLI's debugging mode is enabled. By default, the value is `false`. |\n\n\n### Using the CLI\n\nSet [environment details](#environment-details) as described above. Ensure that Node.js 4.2 or higher is avaialble in your CI/CD tool.\n\nTo install this utility, use `npm install -g grunt-idra3`\n\nThen you can invoke the CLI with the `idra` command. You can run the CLI in any pipeline job's command script. For example, this command uploads functional verification test results to DevOps Insights:\n\n```\n# Upload test results\nidra --publishtestresult --filelocation=\"results.json\" --type=fvt\n```\n\n\n## Upload Build Records\nUse the `--publishbuildrecord` command (alias `-b`) to upload build records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishbuildrecord --branch= --repositoryurl= --commitid= --status= --logicalappname= --buildnumber= [--joburl=] [--buildnumber=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--branch`|`-B` | **Required.** The repository branch on which the build is being performed. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--repositoryurl`|`-R` | **Required.** The url of the git repository. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--commitid`|`-C` | **Required.** The git commit id. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--status`|`-S` | **Required.** The build status. This value must be either `pass` or `fail`. |\n|`--logicalappname`|`-L` | _Optional_. The application's name. If this parameter is specified, environment variable **LOGICAL_APP_NAME** must not be set. |\n|`--buildnumber`|`-N` | _Optional_. Any string that identifies the build. This option overrides the value provided by **BUILD_NUMBER** or **BUILD_PREFIX** environment variables. |\n|`--joburl`|`-J` | _Optional_. The URL to the job's build logs. |\n\n\n\n### An example command\n\nIn this an example, the command uploads a build record from a pipeline job.\n\n```shell\nidra --publishbuildrecord --branch=master --repositoryurl=\"https://github.com/oic/dlms.git\" --commitid=dff7884b9168168d91cb9e5aec78e93db0fa80d9 --status=pass --logicalappname=appname --buildnumber=release:17\n```\n\n## Upload Test Results\n\nUse the `--publishtestresult` command (alias `-p`) to upload results from these test types to DevOps Insights:\n\n* Unit tests\n* Code coverage tests\n* Functional verification tests (FVT)\n* Static security scans from IBM Application Security on Cloud\n* Dynamic app scans from IBM Application Security on Cloud\n* [SonarQube results](#upload-sonarqube-results)\n* [Vulnerability Advisor](https://cloud.ibm.com/docs/services/va)\n\n\n### Command syntax and options\n\n```shell\nidra --publishtestresult --filelocation= --type= --logicalappname= --buildnumber= [--drilldownurl=] [--env=] [--token=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--filelocation`| `-F` |**Required.** The location of the test results that you want to upload. This can be a single file, an entire directory, or multiple files that match a wildcard expression.|\n|`--type`| `-T` |**Required.** The type of test results that you want to upload. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, `sonarqube` for SonarQube scans, and `vulnerabilityadvisor` for Vulnerability Advisor scans. In addition to these types you can also use a custom quality data set tag to upload test results of different type.|\n|`--logicalappname`|`-L` | _Optional_. The application's name. If this parameter is specified, environment variable **LOGICAL_APP_NAME** must not be set. |\n|`--buildnumber`|`-N` | _Optional_. Any string that identifies the build. This option overrides the value provided by **BUILD_NUMBER** or **BUILD_PREFIX** environment variables. |\n|`--drilldownurl`| `-U` |_Optional._ A URL where more information about the test results can be found. If this URL is invalid, the option is ignored. |\n|`--env`| `-E` |_Optional._ The environment name to associate with the test results. This option is ignored for unit tests, code coverage tests, and static security scans. |\n|`--token`| `-K` |_Optional_. This is a SonarQube token. This flag is valid only if the type specified is `sonarqube`. It is used by the CLI to pull additional information from the SonarQube server. |\n\n### An example command\n\nIn this example, the command uploads all JSON-formatted FVT results from a directory to DevOps Insights. Additionally, a test tool is declared, a test result URL is given, and a logical staging environment is provided. Specifying an environment is especially important when you want your results to be analyzed alongside other activities that take place in that same environment.\n\n```shell\nidra --publishtestresult --filelocation=\"tests/fvt/*.json\" --type=fvt --logicalappname=appname --buildnumber=release:17 -drilldownurl=\"https://example.com/testinfo\" --env=\"staging\"\n```\n\n### Supported Test Formats\n|Type of Test|tag|Supported Formats|\n|-----|-----|-----|\n|Unit Test|`unittest`|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Test Case|`fvt`|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Code Coverage|`code`|Cobertura (xml), lcov, Istanbul, JaCoCo|\n|SonarQube|`sonarqube`|SonarQube|\n|Static Security Scan|`staticsecurityscan`|IBM Application Security on Cloud|\n|Dynamic Security Scan|`dynamicsecurityscan`|IBM Application Security on Cloud|\n|Vulnerability Advisor|`vulnerabilityadvisor`|JSON output of the command [ibmcloud cr va](https://cloud.ibm.com/docs/cli?topic=container-registry-cli-plugin-containerregcli#bx_cr_va)|\n|Custom Data Sets - Tests|Custom Tag*|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Custom Data Sets - Code Coverage|Custom Tag*|Cobertura (xml), lcov, Istanbul, JaCoCo|\n\nFor golang [gocov](https://github.com/axw/gocov/) users, please convert to Cobertura using [gocov XML(Cobertura) export](https://github.com/yaoyaozong/gocov-xml)\n\n\\* For custom tags create a quality data set by using the user interface. Navigate to your toolchain, click on DevOps Insights card. Navigate to quality dashboard. Click on the Kebab menu which is to the top-right of the quality dashboard. Click on **Configure Quality Data Sets**\n\n### Upload SonarQube Results\nTo upload data from SonarQube, you must provide the SonarQube server token using `--token`. Your SonarQube server is not required to be accessible from your CI/CD tool.\n\nAfter you run a scan using SonarQube, you can upload SonarQube results by running this command.\n\n```\nidra --publishtestresult --filelocation=.scannerwork/report-task.txt --type=sonarqube --token=234234434\n```\n\nIn the above command, report-task.txt is a file generated during the SonarQube scan.\n\nIf this command fails for some reason, you can enable logs by setting IDRA_DEBUG environment variable to true.\n\nIf you are using self-signed certificates for SonarQube server, you will need to set `export NODE_TLS_REJECT_UNAUTHORIZED=0`\n\n## Upload Deployment Records\nUse the `--publishdeployrecord` command (alias `-d`) to upload deployment records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishdeployrecord --env= --status= --joburl= --logicalappname= --buildnumber= [--appurl=] [--deployableid=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--env`|`-E` | **Required.** The environment where the pipeline job deployed the app. |\n|`--status`|`-S` | **Required.** The deployment status. This value must be either `pass` or `fail`. |\n|`--joburl`|`-J` | **Required.** The URL to the job's deployment logs. |\n|`--logicalappname`|`-L` | _Optional_. The application's name. If this parameter is specified, environment variable **LOGICAL_APP_NAME** must not be set. |\n|`--buildnumber`|`-N` | _Optional_. Any string that identifies the build. This option overrides the value provided by **BUILD_NUMBER** or **BUILD_PREFIX** environment variables. |\n|`--appurl`|`-A` | _Optional._ The URL where the deployed app is running. |\n|`--deployableid`| `-I` | _Optional._ The deployed app's application ID. You can get the ID by running the Cloud Foundry CLI's `cf env` command. The application ID is listed under `VCAP_APPLICATION`. |\n\n### An example command\n\nIn this an example, the command uploads a deployment record from a pipeline job. The deployment is to the \"staging\" environment. The deployment is successful and the app is running at a specified URL.\n\n```shell\nidra --publishdeployrecord --env=\"staging\" --status=pass --joburl=\"https://app.staging.example.com\" --logicalappname=appname --buildnumber=release:17\n```\n\n## Making decisions about build quality using gate policies\n\nTo use this feature, create a quality policy by using the user interface. Navigate to your toolchain, click on **DevOps Insights** card. Then on the left menu, click on **Policies**.\n\nUse the `--evaluategate` command (alias `-g`) to request a gate decision for a DevOps Insights policy in your pipeline. If the policy is satisfied, the pipeline continues running. If not, and you use the `--forcedecision` flag, the pipeline stops running.\n\n### Command syntax and options\n\n```shell\nidra --evaluategate --policy= --logicalappname= --buildnumber= [--forcedecision] [--type=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--policy`|`-P` | **Required.** The name of the policy that the gate uses to make its decision. |\n|`--logicalappname`|`-L` | _Optional_. The application's name. If this parameter is specified, environment variable **LOGICAL_APP_NAME** must not be set. |\n|`--buildnumber`|`-N` | _Optional_. Any string that identifies the build. This option overrides the value provided by **BUILD_NUMBER** or **BUILD_PREFIX** environment variables. |\n|`--forcedecision`|`-D` | _Optional._ Set the value to `true` to cause the process to exit with an error code, if the policy evaluation fails. The value defaults to `false` if this option is not specified. |\n|`--type`|`-E` | _Optional_. A rule type to consider. If you include this option, only rules of this type are considered in the decision-making process. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, and `sonarqube` for SonarQube scans. |\n\n### An example command\n\n```shell\nidra --evaluategate --policy=\"somepolicy\" --logicalappname=appname --buildnumber=release:17\n```\n\n## Release History\n_(Nothing yet)_\n","readmeFilename":"README.md","_id":"grunt-idra3@0.1.47","_npmVersion":"6.4.1","_nodeVersion":"10.11.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"integrity":"sha512-ng9cOHt816/wzmsGkYN/eopE1sIwe9NzX+5XuctYIM1JPGc12InaO1nL54/o9RwsZoUhMN1hjPnIDdSWyZ1+RQ==","shasum":"3351615b16dcd860d04eef21d4fefd13ff0805fb","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.47.tgz","fileCount":49,"unpackedSize":221845,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJcx3nBCRA9TVsSAnZWagAAO0EP/RQ/64VaTRLu5UsXw8my\nZ0vbRKnR4BwoO8B2YmTX9yB7PNEUED0MiLH51VUb5ymiabEo38HRkqzMshOw\nHVeNmniZCM2m0hNF+r7m464xYudtQLLqTwFaVyHMgprUhMCodvUYJhI2yFT+\nAfSx9mzXUfqvwdE51ELcx0euIgJC7WcpWiyAc+Um6OCTbCOi2gHwqBR9ajfA\nTIgJAAaNuYFUxlYUqIl6iPckikKQTAZ5kihCq37MZyIYlpwT3yYflqkGF7fh\nqyKePeZCWBYB4hva5UFQEg0FcZX7w3Dqa67qbpBcW2ykqVEMUWSaCKP19t1I\nhNHFKFN0Oz/9KiTUIu3YJeDUTywlK8hC0fqcg4zdLlMJm7BGJ60Rt1v2yyNy\nw0ednLzHaGlZkG/5WG6mWkIpAjD/H6QsuL6T+bu68OGdPbVGBDdQCqZiDdY1\nfDNQsfIcr6ZjrB1ff0Kku4wpEMX7FRVbScHXzagWBZ5gVEuokl/QsWoLTy3s\ns17JbBtsi7/k18yD0r31boE+BQf831gYBaMdDj+qbzvp14+lxAAxG1535U/l\nj7hjI2keFPvaQcT/03Gj9ZDdS3PuGnIifsbH4mCzMLdsFY+wfoJzVvTooGch\nYbGBGsffPh51QbBoKP5hOzfPZiDVJbgSzcikb3XxXKTFXSi9+CJiFZ3efd2c\nA8XW\r\n=zqki\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDwnT4nvDXYjfGggOFO1UgFpSnSlNK6l9Qp9VGMpRjzKwIgGVHkwOJrHE6HAx3e40lfkrA9D6XSTYYU7O+NlAdrX68="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.47_1556576704161_0.5548243903295724"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.48":{"name":"grunt-idra3","version":"0.1.48","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.3","grunt-contrib-clean":"^1.0.0","grunt-eslint":"^21.0.0","grunt-mocha-test":"^0.12.7","mocha":"^5.2.0","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","inquirer":"^3.0.0","mime":"^1.4.1","request":"^2.87.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.19"},"readme":"# idra\n\n> Command Line utility for integrating with IBM® DevOps Insights\n\nTo install this utility\n```\nnpm install -g grunt-idra3\n```\n\n# Table of Contents\n1. [Concepts](#concepts)\n2. [Getting Started](#getting-started)\n 1. [Scenarios](#scenarios)\n 2. [Prerequisites](#prerequisites)\n 3. [Environment Variables](#environment-variables)\n 4. [Enabling Debug Logs](#enabling-debug-logs)\n 5. [Using the CLI](#using-the-cli)\n3. [Upload Build Records](#upload-build-records)\n4. [Upload Test Results](#upload-test-results)\n 1. [Upload SonarQube Results](#upload-sonarqube-results)\n5. [Upload Deployment Records](#upload-deployment-records)\n6. [Making decisions about build quality using gate policies](#making-decisions-about-build-quality-using-gate-policies)\n\n## Concepts\nIBM® DevOps Insights is a tool that provides insights into your DevOps projects. Use it to learn how compliant your team is with DevOps and developer practices, to manage risk in your codebase, and to automatically enforce quality standards in continuous delivery projects.\n\nUnderstanding of the following concepts will help in faster adoption of IBM® DevOps Insights for your projects.\n\n##### Toolchain\nToolchains are part of [IBM® DevOps Continuous Delivery](https://console.bluemix.net/docs/services/ContinuousDelivery/cd_overview.html#cd_overview). Toolchains provide an integrated set of tools to build, deploy and manage your apps. You can create toolchains that include IBM Cloud services, open source tools, and third party tools that make development and operations repeatable and easier to manage. It is required that the IBM DevOps Insights should be added as one of the tool to your toolchain.\n\n##### Integrating your build tool with IBM DevOps Insights\nThis means instrumenting your build tool with this CLI or DevOps Insights Jenkins plugin to send build, test and deployment records to IBM DevOps Insights.\n\n##### Build record\nIBM DevOps Insights needs to know when a build is complete. This record contains application name, branch, build id, reference to git repo and other fields. This CLI and Jenkins plugin has a command to publish the build record to DevOps Insights.\n\n##### Test record\nIBM DevOps Insights needs to know about the tests performed during the build process. It is necessary that the tests should generate some kind of JSON or XML based file. Here are the list of supported [format](supported-test-formats). The generated test file is published as a test record. Along with the test file this record contains application name, build id, type of tests and other fields. It is required that the application name and build id in the test record matches the one used in the build record for a given build. This CLI and Jenkins plugin has a command to publish test record to DevOps Insights.\n\n##### Deployment records\nIBM DevOps Insights needs to know about the deployments made during the deployment process. This record contains the application name, build id, environment name, status of the deployment and other fields. It is required that the application name and build id in the deployment record matches the one used in the build record for a given build. This CLI and Jenkins plugin has a command to publish a deployment to DevOps Insights.\n\n##### Build Id (or Number)\nThis is an arbitrary length string uniquely identifying each build. This id is used to tie the build, test and deployment records together so it is important to publish those records with the same id for a given build.\n\n##### Policy\nA policy is set of rules specified by the user that collectively defines what is considered a good set of test records for a given application build. Typically, one rule is added for each test record published to DevOps Insights. The policy rules are evaluated by the gate.\n\n##### Branch\nThis is the name of the branch in the source control system.\n\n##### Environment\nThis is the name of environment to which deployments are made during the build process.\n\n##### Data set\nThis is an arbitrary string that identifies the type of tests performed during the build process. Besides the standard names such as \"unit test\", \"fvt\". The tool allows the user to define a custom name.\n\n## Getting Started\n\nUse this utility to integrate IBM® DevOps Insights with Travis CI, Concourse, IBM Urban Code Deploy, IBM Continuous Delivery Pipelines and other CI/CD tools. If you are using Jenkins, use this [Jenkins plugin](https://plugins.jenkins.io/ibm-cloud-devops) instead.\n\nUsing this utility, you can\n - Publish build records, test records and deploy records to IBM® DevOps Insights \n - Make go/no-go decisions about a build's quality by using a Gate policy\n\nFor samples of dashboards in IBM® DevOps Insights, see [Value Proposition](https://plugins.jenkins.io/ibm-cloud-devops).\n\nFor more information about IBM DevOps Insights, see [the official documentation](https://console.bluemix.net/docs/services/DevOpsInsights/index.html).\n\n### Scenarios\nThis document covers two scenarios:\n1. You are integrating DevOps Insights with IBM Continuous Delivery tool.\n2. You are integrating DevOps Insights with other CI/CD tools (e.g., Travis CI, Concourse, IBM Urban Code Deploy, others)\n\n### Prerequisites\n\nTo use the CLI, you need to do the following. These steps should take about 10 minutes.\n\n1. A valid IBM Cloud account. If you don't have one, [register here](https://console.bluemix.net/registration).\n\n2. Once you have an account, you can create an API Key. Log in to [IBM Cloud](https://console.bluemix.net). Click on **Manage**->**Security**->**Platform API Key**. On that screen, create an API Key.\n\n3. An IBM Continuous Delivery toolchain. To create a toolchain:\n - Go to https://console.bluemix.net/devops\n - Click on **Create a Toolchain** button and then select **Build Your Own Toolchain** template. \n - In the next screen, click **Create**.\n - From the URL displayed in the browser, make note of your toolchain id. For example, if your URL is https://console.bluemix.net/devops/toolchains/05572df3-01dc-441b-911d-b2202fe33f96, the toolchain id is the long string after **toolchains/**\n - You can always navigate to your toolchain by [clicking here](https://console.bluemix.net/devops)\n\n4. Add DevOps Insights tool to your toolchain\n - Go to your toolchain\n - Click on **Add a Tool** button\n - Select DevOps Insights tool and click **Create Integration** button\n\n5. Your CI/CD tool must have Node.js® 4.x or greater.\n\n### Environment Variables\n\nIf you are using Travis, Concourse or any CI/CD tool other than the IBM Continuous Delivery pipeline, then set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|TOOLCHAIN_ID| **Required.** The toolchain's GUID |\n|IBM_CLOUD_API_KEY| **Required.** The Bluemix user's Api key|\n|BUILD_NUMBER| **Required.** Any string that identifies the build. You also have the option of specifying build number using the `--buildnumber` parameter, in which case this environment variable is not required. |\n|LOGICAL_APP_NAME| **Required.** The application's name. You also have the option of specifying application's name using the `--logicalappname` parameter, in which case this environment variable must not be set. It is an error to set both the environment variable and the parameter.|\n\nIf you are using IBM Continuous Delivery pipeline, you need to set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|IBM_CLOUD_API_KEY| **Required** The Bluemix user's Api key|\n|BUILD_PREFIX| **Required.** Any string. For example, the Git branch name. If the `--buildnumber` parameter is used to pass a build number then this environment variable is not required.|\n|LOGICAL_APP_NAME| **Required.** The application's name. You also have the option of specifying application's name using the `--logicalappname` parameter, in which case this environment variable must not be set. It is an error to set both the environment variable and the parameter.|\n|PATH|**Required.** In order to have required version of Node.js in your path, set the PATH variable before invoking the utility: `export PATH=/opt/IBM/node-v4.2/bin:$PATH`|\n\nIf you are using IBM Continuous Delivery pipeline and if you want to publish Insights data to another toolchain, then set the following environment variables. \n\n|Name|Description|\n|-----|-----|\n|TOOLCHAIN_ID| **Required.** The target toolchain's GUID. If the target toolchain is owned by different user then provide the target toolchain owner's Bluemix Api key in the `IBM_CLOUD_API_KEY` variable.|\n\n\nIf you are using IBM UrbanCode Deploy, DevOps Insights relies on the previous set of variables, and this one:\n\n|Name|Description|\n|-----|-----|\n|UCD_REQUEST_ID| This maps to the ${p:request.id} property value. |\n\n### Enabling Debug logs\nIf you want to enable debug logs for the DevOps Insights CLI, set the `IDRA_DEBUG` environment variable to `true`. This works in all environments.\n\n|Name|Description|\n|-----|-----|\n|IDRA_DEBUG| When this value is `true`, the DevOps Insights CLI's debugging mode is enabled. By default, the value is `false`. |\n\n\n### Using the CLI\n\nSet [environment details](#environment-details) as described above. Ensure that Node.js 4.2 or higher is avaialble in your CI/CD tool.\n\nTo install this utility, use `npm install -g grunt-idra3`\n\nThen you can invoke the CLI with the `idra` command. You can run the CLI in any pipeline job's command script. For example, this command uploads functional verification test results to DevOps Insights:\n\n```\n# Upload test results\nidra --publishtestresult --filelocation=\"results.json\" --type=fvt\n```\n\n\n## Upload Build Records\nUse the `--publishbuildrecord` command (alias `-b`) to upload build records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishbuildrecord --branch= --repositoryurl= --commitid= --status= --logicalappname= --buildnumber= [--joburl=] [--buildnumber=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--branch`|`-B` | **Required.** The repository branch on which the build is being performed. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--repositoryurl`|`-R` | **Required.** The url of the git repository. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--commitid`|`-C` | **Required.** The git commit id. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--status`|`-S` | **Required.** The build status. This value must be either `pass` or `fail`. |\n|`--logicalappname`|`-L` | _Optional_. The application's name. If this parameter is specified, environment variable **LOGICAL_APP_NAME** must not be set. |\n|`--buildnumber`|`-N` | _Optional_. Any string that identifies the build. This option overrides the value provided by **BUILD_NUMBER** or **BUILD_PREFIX** environment variables. |\n|`--joburl`|`-J` | _Optional_. The URL to the job's build logs. |\n\n\n\n### An example command\n\nIn this an example, the command uploads a build record from a pipeline job.\n\n```shell\nidra --publishbuildrecord --branch=master --repositoryurl=\"https://github.com/oic/dlms.git\" --commitid=dff7884b9168168d91cb9e5aec78e93db0fa80d9 --status=pass --logicalappname=appname --buildnumber=release:17\n```\n\n## Upload Test Results\n\nUse the `--publishtestresult` command (alias `-p`) to upload results from these test types to DevOps Insights:\n\n* Unit tests\n* Code coverage tests\n* Functional verification tests (FVT)\n* Static security scans from IBM Application Security on Cloud\n* Dynamic app scans from IBM Application Security on Cloud\n* [SonarQube results](#upload-sonarqube-results)\n* [Vulnerability Advisor](https://cloud.ibm.com/docs/services/va)\n\n\n### Command syntax and options\n\n```shell\nidra --publishtestresult --filelocation= --type= --logicalappname= --buildnumber= [--drilldownurl=] [--env=] [--token=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--filelocation`| `-F` |**Required.** The location of the test results that you want to upload. This can be a single file, an entire directory, or multiple files that match a wildcard expression.|\n|`--type`| `-T` |**Required.** The type of test results that you want to upload. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, `sonarqube` for SonarQube scans, and `vulnerabilityadvisor` for Vulnerability Advisor scans. In addition to these types you can also use a custom quality data set tag to upload test results of different type.|\n|`--logicalappname`|`-L` | _Optional_. The application's name. If this parameter is specified, environment variable **LOGICAL_APP_NAME** must not be set. |\n|`--buildnumber`|`-N` | _Optional_. Any string that identifies the build. This option overrides the value provided by **BUILD_NUMBER** or **BUILD_PREFIX** environment variables. |\n|`--drilldownurl`| `-U` |_Optional._ A URL where more information about the test results can be found. If this URL is invalid, the option is ignored. |\n|`--env`| `-E` |_Optional._ The environment name to associate with the test results. This option is ignored for unit tests, code coverage tests, and static security scans. |\n|`--token`| `-K` |_Optional_. This is a SonarQube token. This flag is valid only if the type specified is `sonarqube`. It is used by the CLI to pull additional information from the SonarQube server. |\n\n### An example command\n\nIn this example, the command uploads all JSON-formatted FVT results from a directory to DevOps Insights. Additionally, a test tool is declared, a test result URL is given, and a logical staging environment is provided. Specifying an environment is especially important when you want your results to be analyzed alongside other activities that take place in that same environment.\n\n```shell\nidra --publishtestresult --filelocation=\"tests/fvt/*.json\" --type=fvt --logicalappname=appname --buildnumber=release:17 -drilldownurl=\"https://example.com/testinfo\" --env=\"staging\"\n```\n\n### Supported Test Formats\n|Type of Test|tag|Supported Formats|\n|-----|-----|-----|\n|Unit Test|`unittest`|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Test Case|`fvt`|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Code Coverage|`code`|Cobertura (xml), lcov, Istanbul, JaCoCo|\n|SonarQube|`sonarqube`|SonarQube|\n|Static Security Scan|`staticsecurityscan`|IBM Application Security on Cloud|\n|Dynamic Security Scan|`dynamicsecurityscan`|IBM Application Security on Cloud|\n|Vulnerability Advisor|`vulnerabilityadvisor`|JSON output of the command [ibmcloud cr va](https://cloud.ibm.com/docs/cli?topic=container-registry-cli-plugin-containerregcli#bx_cr_va)|\n|Custom Data Sets - Tests|Custom Tag*|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Custom Data Sets - Code Coverage|Custom Tag*|Cobertura (xml), lcov, Istanbul, JaCoCo|\n\nFor golang [gocov](https://github.com/axw/gocov/) users, please convert to Cobertura using [gocov XML(Cobertura) export](https://github.com/yaoyaozong/gocov-xml)\n\n\\* For custom tags create a quality data set by using the user interface. Navigate to your toolchain, click on DevOps Insights card. Navigate to quality dashboard. Click on the Kebab menu which is to the top-right of the quality dashboard. Click on **Configure Quality Data Sets**\n\n### Upload SonarQube Results\nTo upload data from SonarQube, you must provide the SonarQube server token using `--token`. Your SonarQube server is not required to be accessible from your CI/CD tool.\n\nAfter you run a scan using SonarQube, you can upload SonarQube results by running this command.\n\n```\nidra --publishtestresult --filelocation=.scannerwork/report-task.txt --type=sonarqube --token=234234434\n```\n\nIn the above command, report-task.txt is a file generated during the SonarQube scan.\n\nIf this command fails for some reason, you can enable logs by setting IDRA_DEBUG environment variable to true.\n\nIf you are using self-signed certificates for SonarQube server, you will need to set `export NODE_TLS_REJECT_UNAUTHORIZED=0`\n\n## Upload Deployment Records\nUse the `--publishdeployrecord` command (alias `-d`) to upload deployment records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishdeployrecord --env= --status= --joburl= --logicalappname= --buildnumber= [--appurl=] [--deployableid=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--env`|`-E` | **Required.** The environment where the pipeline job deployed the app. |\n|`--status`|`-S` | **Required.** The deployment status. This value must be either `pass` or `fail`. |\n|`--joburl`|`-J` | **Required.** The URL to the job's deployment logs. |\n|`--logicalappname`|`-L` | _Optional_. The application's name. If this parameter is specified, environment variable **LOGICAL_APP_NAME** must not be set. |\n|`--buildnumber`|`-N` | _Optional_. Any string that identifies the build. This option overrides the value provided by **BUILD_NUMBER** or **BUILD_PREFIX** environment variables. |\n|`--appurl`|`-A` | _Optional._ The URL where the deployed app is running. |\n|`--deployableid`| `-I` | _Optional._ The deployed app's application ID. You can get the ID by running the Cloud Foundry CLI's `cf env` command. The application ID is listed under `VCAP_APPLICATION`. |\n\n### An example command\n\nIn this an example, the command uploads a deployment record from a pipeline job. The deployment is to the \"staging\" environment. The deployment is successful and the app is running at a specified URL.\n\n```shell\nidra --publishdeployrecord --env=\"staging\" --status=pass --joburl=\"https://app.staging.example.com\" --logicalappname=appname --buildnumber=release:17\n```\n\n## Making decisions about build quality using gate policies\n\nTo use this feature, create a quality policy by using the user interface. Navigate to your toolchain, click on **DevOps Insights** card. Then on the left menu, click on **Policies**.\n\nUse the `--evaluategate` command (alias `-g`) to request a gate decision for a DevOps Insights policy in your pipeline. If the policy is satisfied, the pipeline continues running. If not, and you use the `--forcedecision` flag, the pipeline stops running.\n\n### Command syntax and options\n\n```shell\nidra --evaluategate --policy= --logicalappname= --buildnumber= [--forcedecision] [--type=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--policy`|`-P` | **Required.** The name of the policy that the gate uses to make its decision. |\n|`--logicalappname`|`-L` | _Optional_. The application's name. If this parameter is specified, environment variable **LOGICAL_APP_NAME** must not be set. |\n|`--buildnumber`|`-N` | _Optional_. Any string that identifies the build. This option overrides the value provided by **BUILD_NUMBER** or **BUILD_PREFIX** environment variables. |\n|`--forcedecision`|`-D` | _Optional._ Set the value to `true` to cause the process to exit with an error code, if the policy evaluation fails. The value defaults to `false` if this option is not specified. |\n|`--type`|`-E` | _Optional_. A rule type to consider. If you include this option, only rules of this type are considered in the decision-making process. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, and `sonarqube` for SonarQube scans. |\n\n### An example command\n\n```shell\nidra --evaluategate --policy=\"somepolicy\" --logicalappname=appname --buildnumber=release:17\n```\n\n## Release History\n_(Nothing yet)_\n","readmeFilename":"README.md","_id":"grunt-idra3@0.1.48","_shasum":"3b6e3427b07ee847503aaaf94facb2c5209a1f1f","_from":".","_npmVersion":"3.10.3","_nodeVersion":"6.7.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"3b6e3427b07ee847503aaaf94facb2c5209a1f1f","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.48.tgz","integrity":"sha512-eNYA2T9THZ3oZuPH++hK0Y4PrDohzWW/D26SSe4c3FfOjnsWl2dJQw8z8yPBE33EOVlAw/UOpoMAHSj7iyxHfw==","fileCount":48,"unpackedSize":171495,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJcyL60CRA9TVsSAnZWagAA3/kP+QHGe8stMY40xybGq4Dp\nFvSAW2YfPKtbykkI1EiXhr7YVjnZt2P2LFypbnH/jVOm1LDxGNuBjUth7RCg\nt+9MH3QAgUkfGlHAGN98dlOqdW51budmDjvgSgdqlK87xDsbeOLGpDpjo8ix\n/goIz52rmzCTDUHDymyhxw/AeNwYhsxxwuMZP5NbvZCeqkc55un8UOpvXSOq\nme8dntfLqXJocww+YICQ2cCilC7Pg4rVmBlPz4zSQLdOx6bAp8T5a1lQBPpW\nQqd/DGRf0QwkZ/gASXl8CamlXNBEkVtd2i5Pc7BXwusBgyjTHRK7VlBlZfZ+\nJCAsicxu4Kd1W2yaipNJ3sK11ZR3OW+RblX5fwov2PY50+ttHWjkwix9aXkc\nXkaNJ+9RmnPaUr6M5oy7AHSX3lzSZ3htSOWkLHgipL6kMVFhlmDBKyYE/tI3\nI/ZTLJjclg7X6lELJAo9iKpS2p3ot/cpk/vhpN8C8Aum1czi+pYDY/NIFbzy\nI+mEvzpe7c7iiFUpcDvztO9MZL3EtxDzmUVt2a2nksSpcyf/F+UEnBvuy8a3\n6s+cCPED7d9mhOkY371ICR77yZvXrwNU7N9Q8UoD6u1nA0P9okXXNXy/ulBF\n102J21HMPjpvUlFAFC11lAq/A3ShzbHXvKhLdexJOlAHhfgINE0IMVn4W6zJ\n6GNj\r\n=t/1B\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIEtjmJdGi6kN2b6ipdGo/CcH1DEbI/ek9bP/rcjH8BRgAiEAiPOO/JhC3qYp3hfEXthc72qJ9z6QSwdffHVrnhUfr+o="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.48_1556659892167_0.03542949062151557"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.49":{"name":"grunt-idra3","version":"0.1.49","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.3","grunt-contrib-clean":"^1.0.0","grunt-eslint":"^21.0.0","grunt-mocha-test":"^0.12.7","mocha":"^5.2.0","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","inquirer":"^3.0.0","mime":"^1.4.1","request":"^2.87.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.19"},"readme":"# idra\n\n> Command Line utility for integrating with IBM® DevOps Insights\n\nTo install this utility\n```\nnpm install -g grunt-idra3\n```\n\n# Table of Contents\n1. [Concepts](#concepts)\n2. [Getting Started](#getting-started)\n 1. [Scenarios](#scenarios)\n 2. [Prerequisites](#prerequisites)\n 3. [Environment Variables](#environment-variables)\n 4. [Enabling Debug Logs](#enabling-debug-logs)\n 5. [Using the CLI](#using-the-cli)\n3. [Upload Build Records](#upload-build-records)\n4. [Upload Test Results](#upload-test-results)\n 1. [Upload SonarQube Results](#upload-sonarqube-results)\n5. [Upload Deployment Records](#upload-deployment-records)\n6. [Making decisions about build quality using gate policies](#making-decisions-about-build-quality-using-gate-policies)\n\n## Concepts\nIBM® DevOps Insights is a tool that provides insights into your DevOps projects. Use it to learn how compliant your team is with DevOps and developer practices, to manage risk in your codebase, and to automatically enforce quality standards in continuous delivery projects.\n\nUnderstanding of the following concepts will help in faster adoption of IBM® DevOps Insights for your projects.\n\n##### Toolchain\nToolchains are part of [IBM® DevOps Continuous Delivery](https://console.bluemix.net/docs/services/ContinuousDelivery/cd_overview.html#cd_overview). Toolchains provide an integrated set of tools to build, deploy and manage your apps. You can create toolchains that include IBM Cloud services, open source tools, and third party tools that make development and operations repeatable and easier to manage. It is required that the IBM DevOps Insights should be added as one of the tool to your toolchain.\n\n##### Integrating your build tool with IBM DevOps Insights\nThis means instrumenting your build tool with this CLI or DevOps Insights Jenkins plugin to send build, test and deployment records to IBM DevOps Insights.\n\n##### Build record\nIBM DevOps Insights needs to know when a build is complete. This record contains application name, branch, build id, reference to git repo and other fields. This CLI and Jenkins plugin has a command to publish the build record to DevOps Insights.\n\n##### Test record\nIBM DevOps Insights needs to know about the tests performed during the build process. It is necessary that the tests should generate some kind of JSON or XML based file. Here are the list of supported [format](supported-test-formats). The generated test file is published as a test record. Along with the test file this record contains application name, build id, type of tests and other fields. It is required that the application name and build id in the test record matches the one used in the build record for a given build. This CLI and Jenkins plugin has a command to publish test record to DevOps Insights.\n\n##### Deployment records\nIBM DevOps Insights needs to know about the deployments made during the deployment process. This record contains the application name, build id, environment name, status of the deployment and other fields. It is required that the application name and build id in the deployment record matches the one used in the build record for a given build. This CLI and Jenkins plugin has a command to publish a deployment to DevOps Insights.\n\n##### Build Id (or Number)\nThis is an arbitrary length string uniquely identifying each build. This id is used to tie the build, test and deployment records together so it is important to publish those records with the same id for a given build.\n\n##### Policy\nA policy is set of rules specified by the user that collectively defines what is considered a good set of test records for a given application build. Typically, one rule is added for each test record published to DevOps Insights. The policy rules are evaluated by the gate.\n\n##### Branch\nThis is the name of the branch in the source control system.\n\n##### Environment\nThis is the name of environment to which deployments are made during the build process.\n\n##### Data set\nThis is an arbitrary string that identifies the type of tests performed during the build process. Besides the standard names such as \"unit test\", \"fvt\". The tool allows the user to define a custom name.\n\n## Getting Started\n\nUse this utility to integrate IBM® DevOps Insights with Travis CI, Concourse, IBM Urban Code Deploy, IBM Continuous Delivery Pipelines and other CI/CD tools. If you are using Jenkins, use this [Jenkins plugin](https://plugins.jenkins.io/ibm-cloud-devops) instead.\n\nUsing this utility, you can\n - Publish build records, test records and deploy records to IBM® DevOps Insights \n - Make go/no-go decisions about a build's quality by using a Gate policy\n\nFor samples of dashboards in IBM® DevOps Insights, see [Value Proposition](https://plugins.jenkins.io/ibm-cloud-devops).\n\nFor more information about IBM DevOps Insights, see [the official documentation](https://console.bluemix.net/docs/services/DevOpsInsights/index.html).\n\n### Scenarios\nThis document covers two scenarios:\n1. You are integrating DevOps Insights with IBM Continuous Delivery tool.\n2. You are integrating DevOps Insights with other CI/CD tools (e.g., Travis CI, Concourse, IBM Urban Code Deploy, others)\n\n### Prerequisites\n\nTo use the CLI, you need to do the following. These steps should take about 10 minutes.\n\n1. A valid IBM Cloud account. If you don't have one, [register here](https://console.bluemix.net/registration).\n\n2. Once you have an account, you can create an API Key. Log in to [IBM Cloud](https://console.bluemix.net). Click on **Manage**->**Security**->**Platform API Key**. On that screen, create an API Key.\n\n3. An IBM Continuous Delivery toolchain. To create a toolchain:\n - Go to https://console.bluemix.net/devops\n - Click on **Create a Toolchain** button and then select **Build Your Own Toolchain** template. \n - In the next screen, click **Create**.\n - From the URL displayed in the browser, make note of your toolchain id. For example, if your URL is https://console.bluemix.net/devops/toolchains/05572df3-01dc-441b-911d-b2202fe33f96, the toolchain id is the long string after **toolchains/**\n - You can always navigate to your toolchain by [clicking here](https://console.bluemix.net/devops)\n\n4. Add DevOps Insights tool to your toolchain\n - Go to your toolchain\n - Click on **Add a Tool** button\n - Select DevOps Insights tool and click **Create Integration** button\n\n5. Your CI/CD tool must have Node.js® 4.x or greater.\n\n### Environment Variables\n\nIf you are using Travis, Concourse or any CI/CD tool other than the IBM Continuous Delivery pipeline, then set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|TOOLCHAIN_ID| **Required.** The toolchain's GUID |\n|IBM_CLOUD_API_KEY| **Required.** The Bluemix user's Api key|\n|BUILD_NUMBER| **Required.** Any string that identifies the build. You also have the option of specifying build number using the `--buildnumber` parameter, in which case this environment variable is not required. |\n|LOGICAL_APP_NAME| **Required.** The application's name. You also have the option of specifying application's name using the `--logicalappname` parameter, in which case this environment variable must not be set. It is an error to set both the environment variable and the parameter.|\n\nIf you are using IBM Continuous Delivery pipeline, you need to set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|IBM_CLOUD_API_KEY| **Required** The Bluemix user's Api key|\n|BUILD_PREFIX| **Required.** Any string. For example, the Git branch name. If the `--buildnumber` parameter is used to pass a build number then this environment variable is not required.|\n|LOGICAL_APP_NAME| **Required.** The application's name. You also have the option of specifying application's name using the `--logicalappname` parameter, in which case this environment variable must not be set. It is an error to set both the environment variable and the parameter.|\n|PATH|**Required.** In order to have required version of Node.js in your path, set the PATH variable before invoking the utility: `export PATH=/opt/IBM/node-v4.2/bin:$PATH`|\n\nIf you are using IBM Continuous Delivery pipeline and if you want to publish Insights data to another toolchain, then set the following environment variables. \n\n|Name|Description|\n|-----|-----|\n|TOOLCHAIN_ID| **Required.** The target toolchain's GUID. If the target toolchain is owned by different user then provide the target toolchain owner's Bluemix Api key in the `IBM_CLOUD_API_KEY` variable.|\n\n\nIf you are using IBM UrbanCode Deploy, DevOps Insights relies on the previous set of variables, and this one:\n\n|Name|Description|\n|-----|-----|\n|UCD_REQUEST_ID| This maps to the ${p:request.id} property value. |\n\n### Enabling Debug logs\nIf you want to enable debug logs for the DevOps Insights CLI, set the `IDRA_DEBUG` environment variable to `true`. This works in all environments.\n\n|Name|Description|\n|-----|-----|\n|IDRA_DEBUG| When this value is `true`, the DevOps Insights CLI's debugging mode is enabled. By default, the value is `false`. |\n\n\n### Using the CLI\n\nSet [environment details](#environment-details) as described above. Ensure that Node.js 4.2 or higher is avaialble in your CI/CD tool.\n\nTo install this utility, use `npm install -g grunt-idra3`\n\nThen you can invoke the CLI with the `idra` command. You can run the CLI in any pipeline job's command script. For example, this command uploads functional verification test results to DevOps Insights:\n\n```\n# Upload test results\nidra --publishtestresult --filelocation=\"results.json\" --type=fvt\n```\n\n\n## Upload Build Records\nUse the `--publishbuildrecord` command (alias `-b`) to upload build records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishbuildrecord --branch= --repositoryurl= --commitid= --status= --logicalappname= --buildnumber= [--joburl=] [--buildnumber=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--branch`|`-B` | **Required.** The repository branch on which the build is being performed. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--repositoryurl`|`-R` | **Required.** The url of the git repository. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--commitid`|`-C` | **Required.** The git commit id. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--status`|`-S` | **Required.** The build status. This value must be either `pass` or `fail`. |\n|`--logicalappname`|`-L` | _Optional_. The application's name. If this parameter is specified, environment variable **LOGICAL_APP_NAME** must not be set. |\n|`--buildnumber`|`-N` | _Optional_. Any string that identifies the build. This option overrides the value provided by **BUILD_NUMBER** or **BUILD_PREFIX** environment variables. |\n|`--joburl`|`-J` | _Optional_. The URL to the job's build logs. |\n\n\n\n### An example command\n\nIn this an example, the command uploads a build record from a pipeline job.\n\n```shell\nidra --publishbuildrecord --branch=master --repositoryurl=\"https://github.com/oic/dlms.git\" --commitid=dff7884b9168168d91cb9e5aec78e93db0fa80d9 --status=pass --logicalappname=appname --buildnumber=release:17\n```\n\n## Upload Test Results\n\nUse the `--publishtestresult` command (alias `-p`) to upload results from these test types to DevOps Insights:\n\n* Unit tests\n* Code coverage tests\n* Functional verification tests (FVT)\n* Static security scans from IBM Application Security on Cloud\n* Dynamic app scans from IBM Application Security on Cloud\n* [SonarQube results](#upload-sonarqube-results)\n* [Vulnerability Advisor](https://cloud.ibm.com/docs/services/va)\n\n\n### Command syntax and options\n\n```shell\nidra --publishtestresult --filelocation= --type= --logicalappname= --buildnumber= [--drilldownurl=] [--env=] [--token=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--filelocation`| `-F` |**Required.** The location of the test results that you want to upload. This can be a single file, an entire directory, or multiple files that match a wildcard expression.|\n|`--type`| `-T` |**Required.** The type of test results that you want to upload. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, `sonarqube` for SonarQube scans, and `vulnerabilityadvisor` for Vulnerability Advisor scans. In addition to these types you can also use a custom quality data set tag to upload test results of different type.|\n|`--logicalappname`|`-L` | _Optional_. The application's name. If this parameter is specified, environment variable **LOGICAL_APP_NAME** must not be set. |\n|`--buildnumber`|`-N` | _Optional_. Any string that identifies the build. This option overrides the value provided by **BUILD_NUMBER** or **BUILD_PREFIX** environment variables. |\n|`--drilldownurl`| `-U` |_Optional._ A URL where more information about the test results can be found. If this URL is invalid, the option is ignored. |\n|`--env`| `-E` |_Optional._ The environment name to associate with the test results. This option is ignored for unit tests, code coverage tests, and static security scans. |\n|`--token`| `-K` |_Optional_. This is a SonarQube token. This flag is valid only if the type specified is `sonarqube`. It is used by the CLI to pull additional information from the SonarQube server. |\n\n### An example command\n\nIn this example, the command uploads all JSON-formatted FVT results from a directory to DevOps Insights. Additionally, a test tool is declared, a test result URL is given, and a logical staging environment is provided. Specifying an environment is especially important when you want your results to be analyzed alongside other activities that take place in that same environment.\n\n```shell\nidra --publishtestresult --filelocation=\"tests/fvt/*.json\" --type=fvt --logicalappname=appname --buildnumber=release:17 -drilldownurl=\"https://example.com/testinfo\" --env=\"staging\"\n```\n\n### Supported Test Formats\n|Type of Test|tag|Supported Formats|\n|-----|-----|-----|\n|Unit Test|`unittest`|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Test Case|`fvt`|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Code Coverage|`code`|Cobertura (xml), lcov, Istanbul, JaCoCo|\n|SonarQube|`sonarqube`|SonarQube|\n|Static Security Scan|`staticsecurityscan`|IBM Application Security on Cloud|\n|Dynamic Security Scan|`dynamicsecurityscan`|IBM Application Security on Cloud|\n|Vulnerability Advisor|`vulnerabilityadvisor`|JSON output of the command [ibmcloud cr va](https://cloud.ibm.com/docs/cli?topic=container-registry-cli-plugin-containerregcli#bx_cr_va)|\n|Custom Data Sets - Tests|Custom Tag*|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Custom Data Sets - Code Coverage|Custom Tag*|Cobertura (xml), lcov, Istanbul, JaCoCo|\n\nFor golang [gocov](https://github.com/axw/gocov/) users, please convert to Cobertura using [gocov XML(Cobertura) export](https://github.com/yaoyaozong/gocov-xml)\n\n\\* For custom tags create a quality data set by using the user interface. Navigate to your toolchain, click on DevOps Insights card. Navigate to quality dashboard. Click on the Kebab menu which is to the top-right of the quality dashboard. Click on **Configure Quality Data Sets**\n\n### Upload SonarQube Results\nTo upload data from SonarQube, you must provide the SonarQube server token using `--token`. Your SonarQube server is not required to be accessible from your CI/CD tool.\n\nAfter you run a scan using SonarQube, you can upload SonarQube results by running this command.\n\n```\nidra --publishtestresult --filelocation=.scannerwork/report-task.txt --type=sonarqube --token=234234434\n```\n\nIn the above command, report-task.txt is a file generated during the SonarQube scan.\n\nIf this command fails for some reason, you can enable logs by setting IDRA_DEBUG environment variable to true.\n\nIf you are using self-signed certificates for SonarQube server, you will need to set `export NODE_TLS_REJECT_UNAUTHORIZED=0`\n\n## Upload Deployment Records\nUse the `--publishdeployrecord` command (alias `-d`) to upload deployment records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishdeployrecord --env= --status= --joburl= --logicalappname= --buildnumber= [--appurl=] [--deployableid=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--env`|`-E` | **Required.** The environment where the pipeline job deployed the app. |\n|`--status`|`-S` | **Required.** The deployment status. This value must be either `pass` or `fail`. |\n|`--joburl`|`-J` | **Required.** The URL to the job's deployment logs. |\n|`--logicalappname`|`-L` | _Optional_. The application's name. If this parameter is specified, environment variable **LOGICAL_APP_NAME** must not be set. |\n|`--buildnumber`|`-N` | _Optional_. Any string that identifies the build. This option overrides the value provided by **BUILD_NUMBER** or **BUILD_PREFIX** environment variables. |\n|`--appurl`|`-A` | _Optional._ The URL where the deployed app is running. |\n|`--deployableid`| `-I` | _Optional._ The deployed app's application ID. You can get the ID by running the Cloud Foundry CLI's `cf env` command. The application ID is listed under `VCAP_APPLICATION`. |\n\n### An example command\n\nIn this an example, the command uploads a deployment record from a pipeline job. The deployment is to the \"staging\" environment. The deployment is successful and the app is running at a specified URL.\n\n```shell\nidra --publishdeployrecord --env=\"staging\" --status=pass --joburl=\"https://app.staging.example.com\" --logicalappname=appname --buildnumber=release:17\n```\n\n## Making decisions about build quality using gate policies\n\nTo use this feature, create a quality policy by using the user interface. Navigate to your toolchain, click on **DevOps Insights** card. Then on the left menu, click on **Policies**.\n\nUse the `--evaluategate` command (alias `-g`) to request a gate decision for a DevOps Insights policy in your pipeline. If the policy is satisfied, the pipeline continues running. If not, and you use the `--forcedecision` flag, the pipeline stops running.\n\n### Command syntax and options\n\n```shell\nidra --evaluategate --policy= --logicalappname= --buildnumber= [--forcedecision] [--type=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--policy`|`-P` | **Required.** The name of the policy that the gate uses to make its decision. |\n|`--logicalappname`|`-L` | _Optional_. The application's name. If this parameter is specified, environment variable **LOGICAL_APP_NAME** must not be set. |\n|`--buildnumber`|`-N` | _Optional_. Any string that identifies the build. This option overrides the value provided by **BUILD_NUMBER** or **BUILD_PREFIX** environment variables. |\n|`--forcedecision`|`-D` | _Optional._ Set the value to `true` to cause the process to exit with an error code, if the policy evaluation fails. The value defaults to `false` if this option is not specified. |\n|`--type`|`-E` | _Optional_. A rule type to consider. If you include this option, only rules of this type are considered in the decision-making process. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, and `sonarqube` for SonarQube scans. |\n\n### An example command\n\n```shell\nidra --evaluategate --policy=\"somepolicy\" --logicalappname=appname --buildnumber=release:17\n```\n\n## Release History\n_(Nothing yet)_\n","readmeFilename":"README.md","_id":"grunt-idra3@0.1.49","_shasum":"c4d1dd1950ae547891d18682c8e0980a6449880c","_from":".","_npmVersion":"3.10.3","_nodeVersion":"6.7.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"c4d1dd1950ae547891d18682c8e0980a6449880c","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.49.tgz","integrity":"sha512-KSB2ZJq4SeVFH+dBZocQrqg704H/IPsfSW18ccOPdRmMXlT+Q4n+i3kNuXxM/9YlZsJK3U6jOZG+XkDNzZOBLA==","fileCount":48,"unpackedSize":171487,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJcyNfsCRA9TVsSAnZWagAAymIP/016QXJVhlZGrU9P8vTh\npDQwEmY2WfOEEsQuSmGLpf85miqu9Co3vEDz4xyrZHBp1fueCQt34Yd864a/\nYsmH0dSUZi/q3AYF+0e/lGPd9ScD9otwYkmbmzGPkZbNI1EdtMpcvK6NK/0S\ngzOBz0UXTWh69wI0LJxF+kh5rI94fHrCOIu0+prqFbeopkXpRnug5gUNYBIh\nMQc7CKd4K8folL8Bl27VZuLQ6ixykvaYwso9mjO8OZHTHrzMFVDL9DKbFZkh\nnxWFLoFIQa29b4D5WPq9Psz/RMQNqkyD1H2f0T2kqguI3rzSRTj5S3xBJCOV\nwJfoyqIL+UoF0M4BfrR3VTDZlZQDfTMxb1uLIZubc5jRKMD193dDAKDHAEZh\nW7QDcBCZrNJXndOBWVt1Fj52C90Qo1hF6m6Az2LAyOAm3BjfB2BWvn1oyWK0\n8WbEsMo5s7XWg0T+jfgKbZIXCtZSYKdLrpAVnh1Zq65EWgHw9/X+0rZKn08M\nkBFXozRkmWJmkLUx5168Lt3Czfz5/wU0vZCs42nhQV+xLH2fOj+l3NyR0rWq\nvOPx/Di6m+i+5DXpDbU3WIOx5IoEqIOcQgjZSEBva7LzRC1yHm5wIRfWV9WT\nH7/sUs/JjyHEQ08IdBrkzkPdZ2n9uuo6LbB5EcCTzvjV67muB38qW3T0bEDQ\nf0h3\r\n=snWI\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIHmJ/WNdQTnv0+r6hLisePaWEsneia4mda+Mn8pAWjQLAiEAhaTzOxB9ArSWuEc4v+Hd/dZ72lhIJeDCvvl6gzC8aJI="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.49_1556666347618_0.15924286323670356"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.50":{"name":"grunt-idra3","version":"0.1.50","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.3","grunt-contrib-clean":"^1.0.0","grunt-eslint":"^21.0.0","grunt-mocha-test":"^0.12.7","mocha":"^5.2.0","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","inquirer":"^3.0.0","mime":"^1.4.1","request":"^2.87.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.19"},"_id":"grunt-idra3@0.1.50","_shasum":"f175c645eb122278fed059fd5b076648d7070662","_from":".","_npmVersion":"3.10.3","_nodeVersion":"6.7.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"f175c645eb122278fed059fd5b076648d7070662","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.50.tgz","integrity":"sha512-rAqrrNX85YVEGVsTG0DXMi+M46Oa1NIGL0CclJtlOq6KeUFQ5oVp7LhHbaCn8S1yROy8r7tojYId1ohI2F6kag==","fileCount":48,"unpackedSize":171835,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJcygNPCRA9TVsSAnZWagAAi9gP+QFmggBv4Qe8quvdx1Bj\n0Jk3pr0I8y+db1wodej9r/XZ4fIi3ybypaFZs4vckFj924KaN7sfLsM+Yd2I\nf6S+gsgAlY6e0lxQR86lL5qNjJMZG+E6z0GnZ0JI3R1w8BBzi97nQwD+ahzD\n0Z3OPf6e5UWFOxuvB1N/Ycs9AU6CWm3yz66mOSrKEa6PN5uxRFA3BE9Hshds\nxUdMVHAWog9AgbS8KmJGgwYMXssJcqqxlGCGRk3XcKaudqQ/7DgSVJ6y0iV9\n5Zk3RAbZ0ZQ3/Z2Zf8hxs6X5b6jNdfckIMe0orVcORCA9TZzA//TglmnjAR2\nT8xYP/ueVKFk4SX7KjY4NDyaTYi6UY38BMi9dfel9vTtE/tDB8ASOdAGtaxU\n0xviIYoa7E+r66zydFbYj+Rl40Gi9GYXWvGcmOU0k/mBQLoC93detWcMD4/Y\n6gpr3jifbponak2f+8D52E+VfBmeTobg3uY9HkzaiDBYyNpUMVw1SR+UHsL9\nryIgwSRbcjfYEVYMyTTBSDTefS4866braaPxIQx5txe6yCwIkOpiCfFe8GSX\nySFn9d4HdUhMqLyH00De2nW+cvkUQdt33cM6/9D6XfyUbFTqzTb0mB3hZm4e\nC9g7CTlqL0Kd1VP0g9gdLCOS3pBfBpNSBGRXMJnHR4/zyy4ueSuj060gyRS5\nbr/s\r\n=0ZAT\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCpBIiHZrLLKSAhO5VQJhWXp6CbtAvcnK6rs7OFYxHyPgIhAL3wv3Qo1cxEqrdfCt/FiCF3kcibvCH/fPu/waD0No+b"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.50_1556742990240_0.6744425441806363"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.51":{"name":"grunt-idra3","version":"0.1.51","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.3","grunt-contrib-clean":"^1.0.0","grunt-eslint":"^21.0.0","grunt-mocha-test":"^0.12.7","mocha":"^5.2.0","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","inquirer":"^3.0.0","mime":"^1.4.1","request":"^2.87.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.19"},"_id":"grunt-idra3@0.1.51","_shasum":"65fb8f01ac62be2de83f08c383c8d2006497f701","_from":".","_npmVersion":"3.10.3","_nodeVersion":"6.7.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"65fb8f01ac62be2de83f08c383c8d2006497f701","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.51.tgz","integrity":"sha512-SXIaTC09+qBV3ns9pXfQ8QXQ+oTJDgo4OUfMvYkkQBRhLIxu14pi4esvp7KBiSgwk7Pl6yzrlUadk/+sruVo7w==","fileCount":48,"unpackedSize":171836,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJc/+odCRA9TVsSAnZWagAASm0P/R5S8BvpOXasbFXRZyUa\n2c4MCkIiW4Q4zpZPUsPvwP3kAL2nZPFIvFx/HX8XdkvYETz42tX580c7lh8P\n6WRnA5tXp/BBf/KqBCaHhPzCo0UiUcLyIUlLf5bFAVLFigYakqXK8KoibO82\nYZvVoifTUGR48X3TXCI1+BaQJL/5USjQFXyuH1uy6aGNrKPqP1ujyCmBnqQx\n+mh7urKgxNhBwmfhYx/jniGf+PFYL+DA6RpGgzBaD518x7EbuLhHlsCf7N94\nkEkQ1ojrkktpwSj7fSB+K5eW1zjixtFGjwxn+XHhE284k/+EW7hh+UYgk39J\ntzBZu2HqS1m3sajDePYK/GpPCH1eECkMd0ybxmXWEFiFev4l7ZwFgrlv+Voc\nUtsrVx22kWswfnGkwfRTtpawIjNLhymLLufXAu264ZuDBs5YUkUwTGRzqxDD\nVO2KxUjkLaEf1tv2uN6FycQi0TheCwisa+0Zgv/uFNcaJ9x9Z2MiiJBIKSRV\npkTe+YHu0w4z6pg++n1N9XPwGHSFhFAaO0NAQsV1cWrQ7FhLprm2UowjHhoy\nHnmu1d4g8r6yxqt1BsDKnTxWlh3jf+lYPodfK3wRCbLGqlMuarP14963dJI7\nBr3Nao0xAethtKfivrlGdFNfxDBnUtgn2T7AvPiGIyY4HghNhXsbXNlHb0YJ\n7G6O\r\n=Dc0r\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDzY39MsPyOJ+i5l7LDZ8JqIq3T70HNYhcZ8Y8FODlmvgIgUEYm66ugyT+gIGVxHoZENSdcDFiIhlnR8CZ1sqh6iTE="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.51_1560275485046_0.7714605351316188"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.52":{"name":"grunt-idra3","version":"0.1.52","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.3","grunt-contrib-clean":"^1.0.0","grunt-eslint":"^21.0.0","grunt-mocha-test":"^0.12.7","mocha":"^5.2.0","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","inquirer":"^3.0.0","mime":"^1.4.1","request":"^2.87.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.19"},"_id":"grunt-idra3@0.1.52","_shasum":"564eeb3083b10af88bddeb2fc4907bf4c8d35854","_from":".","_npmVersion":"3.10.3","_nodeVersion":"6.7.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"564eeb3083b10af88bddeb2fc4907bf4c8d35854","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.52.tgz","integrity":"sha512-cmzyVHe0JveFszq3wvfCQ+EPfBPLH1uqaVpWG7dCf5VJ5ZpVTlNxHQSx2+sb3VY7hffcMfqcRaW7ScZNTkFe4Q==","fileCount":48,"unpackedSize":172017,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdBqMBCRA9TVsSAnZWagAAQ/MP/09w8FWYqEdpyI3Q1vFH\nQFccR6bvDf3M+3k4V4jipzFXb56wcMHy2I6gILodpiH4xbnc6ySJM0k31d8Z\nCS5eWXTrHfYBXieu94fpPN83f9KeGRVmKjAyGc3SVwA5bxNtZYhR2Vhz1SfT\nSz+cjVmwHLk2eAyK9qqOZcQKnbVHH3yfogaCvy6EooxXqiamaN4S3JaZnT8q\nsDC7JWXjAAeywHe+XcxqDZNH6afsYmQM3bnJ0dLZhgCOvnKhTLhMoMBo9qUv\nP88bdHqmaGW3c+REAPuiuCyZtFckx1MIxDGFHG6z54vSvCA/w/P2mlQ/vCsZ\nVgFMebU/GK2WYMujtKs9j5wXBuy6jmHzVzZJ1MmMNDMekPw0C4GsMyrIvNgL\nLZ4+YiCjnkJdzO+BdFNnVlbid1g6UuiYYqP0LKh5HbzPvMSZUnb1SL9UXOiK\nnPZ4id2ZnwlsrENRKRUvltuPOyzRLLzLDP0qKM3eOIOVLs6VreVqWvOAZXAp\nvN5I89pV3zWIvCNzaOUdjnW82Sbwqbe+bOiwZrRk7HcZbALXiqrIyJJhRAIM\n+jTsfvXV68pTaDIMICaVCkra1cR1yQwULSMoOE1K/f3uE7T/NE7tFFrEL7Gg\noBv+iBgRWpkukZwry5jNC6KkW7wRm+ftaii8sfo/lKkddaLE6V22Mf9cLzHf\ns3rb\r\n=jYMf\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIFTxW2yh0hHMyx3E2SoJWRZlC4BoOUjhjcKokWsknFZFAiEAg0itcViai6T3+HXVVcq6hvZUBvHWObLzEDclhmOQ12s="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.52_1560716032741_0.44271856670968535"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.53":{"name":"grunt-idra3","version":"0.1.53","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.3","grunt-contrib-clean":"^1.0.0","grunt-eslint":"^21.0.0","grunt-mocha-test":"^0.12.7","mocha":"^5.2.0","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","inquirer":"^3.0.0","mime":"^1.4.1","request":"^2.87.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.19"},"readme":"# idra\n\n> Command Line utility for integrating with IBM® DevOps Insights\n\nTo install this utility\n```\nnpm install -g grunt-idra3\n```\n\n# Table of Contents\n1. [Concepts](#concepts)\n2. [Getting Started](#getting-started)\n 1. [Scenarios](#scenarios)\n 2. [Prerequisites](#prerequisites)\n 3. [Environment Variables](#environment-variables)\n 4. [Enabling Debug Logs](#enabling-debug-logs)\n 5. [Using the CLI](#using-the-cli)\n3. [Upload Build Records](#upload-build-records)\n4. [Upload Test Results](#upload-test-results)\n 1. [Upload SonarQube Results](#upload-sonarqube-results)\n5. [Upload Deployment Records](#upload-deployment-records)\n6. [Making decisions about build quality using gate policies](#making-decisions-about-build-quality-using-gate-policies)\n\n## Concepts\nIBM® DevOps Insights is a tool that provides insights into your DevOps projects. Use it to learn how compliant your team is with DevOps and developer practices, to manage risk in your codebase, and to automatically enforce quality standards in continuous delivery projects.\n\nUnderstanding of the following concepts will help in faster adoption of IBM® DevOps Insights for your projects.\n\n##### Toolchain\nToolchains are part of [IBM® DevOps Continuous Delivery](https://console.bluemix.net/docs/services/ContinuousDelivery/cd_overview.html#cd_overview). Toolchains provide an integrated set of tools to build, deploy and manage your apps. You can create toolchains that include IBM Cloud services, open source tools, and third party tools that make development and operations repeatable and easier to manage. It is required that the IBM DevOps Insights should be added as one of the tool to your toolchain.\n\n##### Integrating your build tool with IBM DevOps Insights\nThis means instrumenting your build tool with this CLI or DevOps Insights Jenkins plugin to send build, test and deployment records to IBM DevOps Insights.\n\n##### Build record\nIBM DevOps Insights needs to know when a build is complete. This record contains application name, branch, build id, reference to git repo and other fields. This CLI and Jenkins plugin has a command to publish the build record to DevOps Insights.\n\n##### Test record\nIBM DevOps Insights needs to know about the tests performed during the build process. It is necessary that the tests should generate some kind of JSON or XML based file. Here are the list of supported [format](supported-test-formats). The generated test file is published as a test record. Along with the test file this record contains application name, build id, type of tests and other fields. It is required that the application name and build id in the test record matches the one used in the build record for a given build. This CLI and Jenkins plugin has a command to publish test record to DevOps Insights.\n\n##### Deployment records\nIBM DevOps Insights needs to know about the deployments made during the deployment process. This record contains the application name, build id, environment name, status of the deployment and other fields. It is required that the application name and build id in the deployment record matches the one used in the build record for a given build. This CLI and Jenkins plugin has a command to publish a deployment to DevOps Insights.\n\n##### Build Id (or Number)\nThis is an arbitrary length string uniquely identifying each build. This id is used to tie the build, test and deployment records together so it is important to publish those records with the same id for a given build.\n\n##### Policy\nA policy is set of rules specified by the user that collectively defines what is considered a good set of test records for a given application build. Typically, one rule is added for each test record published to DevOps Insights. The policy rules are evaluated by the gate.\n\n##### Branch\nThis is the name of the branch in the source control system.\n\n##### Environment\nThis is the name of environment to which deployments are made during the build process.\n\n##### Data set\nThis is an arbitrary string that identifies the type of tests performed during the build process. Besides the standard names such as \"unit test\", \"fvt\". The tool allows the user to define a custom name.\n\n## Getting Started\n\nUse this utility to integrate IBM® DevOps Insights with Travis CI, Concourse, IBM Urban Code Deploy, IBM Continuous Delivery Pipelines and other CI/CD tools. If you are using Jenkins, use this [Jenkins plugin](https://plugins.jenkins.io/ibm-cloud-devops) instead.\n\nUsing this utility, you can\n - Publish build records, test records and deploy records to IBM® DevOps Insights \n - Make go/no-go decisions about a build's quality by using a Gate policy\n\nFor samples of dashboards in IBM® DevOps Insights, see [Value Proposition](https://plugins.jenkins.io/ibm-cloud-devops).\n\nFor more information about IBM DevOps Insights, see [the official documentation](https://console.bluemix.net/docs/services/DevOpsInsights/index.html).\n\n### Scenarios\nThis document covers two scenarios:\n1. You are integrating DevOps Insights with IBM Continuous Delivery tool.\n2. You are integrating DevOps Insights with other CI/CD tools (e.g., Travis CI, Concourse, IBM Urban Code Deploy, others)\n\n### Prerequisites\n\nTo use the CLI, you need to do the following. These steps should take about 10 minutes.\n\n1. A valid IBM Cloud account. If you don't have one, [register here](https://console.bluemix.net/registration).\n\n2. Once you have an account, you can create an API Key. Log in to [IBM Cloud](https://console.bluemix.net). Click on **Manage**->**Security**->**Platform API Key**. On that screen, create an API Key.\n\n3. An IBM Continuous Delivery toolchain. To create a toolchain:\n - Go to https://console.bluemix.net/devops\n - Click on **Create a Toolchain** button and then select **Build Your Own Toolchain** template. \n - In the next screen, click **Create**.\n - From the URL displayed in the browser, make note of your toolchain id. For example, if your URL is https://console.bluemix.net/devops/toolchains/05572df3-01dc-441b-911d-b2202fe33f96, the toolchain id is the long string after **toolchains/**\n - You can always navigate to your toolchain by [clicking here](https://console.bluemix.net/devops)\n\n4. Add DevOps Insights tool to your toolchain\n - Go to your toolchain\n - Click on **Add a Tool** button\n - Select DevOps Insights tool and click **Create Integration** button\n\n5. Your CI/CD tool must have Node.js® 4.x or greater.\n\n### Environment Variables\n\nIf you are using Travis, Concourse or any CI/CD tool other than the IBM Continuous Delivery pipeline, then set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|TOOLCHAIN_ID| **Required.** The toolchain's GUID |\n|IBM_CLOUD_API_KEY| **Required.** The Bluemix user's Api key|\n|BUILD_NUMBER| **Required.** Any string that identifies the build. You also have the option of specifying build number using the `--buildnumber` parameter, in which case this environment variable is not required. |\n|LOGICAL_APP_NAME| **Required.** The application's name. You also have the option of specifying application's name using the `--logicalappname` parameter, in which case this environment variable must not be set. It is an error to set both the environment variable and the parameter.|\n\nIf you are using IBM Continuous Delivery pipeline, you need to set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|IBM_CLOUD_API_KEY| **Required** The Bluemix user's Api key|\n|BUILD_PREFIX| **Required.** Any string. For example, the Git branch name. If the `--buildnumber` parameter is used to pass a build number then this environment variable is not required.|\n|LOGICAL_APP_NAME| **Required.** The application's name. You also have the option of specifying application's name using the `--logicalappname` parameter, in which case this environment variable must not be set. It is an error to set both the environment variable and the parameter.|\n|PATH|**Required.** In order to have required version of Node.js in your path, set the PATH variable before invoking the utility: `export PATH=/opt/IBM/node-v4.2/bin:$PATH`|\n\nIf you are using IBM Continuous Delivery pipeline and if you want to publish Insights data to another toolchain, then set the following environment variables. \n\n|Name|Description|\n|-----|-----|\n|TOOLCHAIN_ID| **Required.** The target toolchain's GUID. If the target toolchain is owned by different user then provide the target toolchain owner's Bluemix Api key in the `IBM_CLOUD_API_KEY` variable.|\n\n\nIf you are using IBM UrbanCode Deploy, DevOps Insights relies on the previous set of variables, and this one:\n\n|Name|Description|\n|-----|-----|\n|UCD_REQUEST_ID| This maps to the ${p:request.id} property value. |\n\n### Enabling Debug logs\nIf you want to enable debug logs for the DevOps Insights CLI, set the `IDRA_DEBUG` environment variable to `true`. This works in all environments.\n\n|Name|Description|\n|-----|-----|\n|IDRA_DEBUG| When this value is `true`, the DevOps Insights CLI's debugging mode is enabled. By default, the value is `false`. |\n\n\n### Using the CLI\n\nSet [environment details](#environment-details) as described above. Ensure that Node.js 4.2 or higher is avaialble in your CI/CD tool.\n\nTo install this utility, use `npm install -g grunt-idra3`\n\nThen you can invoke the CLI with the `idra` command. You can run the CLI in any pipeline job's command script. For example, this command uploads functional verification test results to DevOps Insights:\n\n```\n# Upload test results\nidra --publishtestresult --filelocation=\"results.json\" --type=fvt\n```\n\n\n## Upload Build Records\nUse the `--publishbuildrecord` command (alias `-b`) to upload build records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishbuildrecord --branch= --repositoryurl= --commitid= --status= --logicalappname= --buildnumber= [--joburl=] [--buildnumber=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--branch`|`-B` | **Required.** The repository branch on which the build is being performed. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--repositoryurl`|`-R` | **Required.** The url of the git repository. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--commitid`|`-C` | **Required.** The git commit id. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--status`|`-S` | **Required.** The build status. This value must be either `pass` or `fail`. |\n|`--logicalappname`|`-L` | _Optional_. The application's name. If this parameter is specified, environment variable **LOGICAL_APP_NAME** must not be set. |\n|`--buildnumber`|`-N` | _Optional_. Any string that identifies the build. This option overrides the value provided by **BUILD_NUMBER** or **BUILD_PREFIX** environment variables. |\n|`--joburl`|`-J` | _Optional_. The URL to the job's build logs. |\n\n\n\n### An example command\n\nIn this an example, the command uploads a build record from a pipeline job.\n\n```shell\nidra --publishbuildrecord --branch=master --repositoryurl=\"https://github.com/oic/dlms.git\" --commitid=dff7884b9168168d91cb9e5aec78e93db0fa80d9 --status=pass --logicalappname=appname --buildnumber=release:17\n```\n\n## Upload Test Results\n\nUse the `--publishtestresult` command (alias `-p`) to upload results from these test types to DevOps Insights:\n\n* Unit tests\n* Code coverage tests\n* Functional verification tests (FVT)\n* Static security scans from IBM Application Security on Cloud\n* Dynamic app scans from IBM Application Security on Cloud\n* [SonarQube results](#upload-sonarqube-results)\n* [Vulnerability Advisor](https://cloud.ibm.com/docs/services/va)\n\n\n### Command syntax and options\n\n```shell\nidra --publishtestresult --filelocation= --type= --logicalappname= --buildnumber= [--drilldownurl=] [--env=] [--token=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--filelocation`| `-F` |**Required.** The location of the test results that you want to upload. This can be a single file, an entire directory, or multiple files that match a wildcard expression.|\n|`--type`| `-T` |**Required.** The type of test results that you want to upload. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, `sonarqube` for SonarQube scans, and `vulnerabilityadvisor` for Vulnerability Advisor scans. In addition to these types you can also use a custom quality data set tag to upload test results of different type.|\n|`--logicalappname`|`-L` | _Optional_. The application's name. If this parameter is specified, environment variable **LOGICAL_APP_NAME** must not be set. |\n|`--buildnumber`|`-N` | _Optional_. Any string that identifies the build. This option overrides the value provided by **BUILD_NUMBER** or **BUILD_PREFIX** environment variables. |\n|`--drilldownurl`| `-U` |_Optional._ A URL where more information about the test results can be found. If this URL is invalid, the option is ignored. |\n|`--env`| `-E` |_Optional._ The environment name to associate with the test results. This option is ignored for unit tests, code coverage tests, and static security scans. |\n|`--token`| `-K` |_Optional_. This is a SonarQube token. This flag is valid only if the type specified is `sonarqube`. It is used by the CLI to pull additional information from the SonarQube server. |\n\n### An example command\n\nIn this example, the command uploads all JSON-formatted FVT results from a directory to DevOps Insights. Additionally, a test tool is declared, a test result URL is given, and a logical staging environment is provided. Specifying an environment is especially important when you want your results to be analyzed alongside other activities that take place in that same environment.\n\n```shell\nidra --publishtestresult --filelocation=\"tests/fvt/*.json\" --type=fvt --logicalappname=appname --buildnumber=release:17 -drilldownurl=\"https://example.com/testinfo\" --env=\"staging\"\n```\n\n### Supported Test Formats\n|Type of Test|tag|Supported Formats|\n|-----|-----|-----|\n|Unit Test|`unittest`|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Test Case|`fvt`|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Code Coverage|`code`|Cobertura (xml), lcov, Istanbul, JaCoCo|\n|SonarQube|`sonarqube`|SonarQube|\n|Static Security Scan|`staticsecurityscan`|IBM Application Security on Cloud|\n|Dynamic Security Scan|`dynamicsecurityscan`|IBM Application Security on Cloud|\n|Vulnerability Advisor|`vulnerabilityadvisor`|JSON output of the command [ibmcloud cr va](https://cloud.ibm.com/docs/cli?topic=container-registry-cli-plugin-containerregcli#bx_cr_va)|\n|Custom Data Sets - Tests|Custom Tag*|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Custom Data Sets - Code Coverage|Custom Tag*|Cobertura (xml), lcov, Istanbul, JaCoCo|\n\nFor golang [gocov](https://github.com/axw/gocov/) users, please convert to Cobertura using [gocov XML(Cobertura) export](https://github.com/yaoyaozong/gocov-xml)\n\n\\* For custom tags create a quality data set by using the user interface. Navigate to your toolchain, click on DevOps Insights card. Navigate to quality dashboard. Click on the Kebab menu which is to the top-right of the quality dashboard. Click on **Configure Quality Data Sets**\n\n### Upload SonarQube Results\nTo upload data from SonarQube, you must provide the SonarQube server token using `--token`. Your SonarQube server is not required to be accessible from your CI/CD tool.\n\nAfter you run a scan using SonarQube, you can upload SonarQube results by running this command.\n\n```\nidra --publishtestresult --filelocation=.scannerwork/report-task.txt --type=sonarqube --token=234234434\n```\n\nIn the above command, report-task.txt is a file generated during the SonarQube scan.\n\nIf this command fails for some reason, you can enable logs by setting IDRA_DEBUG environment variable to true.\n\nIf you are using self-signed certificates for SonarQube server, you will need to set `export NODE_TLS_REJECT_UNAUTHORIZED=0`\n\n## Upload Deployment Records\nUse the `--publishdeployrecord` command (alias `-d`) to upload deployment records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishdeployrecord --env= --status= --joburl= --logicalappname= --buildnumber= [--appurl=] [--deployableid=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--env`|`-E` | **Required.** The environment where the pipeline job deployed the app. |\n|`--status`|`-S` | **Required.** The deployment status. This value must be either `pass` or `fail`. |\n|`--joburl`|`-J` | **Required.** The URL to the job's deployment logs. |\n|`--logicalappname`|`-L` | _Optional_. The application's name. If this parameter is specified, environment variable **LOGICAL_APP_NAME** must not be set. |\n|`--buildnumber`|`-N` | _Optional_. Any string that identifies the build. This option overrides the value provided by **BUILD_NUMBER** or **BUILD_PREFIX** environment variables. |\n|`--appurl`|`-A` | _Optional._ The URL where the deployed app is running. |\n|`--deployableid`| `-I` | _Optional._ The deployed app's application ID. You can get the ID by running the Cloud Foundry CLI's `cf env` command. The application ID is listed under `VCAP_APPLICATION`. |\n\n### An example command\n\nIn this an example, the command uploads a deployment record from a pipeline job. The deployment is to the \"staging\" environment. The deployment is successful and the app is running at a specified URL.\n\n```shell\nidra --publishdeployrecord --env=\"staging\" --status=pass --joburl=\"https://app.staging.example.com\" --logicalappname=appname --buildnumber=release:17\n```\n\n## Making decisions about build quality using gate policies\n\nTo use this feature, create a quality policy by using the user interface. Navigate to your toolchain, click on **DevOps Insights** card. Then on the left menu, click on **Policies**.\n\nUse the `--evaluategate` command (alias `-g`) to request a gate decision for a DevOps Insights policy in your pipeline. If the policy is satisfied, the pipeline continues running. If not, and you use the `--forcedecision` flag, the pipeline stops running.\n\n### Command syntax and options\n\n```shell\nidra --evaluategate --policy= --logicalappname= --buildnumber= [--forcedecision] [--type=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--policy`|`-P` | **Required.** The name of the policy that the gate uses to make its decision. |\n|`--logicalappname`|`-L` | _Optional_. The application's name. If this parameter is specified, environment variable **LOGICAL_APP_NAME** must not be set. |\n|`--buildnumber`|`-N` | _Optional_. Any string that identifies the build. This option overrides the value provided by **BUILD_NUMBER** or **BUILD_PREFIX** environment variables. |\n|`--forcedecision`|`-D` | _Optional._ Set the value to `true` to cause the process to exit with an error code, if the policy evaluation fails. The value defaults to `false` if this option is not specified. |\n|`--type`|`-E` | _Optional_. A rule type to consider. If you include this option, only rules of this type are considered in the decision-making process. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, and `sonarqube` for SonarQube scans. |\n\n### An example command\n\n```shell\nidra --evaluategate --policy=\"somepolicy\" --logicalappname=appname --buildnumber=release:17\n```\n\n## Release History\n_(Nothing yet)_\n","readmeFilename":"README.md","_id":"grunt-idra3@0.1.53","_shasum":"a894effcf585311002f50104e8efd4ee987efe02","_from":".","_npmVersion":"3.10.3","_nodeVersion":"6.7.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"a894effcf585311002f50104e8efd4ee987efe02","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.53.tgz","integrity":"sha512-sPh6/eKfMKrIyEsdFkBzAiQvdqSnEgvq4PBwsaMn1Ur3I7/av/dwXRzW3jzJHm6N90H+uGzBEKE9rvVu4O73Rg==","fileCount":48,"unpackedSize":172671,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdCrDmCRA9TVsSAnZWagAAIPkP+wSJsH/Gr8DZUYfoRKtV\n58r+bYNVQpQlDxkf9DUyVEb7QzASokwwAaOuBaD8CdrIJnA5ayGJQeLzQpG+\nq/diwjeaGO5K45h9PAlnXLgN4RIWyiEEmX+0SJtoLozoyE7df61LnWBph6XV\n3wejifga7kQDwiTRIXIkWtohgvS3BRFKpH3xH8fQ1D4yNLEdG9R8BlC76bbD\nR1BskE3zsI+QEeBPCN7OGpy1OdRG42ndmcnv9vWIrYvi7ajW/WetvePIXOt/\nGnaxQUpkVFzEdrhwuuWNWfaJba2oofa4O69cEBaakB1rxtyvJsCPTqy/LV+8\nDbp3GhCA6/MtyI/BGXiqSPB3/C+LHpM093ydS2dDLtxwmYQljn26qNaMCVpU\ndpXWSsIDlUE9LRxXf3NNcHxz+aIbKOft35CBBR8wMs2NTiw4Nfma3++Ku84j\ninZBAKUSdSL5F8q8/vtPPHLa6xA/cZX6N4WXvq7lkFNZYktyxN48VXooo/98\niZiiOHf5fugXFJqGgcEzK0VDmfTHLgq1H3hfZmJ6Z4dSb3fH5gXL7Qu59Qzj\nZC+s9Jf9wykzU27rUgTjVsrVieaBhHc31bl2Zx64VYmPWwgTpzKKz3JdG1Lh\nWzpu0oj4oyQK+yICQ1xw8+8omQcSQofA+pjQQppa0sLTT1cPfYw3T73Kp8aj\nl2qT\r\n=u/Qg\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDI93t01IvsG8aODUxcsbjtAoFaKm7ysH2ROgUaLinl5AIhAO8LjP16OYUtwnYR8VX27Jze1i/yabIyOE29sx65iuMF"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.53_1560981733257_0.6979868101959068"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.54":{"name":"grunt-idra3","version":"0.1.54","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.3","grunt-contrib-clean":"^1.0.0","grunt-eslint":"^21.0.0","grunt-mocha-test":"^0.12.7","mocha":"^5.2.0","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","inquirer":"^3.0.0","mime":"^1.4.1","request":"^2.87.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.19"},"_id":"grunt-idra3@0.1.54","_shasum":"fc239d80824eac810a53658cf00191356c4b9ece","_from":".","_npmVersion":"3.10.3","_nodeVersion":"6.7.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"fc239d80824eac810a53658cf00191356c4b9ece","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.54.tgz","integrity":"sha512-j4RchY6wJnzZ+EXN1Pr9iKfPPEPw/RkbH3PYkAuWZ4Oj7WWt+SdQJn8uz4lUwXOdF+j5EY52ttK5bJe0/FSMUg==","fileCount":48,"unpackedSize":172670,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdC+K4CRA9TVsSAnZWagAAbesQAIuGk36djXbkYYCZ7ixF\nIH7Ir3t1Vr8vxp87A4aTfY1uYk2zaSAeWkmiL0YkN7MvHv6TtSxZnjXolbYC\nBdQ6FAW+He+lKQnyTGN+0greI+xKJPKiWM9Jy0fTeEvJWl4Z5hmPQsNNpaI2\n59jRi4Uyzh7yHHA3cswMP6YZftrpfzjAswadTY7BMAOIyTxnBeAiI/nj29Kg\n6779p37PFsTuQCRMeMt1fGf3pRblRJtM3FErg/IM6VIzBYlbUjb1i7vviYPC\n4ypcm1TA3A+e1tA7ClhPYWLWGTT6gBXEDEJBPJuJTVxcQbc1T5sAyiNZk+6s\nTSOIc8bzOClMZWJhdCJvc4KELs59hMURFnrCZHtItrZ+eUBm37ohlV5KZAw7\n1MSjQdqV6vWT6ufJE5ytjUfKXgikkN3KOTtVvpOEhC6grOdArnEXb4fusgu8\n8SggkZuFL4PjH0eokEMBP5ra5X/JBq1+wRPyl5xPmVzzCzh0cLjk+KpwsfzO\npTY2Lg8XJ52+TRkOM2Y/cBVJ64QAREpvEF7eOLWAIdEDyqh39y2KV8D7KVkH\nP03qxvZdFnseB5U2f2ME/8Pu8jlYI3aN4lTBRSaXHfzGAahd6cWHu41uidSh\nTgVmw82QNhSBlGXkIN4V2UpC5TiGFw70vRMElh9aLr+09BMOuZK/967K0D2y\n38EY\r\n=PX7E\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCrogosP1FO8ybnJ33aJJO57CXs6/N1a544BrDzCtlMmwIhAJWB5FAqBLxqLvz/x8HzMOLebWAY5XdDeA/ReSy3XvVq"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.54_1561060023728_0.9137649560089245"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.55":{"name":"grunt-idra3","version":"0.1.55","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.3","grunt-contrib-clean":"^1.0.0","grunt-eslint":"^21.0.0","grunt-mocha-test":"^0.12.7","mocha":"^5.2.0","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","inquirer":"^3.0.0","mime":"^1.4.1","request":"^2.87.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.19"},"readme":"# idra\n\n> Command Line utility for integrating with IBM® DevOps Insights\n\nTo install this utility\n```\nnpm install -g grunt-idra3\n```\n\n# Table of Contents\n1. [Concepts](#concepts)\n2. [Getting Started](#getting-started)\n 1. [Scenarios](#scenarios)\n 2. [Prerequisites](#prerequisites)\n 3. [Environment Variables](#environment-variables)\n 4. [Enabling Debug Logs](#enabling-debug-logs)\n 5. [Using the CLI](#using-the-cli)\n3. [Upload Build Records](#upload-build-records)\n4. [Upload Test Results](#upload-test-results)\n 1. [Upload SonarQube Results](#upload-sonarqube-results)\n5. [Upload Deployment Records](#upload-deployment-records)\n6. [Making decisions about build quality using gate policies](#making-decisions-about-build-quality-using-gate-policies)\n\n## Concepts\nIBM® DevOps Insights is a tool that provides insights into your DevOps projects. Use it to learn how compliant your team is with DevOps and developer practices, to manage risk in your codebase, and to automatically enforce quality standards in continuous delivery projects.\n\nUnderstanding of the following concepts will help in faster adoption of IBM® DevOps Insights for your projects.\n\n##### Toolchain\nToolchains are part of [IBM® DevOps Continuous Delivery](https://console.bluemix.net/docs/services/ContinuousDelivery/cd_overview.html#cd_overview). Toolchains provide an integrated set of tools to build, deploy and manage your apps. You can create toolchains that include IBM Cloud services, open source tools, and third party tools that make development and operations repeatable and easier to manage. It is required that the IBM DevOps Insights should be added as one of the tool to your toolchain.\n\n##### Integrating your build tool with IBM DevOps Insights\nThis means instrumenting your build tool with this CLI or DevOps Insights Jenkins plugin to send build, test and deployment records to IBM DevOps Insights.\n\n##### Build record\nIBM DevOps Insights needs to know when a build is complete. This record contains application name, branch, build id, reference to git repo and other fields. This CLI and Jenkins plugin has a command to publish the build record to DevOps Insights.\n\n##### Test record\nIBM DevOps Insights needs to know about the tests performed during the build process. It is necessary that the tests should generate some kind of JSON or XML based file. Here are the list of supported [format](supported-test-formats). The generated test file is published as a test record. Along with the test file this record contains application name, build id, type of tests and other fields. It is required that the application name and build id in the test record matches the one used in the build record for a given build. This CLI and Jenkins plugin has a command to publish test record to DevOps Insights.\n\n##### Deployment records\nIBM DevOps Insights needs to know about the deployments made during the deployment process. This record contains the application name, build id, environment name, status of the deployment and other fields. It is required that the application name and build id in the deployment record matches the one used in the build record for a given build. This CLI and Jenkins plugin has a command to publish a deployment to DevOps Insights.\n\n##### Build Id (or Number)\nThis is an arbitrary length string uniquely identifying each build. This id is used to tie the build, test and deployment records together so it is important to publish those records with the same id for a given build.\n\n##### Policy\nA policy is set of rules specified by the user that collectively defines what is considered a good set of test records for a given application build. Typically, one rule is added for each test record published to DevOps Insights. The policy rules are evaluated by the gate.\n\n##### Branch\nThis is the name of the branch in the source control system.\n\n##### Environment\nThis is the name of environment to which deployments are made during the build process.\n\n##### Data set\nThis is an arbitrary string that identifies the type of tests performed during the build process. Besides the standard names such as \"unit test\", \"fvt\". The tool allows the user to define a custom name.\n\n## Getting Started\n\nUse this utility to integrate IBM® DevOps Insights with Travis CI, Concourse, IBM Urban Code Deploy, IBM Continuous Delivery Pipelines and other CI/CD tools. If you are using Jenkins, use this [Jenkins plugin](https://plugins.jenkins.io/ibm-cloud-devops) instead.\n\nUsing this utility, you can\n - Publish build records, test records and deploy records to IBM® DevOps Insights \n - Make go/no-go decisions about a build's quality by using a Gate policy\n\nFor samples of dashboards in IBM® DevOps Insights, see [Value Proposition](https://plugins.jenkins.io/ibm-cloud-devops).\n\nFor more information about IBM DevOps Insights, see [the official documentation](https://console.bluemix.net/docs/services/DevOpsInsights/index.html).\n\n### Scenarios\nThis document covers two scenarios:\n1. You are integrating DevOps Insights with IBM Continuous Delivery tool.\n2. You are integrating DevOps Insights with other CI/CD tools (e.g., Travis CI, Concourse, IBM Urban Code Deploy, others)\n\n### Prerequisites\n\nTo use the CLI, you need to do the following. These steps should take about 10 minutes.\n\n1. A valid IBM Cloud account. If you don't have one, [register here](https://console.bluemix.net/registration).\n\n2. Once you have an account, you can create an API Key. Log in to [IBM Cloud](https://console.bluemix.net). Click on **Manage**->**Security**->**Platform API Key**. On that screen, create an API Key.\n\n3. An IBM Continuous Delivery toolchain. To create a toolchain:\n - Go to https://console.bluemix.net/devops\n - Click on **Create a Toolchain** button and then select **Build Your Own Toolchain** template. \n - In the next screen, click **Create**.\n - From the URL displayed in the browser, make note of your toolchain id. For example, if your URL is https://console.bluemix.net/devops/toolchains/05572df3-01dc-441b-911d-b2202fe33f96, the toolchain id is the long string after **toolchains/**\n - You can always navigate to your toolchain by [clicking here](https://console.bluemix.net/devops)\n\n4. Add DevOps Insights tool to your toolchain\n - Go to your toolchain\n - Click on **Add a Tool** button\n - Select DevOps Insights tool and click **Create Integration** button\n\n5. Your CI/CD tool must have Node.js® 4.x or greater.\n\n### Environment Variables\n\nIf you are using Travis, Concourse or any CI/CD tool other than the IBM Continuous Delivery pipeline, then set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|TOOLCHAIN_ID| **Required.** The toolchain's GUID |\n|IBM_CLOUD_API_KEY| **Required.** The Bluemix user's Api key|\n|BUILD_NUMBER| **Required.** Any string that identifies the build. You also have the option of specifying build number using the `--buildnumber` parameter, in which case this environment variable is not required. |\n|LOGICAL_APP_NAME| **Required.** The application's name. You also have the option of specifying application's name using the `--logicalappname` parameter, in which case this environment variable must not be set. It is an error to set both the environment variable and the parameter.|\n\nIf you are using IBM Continuous Delivery pipeline, you need to set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|IBM_CLOUD_API_KEY| **Required** The Bluemix user's Api key|\n|BUILD_PREFIX| **Required.** Any string. For example, the Git branch name. If the `--buildnumber` parameter is used to pass a build number then this environment variable is not required.|\n|LOGICAL_APP_NAME| **Required.** The application's name. You also have the option of specifying application's name using the `--logicalappname` parameter, in which case this environment variable must not be set. It is an error to set both the environment variable and the parameter.|\n|PATH|**Required.** In order to have required version of Node.js in your path, set the PATH variable before invoking the utility: `export PATH=/opt/IBM/node-v4.2/bin:$PATH`|\n\nIf you are using IBM Continuous Delivery pipeline and if you want to publish Insights data to another toolchain, then set the following environment variables. \n\n|Name|Description|\n|-----|-----|\n|TOOLCHAIN_ID| **Required.** The target toolchain's GUID. If the target toolchain is owned by different user then provide the target toolchain owner's Bluemix Api key in the `IBM_CLOUD_API_KEY` variable.|\n\n\nIf you are using IBM UrbanCode Deploy, DevOps Insights relies on the previous set of variables, and this one:\n\n|Name|Description|\n|-----|-----|\n|UCD_REQUEST_ID| This maps to the ${p:request.id} property value. |\n\n### Enabling Debug logs\nIf you want to enable debug logs for the DevOps Insights CLI, set the `IDRA_DEBUG` environment variable to `true`. This works in all environments.\n\n|Name|Description|\n|-----|-----|\n|IDRA_DEBUG| When this value is `true`, the DevOps Insights CLI's debugging mode is enabled. By default, the value is `false`. |\n\n\n### Using the CLI\n\nSet [environment details](#environment-details) as described above. Ensure that Node.js 4.2 or higher is avaialble in your CI/CD tool.\n\nTo install this utility, use `npm install -g grunt-idra3`\n\nThen you can invoke the CLI with the `idra` command. You can run the CLI in any pipeline job's command script. For example, this command uploads functional verification test results to DevOps Insights:\n\n```\n# Upload test results\nidra --publishtestresult --filelocation=\"results.json\" --type=fvt\n```\n\n\n## Upload Build Records\nUse the `--publishbuildrecord` command (alias `-b`) to upload build records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishbuildrecord --branch= --repositoryurl= --commitid= --status= --logicalappname= --buildnumber= [--joburl=] [--buildnumber=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--branch`|`-B` | **Required.** The repository branch on which the build is being performed. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--repositoryurl`|`-R` | **Required.** The url of the git repository. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--commitid`|`-C` | **Required.** The git commit id. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--status`|`-S` | **Required.** The build status. This value must be either `pass` or `fail`. |\n|`--logicalappname`|`-L` | _Optional_. The application's name. If this parameter is specified, environment variable **LOGICAL_APP_NAME** must not be set. |\n|`--buildnumber`|`-N` | _Optional_. Any string that identifies the build. This option overrides the value provided by **BUILD_NUMBER** or **BUILD_PREFIX** environment variables. |\n|`--joburl`|`-J` | _Optional_. The URL to the job's build logs. |\n\n\n\n### An example command\n\nIn this an example, the command uploads a build record from a pipeline job.\n\n```shell\nidra --publishbuildrecord --branch=master --repositoryurl=\"https://github.com/oic/dlms.git\" --commitid=dff7884b9168168d91cb9e5aec78e93db0fa80d9 --status=pass --logicalappname=appname --buildnumber=release:17\n```\n\n## Upload Test Results\n\nUse the `--publishtestresult` command (alias `-p`) to upload results from these test types to DevOps Insights:\n\n* Unit tests\n* Code coverage tests\n* Functional verification tests (FVT)\n* Static security scans from IBM Application Security on Cloud\n* Dynamic app scans from IBM Application Security on Cloud\n* [SonarQube results](#upload-sonarqube-results)\n* [Vulnerability Advisor](https://cloud.ibm.com/docs/services/va)\n\n\n### Command syntax and options\n\n```shell\nidra --publishtestresult --filelocation= --type= --logicalappname= --buildnumber= [--drilldownurl=] [--env=] [--token=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--filelocation`| `-F` |**Required.** The location of the test results that you want to upload. This can be a single file, an entire directory, or multiple files that match a wildcard expression.|\n|`--type`| `-T` |**Required.** The type of test results that you want to upload. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, `sonarqube` for SonarQube scans, and `vulnerabilityadvisor` for Vulnerability Advisor scans. In addition to these types you can also use a custom quality data set tag to upload test results of different type.|\n|`--logicalappname`|`-L` | _Optional_. The application's name. If this parameter is specified, environment variable **LOGICAL_APP_NAME** must not be set. |\n|`--buildnumber`|`-N` | _Optional_. Any string that identifies the build. This option overrides the value provided by **BUILD_NUMBER** or **BUILD_PREFIX** environment variables. |\n|`--drilldownurl`| `-U` |_Optional._ A URL where more information about the test results can be found. If this URL is invalid, the option is ignored. |\n|`--env`| `-E` |_Optional._ The environment name to associate with the test results. This option is ignored for unit tests, code coverage tests, and static security scans. |\n|`--token`| `-K` |_Optional_. This is a SonarQube token. This flag is valid only if the type specified is `sonarqube`. It is used by the CLI to pull additional information from the SonarQube server. |\n\n### An example command\n\nIn this example, the command uploads all JSON-formatted FVT results from a directory to DevOps Insights. Additionally, a test tool is declared, a test result URL is given, and a logical staging environment is provided. Specifying an environment is especially important when you want your results to be analyzed alongside other activities that take place in that same environment.\n\n```shell\nidra --publishtestresult --filelocation=\"tests/fvt/*.json\" --type=fvt --logicalappname=appname --buildnumber=release:17 -drilldownurl=\"https://example.com/testinfo\" --env=\"staging\"\n```\n\n### Supported Test Formats\n|Type of Test|tag|Supported Formats|\n|-----|-----|-----|\n|Unit Test|`unittest`|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Test Case|`fvt`|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Code Coverage|`code`|Cobertura (xml), lcov, Istanbul, JaCoCo|\n|SonarQube|`sonarqube`|SonarQube|\n|Static Security Scan|`staticsecurityscan`|IBM Application Security on Cloud|\n|Dynamic Security Scan|`dynamicsecurityscan`|IBM Application Security on Cloud|\n|Vulnerability Advisor|`vulnerabilityadvisor`|JSON output of the command [ibmcloud cr va](https://cloud.ibm.com/docs/cli?topic=container-registry-cli-plugin-containerregcli#bx_cr_va)|\n|Custom Data Sets - Tests|Custom Tag*|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Custom Data Sets - Code Coverage|Custom Tag*|Cobertura (xml), lcov, Istanbul, JaCoCo|\n\nFor golang [gocov](https://github.com/axw/gocov/) users, please convert to Cobertura using [gocov XML(Cobertura) export](https://github.com/yaoyaozong/gocov-xml)\n\n\\* For custom tags create a quality data set by using the user interface. Navigate to your toolchain, click on DevOps Insights card. Navigate to quality dashboard. Click on the Kebab menu which is to the top-right of the quality dashboard. Click on **Configure Quality Data Sets**\n\n### Upload SonarQube Results\nTo upload data from SonarQube, you must provide the SonarQube server token using `--token`. Your SonarQube server is not required to be accessible from your CI/CD tool.\n\nAfter you run a scan using SonarQube, you can upload SonarQube results by running this command.\n\n```\nidra --publishtestresult --filelocation=.scannerwork/report-task.txt --type=sonarqube --token=234234434\n```\n\nIn the above command, report-task.txt is a file generated during the SonarQube scan.\n\nIf this command fails for some reason, you can enable logs by setting IDRA_DEBUG environment variable to true.\n\nIf you are using self-signed certificates for SonarQube server, you will need to set `export NODE_TLS_REJECT_UNAUTHORIZED=0`\n\n## Upload Deployment Records\nUse the `--publishdeployrecord` command (alias `-d`) to upload deployment records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishdeployrecord --env= --status= --joburl= --logicalappname= --buildnumber= [--appurl=] [--deployableid=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--env`|`-E` | **Required.** The environment where the pipeline job deployed the app. |\n|`--status`|`-S` | **Required.** The deployment status. This value must be either `pass` or `fail`. |\n|`--joburl`|`-J` | **Required.** The URL to the job's deployment logs. |\n|`--logicalappname`|`-L` | _Optional_. The application's name. If this parameter is specified, environment variable **LOGICAL_APP_NAME** must not be set. |\n|`--buildnumber`|`-N` | _Optional_. Any string that identifies the build. This option overrides the value provided by **BUILD_NUMBER** or **BUILD_PREFIX** environment variables. |\n|`--appurl`|`-A` | _Optional._ The URL where the deployed app is running. |\n|`--deployableid`| `-I` | _Optional._ The deployed app's application ID. You can get the ID by running the Cloud Foundry CLI's `cf env` command. The application ID is listed under `VCAP_APPLICATION`. |\n\n### An example command\n\nIn this an example, the command uploads a deployment record from a pipeline job. The deployment is to the \"staging\" environment. The deployment is successful and the app is running at a specified URL.\n\n```shell\nidra --publishdeployrecord --env=\"staging\" --status=pass --joburl=\"https://app.staging.example.com\" --logicalappname=appname --buildnumber=release:17\n```\n\n## Making decisions about build quality using gate policies\n\nTo use this feature, create a quality policy by using the user interface. Navigate to your toolchain, click on **DevOps Insights** card. Then on the left menu, click on **Policies**.\n\nUse the `--evaluategate` command (alias `-g`) to request a gate decision for a DevOps Insights policy in your pipeline. If the policy is satisfied, the pipeline continues running. If not, and you use the `--forcedecision` flag, the pipeline stops running.\n\n### Command syntax and options\n\n```shell\nidra --evaluategate --policy= --logicalappname= --buildnumber= [--forcedecision] [--type=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--policy`|`-P` | **Required.** The name of the policy that the gate uses to make its decision. |\n|`--logicalappname`|`-L` | _Optional_. The application's name. If this parameter is specified, environment variable **LOGICAL_APP_NAME** must not be set. |\n|`--buildnumber`|`-N` | _Optional_. Any string that identifies the build. This option overrides the value provided by **BUILD_NUMBER** or **BUILD_PREFIX** environment variables. |\n|`--forcedecision`|`-D` | _Optional._ Set the value to `true` to cause the process to exit with an error code, if the policy evaluation fails. The value defaults to `false` if this option is not specified. |\n|`--type`|`-E` | _Optional_. A rule type to consider. If you include this option, only rules of this type are considered in the decision-making process. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, and `sonarqube` for SonarQube scans. |\n\n### An example command\n\n```shell\nidra --evaluategate --policy=\"somepolicy\" --logicalappname=appname --buildnumber=release:17\n```\n\n## Release History\n_(Nothing yet)_\n","readmeFilename":"README.md","_id":"grunt-idra3@0.1.55","_shasum":"71a9bbe70c96b9830d33ec123be59a273fb55447","_from":".","_npmVersion":"3.10.3","_nodeVersion":"6.7.0","_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"dist":{"shasum":"71a9bbe70c96b9830d33ec123be59a273fb55447","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.55.tgz","integrity":"sha512-3vEGjjVTSSDYlx6KS1Wp3MJp7yH7jlnAj0qh9MYvhp1nZX/76R8JI5Jp3iZ9pypzhPiLYsJT2SGShNg5gYRjBw==","fileCount":48,"unpackedSize":172655,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdERBOCRA9TVsSAnZWagAAXrIQAJTvcpzMRfljF/6H1w5S\n+BXEJjpjJZAiNf8jFpdvvMeqo0TFnsqTofulsgA5OJUkVu2Thawg1TPWhUMh\nRQ+Zz7gW16jp1wCrXXiS3dHktrSNu+CUTnPgkjasfRAY1f4LCsunmDGOhq27\n2QeKnIXwF7cMEOlPGMvNxmwiINIftUhVR0rerH9CEGJkXOgIUph+nT4+wdA8\n7/POOuIMbprMBXW4NludmvDsivbXOKTGtnGPyVybYaL+D+jDYumStKXgiK54\nDcWOso4+JE5GOkDUWRnTHXJKVyOjPCzqtQWcdhcXLGwr3ssKFa1u4xp9/FBB\nwbCZxxF0T9JsZR4mOf3Pi4yWXIdUJUOFh5ZtSI5Gd8PqpNKF4tf1qiN7yYrL\nsn4c5amS7tj5v9S+Xkwq8ByuW3TxafoawI3vR+UY2MS1dz2LYNp/qPpOsoHy\nlBGVUYVpWjv0RnUzh4Mzqw3QH55u0liqGTQBh3rMgq8DfCiA1hZbEE+jMNch\nzFGfnZtMUeHgHuDEcp7HD8yPO2sVx+IRXmA+yKEUSxf6pIW6b9TpzyPf7Mts\nD5GOsyTcEtc+YPwrizZbMiiBat4k7wyUtDB9Qp1bjXZV+d3JC6Wz4WqZ5Iwk\nnQSeZB4TaNK1Nwq9u+SRit2OPbSyjfjgXvQMAE33OB4PMyHCrNTlBVaxUO0w\n/TVS\r\n=f8Eu\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIASK0VFP5gbZck4tIEsUsHe6US4/mTocbYnBDDtYewEKAiEAqHWTZ3S+RsLSNTXH2SKJI5OPCOMorzkrm9TwoMtCElA="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.55_1561399373715_0.37954843767250646"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.57":{"name":"grunt-idra3","version":"0.1.57","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.3","grunt-contrib-clean":"^1.0.0","grunt-eslint":"^21.0.0","grunt-mocha-test":"^0.12.7","mocha":"^5.2.0","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^2.1.4","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","inquirer":"^3.0.0","mime":"^1.4.1","request":"^2.87.0","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.19"},"gitHead":"4877ff98f5504149156be9e5e8bf76d30be7e40e","_id":"grunt-idra3@0.1.57","_nodeVersion":"10.16.3","_npmVersion":"6.9.0","dist":{"integrity":"sha512-uGFckjlRz7nLXlQY/RqMMD+3/mGqqZ+JG74XEf0/A5qAirmdIzp4Ir5uSrdR8ZDPQkQWRP/b5MNUoXSCFB56UA==","shasum":"2720bff18a03a896d973b4eff0f957ee3b73fbb7","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.57.tgz","fileCount":47,"unpackedSize":222305,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJdiPOeCRA9TVsSAnZWagAAG4UQAIqaNWdggRSv5sJp+Mg/\nMbLSf5RV4Wu5bGxRMsiAAtLb95Nr2PCTUoYJZpvDAy8KzsYJaoYYxcXpIR+u\nbbeX0/NZKddg2aC3BZHRk7iG3yJGltt8kacVpTMbW/CGMLVoNJoPKQq4R6Wg\nmhm6FtbOC/j/ZD947r5wx/ICjl5NGdnY5d4o1zAfGIo75mUqdFap60wJsv+U\nStOncLcQTsFjOwksoc+c4V8VARm1NxIb20y3rv4oTpJcXnGG/UeJNWIJczkq\nb0vAdBxoPNiZ7XY9T+s2XZXsEzRIFpXsWhkSfjg1P37gWxitU89PUt1LJEWu\n+g/Wl8J6morCL1bihwh/M7aSX6od3f9lQ6sY5oBG7fkWrul0Db5nsKCvol18\nhEIFWStkdZxuoViMhhxUHboLelsLXwrE/LImsPRNZUi/aqf6rWtvKSZmM2LH\nk2a+gI284lJ0rPju1WH7FY+H4h7MXO7iNpZBilOB5nwDSPpf15FMryQL9XRK\nebnhEFr7fFDtoS8I/jiRYlyokjXl9FsNhxfjGWFCwQOF40Yd+mbAWd/r6zIS\noV1A/GCytZr342wj9FAHRWAHQQjAryL65s9wHSC/f9ZRfr3PWPTBDoPP65Br\nAxDvtqwjGu0+FAv4NzTPqMzzCsiLjYhsJqcDzatIVjD5DI5bqe0EcbTzzmf/\ngcfG\r\n=myoq\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCmu+/MB+vvBgeiq0XkYnsfoeVRiFrGzroOYMRpA5+HDQIhAMKdlT2xsCRGoiMt3NfMa3clPKPPJnQtjq6t4um3l0Bh"}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.57_1569256349209_0.2070988162658436"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.58":{"name":"grunt-idra3","version":"0.1.58","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.3","grunt-contrib-clean":"^1.0.0","grunt-eslint":"^23.0.0","grunt-mocha-test":"^0.12.7","mocha":"^5.2.0","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^3.2.0","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","inquirer":"^7.3.3","mime":"^1.4.1","request":"^2.88.2","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.19"},"gitHead":"237f3b34f0bf6c77917d8adbdc615fcf0727e6fb","_id":"grunt-idra3@0.1.58","_nodeVersion":"13.12.0","_npmVersion":"6.14.4","dist":{"integrity":"sha512-MCB6oogFCFdXmO2g6PoLHkc8VJINzWXguHdjOtslmukuWrvv5J0gpxlQDWlVkgzHn32vBD88iD9dlNI3rBnTOg==","shasum":"26b35a77c6be1645fd083c47a3f4103e8791d761","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.58.tgz","fileCount":47,"unpackedSize":222289,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJfWRnUCRA9TVsSAnZWagAAWcgP/RTcgwSt+FmK6yaZg5e7\nBYgHCfJdB6ZehRjKsTO444v+TbRpvO/rR1t8NYOf8jTAEwkmzd6Vf520MdQC\nYL6MzXYiADArsEobQTu0tLi76LifRLfKl4Q1C5KiWlqv5UShBftqLc0Vc9SF\nmSssV1gLNDpWRkd2AuRE9z6YzrCjIDTCNfTlc/8+ANiYXmSq0gAiwpzD65Hp\nvUxeP/i+Kcsi3BzwmKgIywuXZGwRM4dnBbExkkNAeLf996/Dn2HwKqAv6g+W\n5tE6+PZ5ERc7CQon8xgzK8aiKxxvkTjx7JlUrOPonPdkgv3q3SeQGGvz+15Z\nbJGHrwwg9Q0BOBfy0WMD4IVtXgWCl8AMHkfHts01C/lCsg5JCj5FXKb0DFBF\nLeY6MS68Rzi6efeCMeW0tsTF39Z2JKqN5S6iQzeYq+ZY8XVIzR+giXqImDMV\nnpI+ZJAw69hJPy5VOfrND0zsV9E+aOniEZWNLaUgc+V4Qe7vxS9PEvI42Pcr\n7491CgzvJXunxQELNTTOBB5QRQiu+YwtSbJXKUE8X6uiJvJj7mLrEyA7ofUg\noWdxsArp9pkQFqVyXTDdERP2yFFCp51E2vwsY9MZDKeieW0DLeRAondaWkKj\njgjjRwU3EyZ2wXRWeKsfydLAr6ufSqEvlGk4+fhgEiHAgaXKwkIY643lEeXX\nZCOV\r\n=KUpr\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDOWuPOrhTbepRHdqZv6gi+SUeYguvvrcRlQ8b/CPnbYgIgfym+AyTYqIRc3jVnN6lRvFT2EIE7Ca8K00DlXh5Z86k="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.58_1599674835731_0.5192746763617653"},"_hasShrinkwrap":false,"deprecated":"Deprecated - use IBM Cloud CLI instead, Checkout migration at https://cloud.ibm.com/docs/services/DevOpsInsights?topic=DevOpsInsights-migration-ibmcloud-cli"},"0.1.59":{"name":"grunt-idra3","version":"0.1.59","description":"Grunt Plugin for IBM DevOps Insights","main":"Gruntfile.js","directories":{"test":"tests"},"scripts":{"test":"grunt test"},"bin":{"idra":"bin/runidra.js"},"keywords":["IBM DevOps Insights"],"author":"","license":"MIT","devDependencies":{"chai":"^4.1.2","grunt":"^1.0.3","grunt-contrib-clean":"^1.0.0","grunt-eslint":"^23.0.0","grunt-mocha-test":"^0.12.7","mocha":"^5.2.0","sonar-scanner":"^1.0.1"},"dependencies":{"async":"^3.2.0","command-line-args":"^4.0.6","extend":"^3.0.1","glob":"^7.1.2","inquirer":"^7.3.3","mime":"^1.4.1","request":"^2.88.2","url":"^0.11.0","valid-url":"^1.0.9","xml2js":"^0.4.19"},"readme":"# idra\n\n> Command Line utility for integrating with IBM® DevOps Insights\n\nTo install this utility\n```\nnpm install -g grunt-idra3\n```\n\n# Table of Contents\n1. [Concepts](#concepts)\n2. [Getting Started](#getting-started)\n 1. [Scenarios](#scenarios)\n 2. [Prerequisites](#prerequisites)\n 3. [Environment Variables](#environment-variables)\n 4. [Enabling Debug Logs](#enabling-debug-logs)\n 5. [Using the CLI](#using-the-cli)\n3. [Upload Build Records](#upload-build-records)\n4. [Upload Test Results](#upload-test-results)\n 1. [Upload SonarQube Results](#upload-sonarqube-results)\n5. [Upload Deployment Records](#upload-deployment-records)\n6. [Making decisions about build quality using gate policies](#making-decisions-about-build-quality-using-gate-policies)\n\n## Concepts\nIBM® DevOps Insights is a tool that provides insights into your DevOps projects. Use it to learn how compliant your team is with DevOps and developer practices, to manage risk in your codebase, and to automatically enforce quality standards in continuous delivery projects.\n\nUnderstanding of the following concepts will help in faster adoption of IBM® DevOps Insights for your projects.\n\n##### Toolchain\nToolchains are part of [IBM® DevOps Continuous Delivery](https://console.bluemix.net/docs/services/ContinuousDelivery/cd_overview.html#cd_overview). Toolchains provide an integrated set of tools to build, deploy and manage your apps. You can create toolchains that include IBM Cloud services, open source tools, and third party tools that make development and operations repeatable and easier to manage. It is required that the IBM DevOps Insights should be added as one of the tool to your toolchain.\n\n##### Integrating your build tool with IBM DevOps Insights\nThis means instrumenting your build tool with this CLI or DevOps Insights Jenkins plugin to send build, test and deployment records to IBM DevOps Insights.\n\n##### Build record\nIBM DevOps Insights needs to know when a build is complete. This record contains application name, branch, build id, reference to git repo and other fields. This CLI and Jenkins plugin has a command to publish the build record to DevOps Insights.\n\n##### Test record\nIBM DevOps Insights needs to know about the tests performed during the build process. It is necessary that the tests should generate some kind of JSON or XML based file. Here are the list of supported [format](supported-test-formats). The generated test file is published as a test record. Along with the test file this record contains application name, build id, type of tests and other fields. It is required that the application name and build id in the test record matches the one used in the build record for a given build. This CLI and Jenkins plugin has a command to publish test record to DevOps Insights.\n\n##### Deployment records\nIBM DevOps Insights needs to know about the deployments made during the deployment process. This record contains the application name, build id, environment name, status of the deployment and other fields. It is required that the application name and build id in the deployment record matches the one used in the build record for a given build. This CLI and Jenkins plugin has a command to publish a deployment to DevOps Insights.\n\n##### Build Id (or Number)\nThis is an arbitrary length string uniquely identifying each build. This id is used to tie the build, test and deployment records together so it is important to publish those records with the same id for a given build.\n\n##### Policy\nA policy is set of rules specified by the user that collectively defines what is considered a good set of test records for a given application build. Typically, one rule is added for each test record published to DevOps Insights. The policy rules are evaluated by the gate.\n\n##### Branch\nThis is the name of the branch in the source control system.\n\n##### Environment\nThis is the name of environment to which deployments are made during the build process.\n\n##### Data set\nThis is an arbitrary string that identifies the type of tests performed during the build process. Besides the standard names such as \"unit test\", \"fvt\". The tool allows the user to define a custom name.\n\n## Getting Started\n\nUse this utility to integrate IBM® DevOps Insights with Travis CI, Concourse, IBM Urban Code Deploy, IBM Continuous Delivery Pipelines and other CI/CD tools. If you are using Jenkins, use this [Jenkins plugin](https://plugins.jenkins.io/ibm-cloud-devops) instead.\n\nUsing this utility, you can\n - Publish build records, test records and deploy records to IBM® DevOps Insights \n - Make go/no-go decisions about a build's quality by using a Gate policy\n\nFor samples of dashboards in IBM® DevOps Insights, see [Value Proposition](https://plugins.jenkins.io/ibm-cloud-devops).\n\nFor more information about IBM DevOps Insights, see [the official documentation](https://console.bluemix.net/docs/services/DevOpsInsights).\n\n### Scenarios\nThis document covers two scenarios:\n1. You are integrating DevOps Insights with IBM Continuous Delivery tool.\n2. You are integrating DevOps Insights with other CI/CD tools (e.g., Travis CI, Concourse, IBM Urban Code Deploy, others)\n\n### Prerequisites\n\nTo use the CLI, you need to do the following. These steps should take about 10 minutes.\n\n1. A valid IBM Cloud account. If you don't have one, [register here](https://console.bluemix.net/registration).\n\n2. Once you have an account, you can create an API Key. Log in to [IBM Cloud](https://console.bluemix.net). Click on **Manage**->**Security**->**Platform API Key**. On that screen, create an API Key.\n\n3. An IBM Continuous Delivery toolchain. To create a toolchain:\n - Go to https://console.bluemix.net/devops\n - Click on **Create a Toolchain** button and then select **Build Your Own Toolchain** template. \n - In the next screen, click **Create**.\n - From the URL displayed in the browser, make note of your toolchain id. For example, if your URL is https://console.bluemix.net/devops/toolchains/05572df3-01dc-441b-911d-b2202fe33f96, the toolchain id is the long string after **toolchains/**\n - You can always navigate to your toolchain by [clicking here](https://console.bluemix.net/devops)\n\n4. Add DevOps Insights tool to your toolchain\n - Go to your toolchain\n - Click on **Add a Tool** button\n - Select DevOps Insights tool and click **Create Integration** button\n\n5. Your CI/CD tool must have Node.js® 4.x or greater.\n\n### Environment Variables\n\nIf you are using Travis, Concourse or any CI/CD tool other than the IBM Continuous Delivery pipeline, then set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|TOOLCHAIN_ID| **Required.** The toolchain's GUID |\n|IBM_CLOUD_API_KEY| **Required.** The Bluemix user's Api key|\n|BUILD_NUMBER| **Required.** Any string that identifies the build. You also have the option of specifying build number using the `--buildnumber` parameter, in which case this environment variable is not required. |\n|LOGICAL_APP_NAME| **Required.** The application's name. You also have the option of specifying application's name using the `--logicalappname` parameter, in which case this environment variable must not be set. It is an error to set both the environment variable and the parameter.|\n\nIf you are using IBM Continuous Delivery pipeline, you need to set the following environment variables:\n\n|Name|Description|\n|-----|-----|\n|IBM_CLOUD_API_KEY| **Required** The Bluemix user's Api key|\n|BUILD_PREFIX| **Required.** Any string. For example, the Git branch name. If the `--buildnumber` parameter is used to pass a build number then this environment variable is not required.|\n|LOGICAL_APP_NAME| **Required.** The application's name. You also have the option of specifying application's name using the `--logicalappname` parameter, in which case this environment variable must not be set. It is an error to set both the environment variable and the parameter.|\n|PATH|**Required.** In order to have required version of Node.js in your path, set the PATH variable before invoking the utility: `export PATH=/opt/IBM/node-v4.2/bin:$PATH`|\n\nIf you are using IBM Continuous Delivery pipeline and if you want to publish Insights data to another toolchain, then set the following environment variables. \n\n|Name|Description|\n|-----|-----|\n|TOOLCHAIN_ID| **Required.** The target toolchain's GUID. If the target toolchain is owned by different user then provide the target toolchain owner's Bluemix Api key in the `IBM_CLOUD_API_KEY` variable.|\n\n\nIf you are using IBM UrbanCode Deploy, DevOps Insights relies on the previous set of variables, and this one:\n\n|Name|Description|\n|-----|-----|\n|UCD_REQUEST_ID| This maps to the ${p:request.id} property value. |\n\n### Enabling Debug logs\nIf you want to enable debug logs for the DevOps Insights CLI, set the `IDRA_DEBUG` environment variable to `true`. This works in all environments.\n\n|Name|Description|\n|-----|-----|\n|IDRA_DEBUG| When this value is `true`, the DevOps Insights CLI's debugging mode is enabled. By default, the value is `false`. |\n\n\n### Using the CLI\n\nSet [environment details](#environment-details) as described above. Ensure that Node.js 4.2 or higher is avaialble in your CI/CD tool.\n\nTo install this utility, use `npm install -g grunt-idra3`\n\nThen you can invoke the CLI with the `idra` command. You can run the CLI in any pipeline job's command script. For example, this command uploads functional verification test results to DevOps Insights:\n\n```\n# Upload test results\nidra --publishtestresult --filelocation=\"results.json\" --type=fvt\n```\n\n\n## Upload Build Records\nUse the `--publishbuildrecord` command (alias `-b`) to upload build records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishbuildrecord --branch= --repositoryurl= --commitid= --status= --logicalappname= --buildnumber= [--joburl=] [--buildnumber=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--branch`|`-B` | **Required.** The repository branch on which the build is being performed. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--repositoryurl`|`-R` | **Required.** The url of the git repository. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--commitid`|`-C` | **Required.** The git commit id. This value is not required in IBM Continuous Delivery pipeline environment|\n|`--status`|`-S` | **Required.** The build status. This value must be either `pass` or `fail`. |\n|`--logicalappname`|`-L` | _Optional_. The application's name. If this parameter is specified, environment variable **LOGICAL_APP_NAME** must not be set. |\n|`--buildnumber`|`-N` | _Optional_. Any string that identifies the build. This option overrides the value provided by **BUILD_NUMBER** or **BUILD_PREFIX** environment variables. |\n|`--joburl`|`-J` | _Optional_. The URL to the job's build logs. |\n\n\n\n### An example command\n\nIn this an example, the command uploads a build record from a pipeline job.\n\n```shell\nidra --publishbuildrecord --branch=master --repositoryurl=\"https://github.com/oic/dlms.git\" --commitid=dff7884b9168168d91cb9e5aec78e93db0fa80d9 --status=pass --logicalappname=appname --buildnumber=release:17\n```\n\n## Upload Test Results\n\nUse the `--publishtestresult` command (alias `-p`) to upload results from these test types to DevOps Insights:\n\n* Unit tests\n* Code coverage tests\n* Functional verification tests (FVT)\n* Static security scans from IBM Application Security on Cloud\n* Dynamic app scans from IBM Application Security on Cloud\n* [SonarQube results](#upload-sonarqube-results)\n* [Vulnerability Advisor](https://cloud.ibm.com/docs/services/va)\n\n\n### Command syntax and options\n\n```shell\nidra --publishtestresult --filelocation= --type= --logicalappname= --buildnumber= [--drilldownurl=] [--env=] [--token=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--filelocation`| `-F` |**Required.** The location of the test results that you want to upload. This can be a single file, an entire directory, or multiple files that match a wildcard expression.|\n|`--type`| `-T` |**Required.** The type of test results that you want to upload. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, `sonarqube` for SonarQube scans, and `vulnerabilityadvisor` for Vulnerability Advisor scans. In addition to these types you can also use a custom quality data set tag to upload test results of different type.|\n|`--logicalappname`|`-L` | _Optional_. The application's name. If this parameter is specified, environment variable **LOGICAL_APP_NAME** must not be set. |\n|`--buildnumber`|`-N` | _Optional_. Any string that identifies the build. This option overrides the value provided by **BUILD_NUMBER** or **BUILD_PREFIX** environment variables. |\n|`--drilldownurl`| `-U` |_Optional._ A URL where more information about the test results can be found. If this URL is invalid, the option is ignored. |\n|`--env`| `-E` |_Optional._ The environment name to associate with the test results. This option is ignored for unit tests, code coverage tests, and static security scans. |\n|`--token`| `-K` |_Optional_. This is a SonarQube token. This flag is valid only if the type specified is `sonarqube`. It is used by the CLI to pull additional information from the SonarQube server. |\n\n### An example command\n\nIn this example, the command uploads all JSON-formatted FVT results from a directory to DevOps Insights. Additionally, a test tool is declared, a test result URL is given, and a logical staging environment is provided. Specifying an environment is especially important when you want your results to be analyzed alongside other activities that take place in that same environment.\n\n```shell\nidra --publishtestresult --filelocation=\"tests/fvt/*.json\" --type=fvt --logicalappname=appname --buildnumber=release:17 -drilldownurl=\"https://example.com/testinfo\" --env=\"staging\"\n```\n\n### Supported Test Formats\n|Type of Test|tag|Supported Formats|\n|-----|-----|-----|\n|Unit Test|`unittest`|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Test Case|`fvt`|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Code Coverage|`code`|Cobertura (xml), lcov, Istanbul, JaCoCo|\n|SonarQube|`sonarqube`|SonarQube|\n|Static Security Scan|`staticsecurityscan`|IBM Application Security on Cloud|\n|Dynamic Security Scan|`dynamicsecurityscan`|IBM Application Security on Cloud|\n|Vulnerability Advisor|`vulnerabilityadvisor`|JSON output of the command [ibmcloud cr va](https://cloud.ibm.com/docs/cli?topic=container-registry-cli-plugin-containerregcli#bx_cr_va)|\n|Custom Data Sets - Tests|Custom Tag*|JUnit, xUnit, Mocha (mocha JSON reporter), KarmaMocha (karma-mocha-reporter)|\n|Custom Data Sets - Code Coverage|Custom Tag*|Cobertura (xml), lcov, Istanbul, JaCoCo|\n\nFor golang [gocov](https://github.com/axw/gocov/) users, please convert to Cobertura using [gocov XML(Cobertura) export](https://github.com/yaoyaozong/gocov-xml)\n\n\\* For custom tags create a quality data set by using the user interface. Navigate to your toolchain, click on DevOps Insights card. Navigate to quality dashboard. Click on the Kebab menu which is to the top-right of the quality dashboard. Click on **Configure Quality Data Sets**\n\n### Upload SonarQube Results\nTo upload data from SonarQube, you must provide the SonarQube server token using `--token`. Your SonarQube server is not required to be accessible from your CI/CD tool.\n\nAfter you run a scan using SonarQube, you can upload SonarQube results by running this command.\n\n```\nidra --publishtestresult --filelocation=.scannerwork/report-task.txt --type=sonarqube --token=234234434\n```\n\nIn the above command, report-task.txt is a file generated during the SonarQube scan.\n\nIf this command fails for some reason, you can enable logs by setting IDRA_DEBUG environment variable to true.\n\nIf you are using self-signed certificates for SonarQube server, you will need to set `export NODE_TLS_REJECT_UNAUTHORIZED=0`\n\n## Upload Deployment Records\nUse the `--publishdeployrecord` command (alias `-d`) to upload deployment records to DevOps Insights.\n\n### Command syntax and options\n\n```shell\nidra --publishdeployrecord --env= --status= --joburl= --logicalappname= --buildnumber= [--appurl=] [--deployableid=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--env`|`-E` | **Required.** The environment where the pipeline job deployed the app. |\n|`--status`|`-S` | **Required.** The deployment status. This value must be either `pass` or `fail`. |\n|`--joburl`|`-J` | **Required.** The URL to the job's deployment logs. |\n|`--logicalappname`|`-L` | _Optional_. The application's name. If this parameter is specified, environment variable **LOGICAL_APP_NAME** must not be set. |\n|`--buildnumber`|`-N` | _Optional_. Any string that identifies the build. This option overrides the value provided by **BUILD_NUMBER** or **BUILD_PREFIX** environment variables. |\n|`--appurl`|`-A` | _Optional._ The URL where the deployed app is running. |\n|`--deployableid`| `-I` | _Optional._ The deployed app's application ID. You can get the ID by running the Cloud Foundry CLI's `cf env` command. The application ID is listed under `VCAP_APPLICATION`. |\n\n### An example command\n\nIn this an example, the command uploads a deployment record from a pipeline job. The deployment is to the \"staging\" environment. The deployment is successful and the app is running at a specified URL.\n\n```shell\nidra --publishdeployrecord --env=\"staging\" --status=pass --joburl=\"https://app.staging.example.com\" --logicalappname=appname --buildnumber=release:17\n```\n\n## Making decisions about build quality using gate policies\n\nTo use this feature, create a quality policy by using the user interface. Navigate to your toolchain, click on **DevOps Insights** card. Then on the left menu, click on **Policies**.\n\nUse the `--evaluategate` command (alias `-g`) to request a gate decision for a DevOps Insights policy in your pipeline. If the policy is satisfied, the pipeline continues running. If not, and you use the `--forcedecision` flag, the pipeline stops running.\n\n### Command syntax and options\n\n```shell\nidra --evaluategate --policy= --logicalappname= --buildnumber= [--forcedecision] [--type=]\n```\n\n|Option |Alias |Description|\n|----------------|-----------------|-----------|\n|`--policy`|`-P` | **Required.** The name of the policy that the gate uses to make its decision. |\n|`--logicalappname`|`-L` | _Optional_. The application's name. If this parameter is specified, environment variable **LOGICAL_APP_NAME** must not be set. |\n|`--buildnumber`|`-N` | _Optional_. Any string that identifies the build. This option overrides the value provided by **BUILD_NUMBER** or **BUILD_PREFIX** environment variables. |\n|`--forcedecision`|`-D` | _Optional._ Set the value to `true` to cause the process to exit with an error code, if the policy evaluation fails. The value defaults to `false` if this option is not specified. |\n|`--type`|`-E` | _Optional_. A rule type to consider. If you include this option, only rules of this type are considered in the decision-making process. The value can be `code` for code coverage, `unittest` for unit tests, `fvt` for FVT tests, `staticsecurityscan` for static security scans, `dynamicsecurityscan` for dynamic app scans, and `sonarqube` for SonarQube scans. |\n\n### An example command\n\n```shell\nidra --evaluategate --policy=\"somepolicy\" --logicalappname=appname --buildnumber=release:17\n```\n\n## Release History\n\n_(Nothing yet)_\n","readmeFilename":"README.md","gitHead":"006a0d9147b0be46b8d8dd9fe2a9519c1f010f1d","_id":"grunt-idra3@0.1.59","_nodeVersion":"12.10.0","_npmVersion":"6.10.3","dist":{"integrity":"sha512-UZlQRV/AgXmpqLRdAvfaPnQtDgQRrCIFLvsh/7QKaY+nz8l0b86xB//zqTTEZsp+dExq5e3yc1nHiHafkVrM5w==","shasum":"cd9cb31cb185284f0fb3e3edeaae378bde8028ad","tarball":"https://registry.npmjs.org/grunt-idra3/-/grunt-idra3-0.1.59.tgz","fileCount":49,"unpackedSize":222609,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.13\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJfbQFPCRA9TVsSAnZWagAAbNAP/Rp9Rrm0nWf46wQPGcBV\naVCgeB0yBKRlCpUe9WToozuQ9Ptnne2grwLztMZTqX6oWzgFz1LS9xl8MEiH\n9tMfW7MrDhRDi/FPGhvjcoiVjvXhmLC/3RUrL9K7kVR1BG6KFIo52CuQSXyI\nJBz++0xtOYz5Ke9jr40HyyKpnHv3WY6wQfeSK81uhNK76er6XAWufV09IxG9\nsS/BTs4KjHOR+wPuQyDJJ6HZN/3lqop2w8Uzsmh+wpIlwUceS4/n08dMpVLR\nS+dd0zDY6obT3DvQY0EkETSTgJJKSOvZhVXZA2G9/rPafu2PEcnVFLQRVimp\nlAsLUTDjA5cINtkb2jF9bYxvwzEj8lRon0dJEuDy0PcQzOh0ddShhA4cXoVL\nXq2P3smdRpZqU132d+AtoR0gU1OH53a87vliSTgDMrROH2RLwJkthXzuGZlr\nEHviORGZ2bIWxV9JAoZrbaCVgKU7S1INB0QGNqUHOMZGIkKzI94TzKDJqyog\njVcmfWIiCyeBCP7ItsBOt+a8fzoFooZn+ISg/5/S9EQwfdvpSTR/KnXF3hTb\nhEHkarCwgOE6V/UnNYoyfhY+mhsxVhoOQv3FFk8TCtC+2Z+zR0wkGs/mmvz0\nZLMbdS+YEFVLpGMieo5wvpQH3L7dV/V3b263uCni+ksR0bobruHb1JftTb+/\nLklL\r\n=4S/7\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIBO9v2mnOnyltQNivLCTa8W+O4WOnDtYcUZmDAOn9k8/AiBexFUL7GgJkNNx88NWVx9fUoZ3kVvz0uVnoEsKsOPvyQ=="}]},"maintainers":[{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"}],"_npmUser":{"name":"umesh.parulekar","email":"umesh.parulekar@gmail.com"},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/grunt-idra3_0.1.59_1600979274469_0.7511298382839242"},"_hasShrinkwrap":false}},"keywords":["IBM DevOps Insights"],"license":"MIT","readmeFilename":"README.md"}