Description
CircleCI is a modern continuous integration and continuous delivery (CI/CD) platform. CircleCI automates build, test, and deployment of software.
The CircleCI plug-in imports CI/CD data from CircleCI.
CircleCI is a modern continuous integration and continuous delivery (CI/CD) platform. CircleCI automates build, test, and deployment of software.
The CircleCI plug-in imports CI/CD data from CircleCI.
The CircleCI plugin for HCL DevOps Velocity (beta) synchronizes pipelines, workflows and job executions of a CicleCI project with HCL DevOps Velocity. The project can be configured as an application in an HCL DevOps Velocity pipeline and CircleCI jobs can be configured in the HCL DevOps Velocity pipeline. The Accelerate Pipeline displays the latest version of the application deployed to the different environments.
The CircleCI plug-in requires HCL DevOps Velocity version 2.2.0 and later.
Currently, this plug-in does not support deployments to CircleCI from HCL DevOps Velocity.
To use the Handlebar Reporter plugin, the plugin must be loaded and an instance created before you can configure the plugin integration. You define configuration properties in the user interface or in a JSON file.
The Handlebar Reporter plugin supports scheduled events integration which are listed in the following table.
| Name | Description |
|---|---|
| handlebarsRunner | Generates a report. |
There are two methods to integrate the plugin:
The JSON file contains the information for creating a value stream and integrating with the Handlebar server. The following table describes the information for the creating an HCL Accelerate value stream map.
The following tables describe the properties used to configure the integration. Each table contains the field name when using the user interface and the property name when using a JSON file.
properties configuration property.Some properties might not be displayed in the user interface, to see all properties enable the Show Hidden Properties field.
| Name | Description | Required | Property Name |
|---|---|---|---|
| NA | The version of the plug-in that you want to use. To view available versions, click the Version History tab. If a value is not specified, the version named latest is used. | No | image |
| Integration Name | An assigned name to the integration. | Yes | name |
| Logging Level | The level of Log4j messages to display in the log file. Valid values are: all, debug, info, warn, error, fatal, off, and trace. | No | loggingLevel |
| NA | List of plug-in configuration properties used to connect and communicate with the CircleCI server. Enclose the properties within braces. | Yes | properties |
| The name of the tenant. | Yes | tenant_id | |
| NA | Unique identifier assigned to the plug-in. The value for the CircleCI plug-in is ucv-ext-circleci. |
Yes | type |
| Name | Type | Description | Required | Property Name |
|---|---|---|---|---|
| Access Token | String | The access token to authenticate with CircleCI. | Yes | accessToken |
| Repositories | Array | A comma seperated list of repositories from which to import pull requests, commits, and build data. | Yes | repositories |
| Proxy Server | String | The URL of the proxy server including the port number. | No | proxyServer |
| Proxy User Name | String | The user name used to authenticate with the proxy server. | No | proxyUsername |
| Proxy Password | String | The password used to authenticate with the proxy server. | No | proxyPassword |
| URL | String | API URL of CircleCI. | Yes | apiUrl |
| User Access Key | String | The user access key to authenticate with the HCL DevOps Velocity server. | Yes | accelerateAccessKey |
| Project type (VCS provider) | String | The Version Control System that is used, eg: github, bitbucket. | Yes | projectType |
| Organization Name | String | The username or organization name in the version control system. | Yes | orgName |
| Branch | String | The branch for which build data is to be synced. If nothing is specified, the default_branch of the project will be used. | No | branch |
The following sample code can be used as a template to define the integration within the JSON file for a value stream. Copy and paste the template into the JSON file Integration section and make the appropriate changes.
"integrations": [
{
"type": "ucv-ext-circleci",
"tenant_id": "tenantid",
"name": "CircleCI_Plugin ",
"properties": {
"apiUrl": "circleci_server_url",
"velocityAccessKey": "velocity_access_key",
"accessToken": "circleci_access_token",
"projectType": "circleci_projct_type",
"orgName": "circleci_org_name",
"repositories": [
"CiecleCI-Project"
],
"proxyServer": "proxy_server_url",
"proxyUsername": "proxy_server_user_name",
"proxyPassword": "proxy_server_password"
}
} ]
Uploaded: 27-Dec-2022 08:53
docker pull hclcr.io/accelerate/ucv-ext-circleci:1.0.24
Uploaded: 11-Aug-2022 15:42
docker pull hclcr.io/accelerate/ucv-ext-circleci:1.0.22
Uploaded: 07-Jun-2022 05:33
docker pull hclcr.io/accelerate/ucv-ext-circleci:1.0.18
Uploaded: 01-Mar-2022 08:59
docker pull hclcr.io/accelerate/ucv-ext-circleci:1.0.16
Uploaded: 08-Feb-2021 07:33
Uploaded: 08-Feb-2021 07:33