PulseUno includes an extensive set of plugins to use in chains.
Tip: You can add more chain plugins in addition to the standard PulseUno set. For details, see Use plugins.
Use these plugins to run builds.
|Ant||Runs an Ant build.|
|CM Build||If your team uses Dimensions Build and you have existing build configurations, you can run the configurations in PulseUno.|
|Dimensions CM command line||Enables you to enter dmcli commands.|
|Gradle||Runs a Gradle build.|
|Jenkins||A continuous integration server that you can use with PulseUno to run and report on builds of changesets as they are delivered.|
|Makefile||Runs a build using a makefile.|
|Maven||Builds and distributes artifacts.|
|MSBuild||Runs an MSBuild.|
|Script||Runs a batch script (Windows) or shell script (Linux).|
|Visual Studio Build||Runs a Microsoft Visual Studio Build.|
Use these plugins to capture built artifacts.
|Capture to DA CodeStation||Captures built artifacts to Deployment Automation CodeStation. These artifacts represent deployable items such as files, images, databases, configuration materials, or any other assets associated with a software project.|
|Capture to Dimensions CM||Captures built artifacts to a Dimensions CM stream.|
|Capture to Directory||Captures built artifacts to a directory.|
|Capture to SCP/SFTP||Captures built artifacts to a workspace using secure copy (SCP) or to remote network server using Secure File Transfer Protocol (SFTP).|
Use these plugins for Docker images and containers.
|Build a Docker Image||Builds a Docker image in which you can run applications.|
|Run a Docker Container||Creates a Docker container in which you can run Docker images.|
|Run Script in Docker Container||Use a command to run a script in a Docker container that is running, without logging into that container.|
Use these plugins to run a dependency analysis.
|CycloneDx Dependency Detector||A lightweight software bill of materials (SBOM) specification designed for use in application security contexts and supply chain component analysis.|
|Maven Dependency Detection||Analyzes the dependencies of a project and determines which are: used and declared; used and undeclared; unused and declared.|
|npm Dependency Detection||Checks which modules you have used in your code and lists them as dependencies in your package.json.|
Use these plugins to run Deployment Automation deployments and processes:
|Deploy via Deployment Automation||Imports and deploys a component using Deployment Automation.|
|Run a Deployment Automation Generic Process||Runs a generic process in Deployment Automation.|
Use these plugins to fetch sources from repositories.
|Fetch from Dimensions CM||Fetches sources from a Dimensions CM repository.|
|Fetch from Git||Fetches sources from a Git repository.|
|Fetch from StarTeam||Fetches sources from a StarTeam repository.|
Security and compliance
Use these plugins to identify security vulnerabilities in your code.
|Dependency Vulnerabilities||Finds third-party dependencies in your code that may have known security vulnerabilities.|
|Fortify SCA (Static Code Analyzer)||Analyzes your source code and identifies the root causes of security vulnerabilities.|
|Fortify ScanCentral SAST||
Offloads the translation and scanning phases of code analysis to remote Fortify ScanCentral SAST sensors.
Can publish the scan results to Fortify Software Security Center (SSC) and pull them from Fortify SSC to generate findings in PulseUno.
|Fortify SSC (Software Security Center)||Uploads scan results generated by Fortify SCA to Fortify Software Security Center.|
|WhiteSource||Identiﬁes all the open-source components and dependencies in your build, reports any known security vulnerabilities, and lists their licenses.|
Use these plugins to analyze the quality of your code.
|Checkstyle||Enforces coding standards.|
|Copyright header checker||Checks files for the presence of copyright statements or other snippets.|
|Kiuwan||Measures, analyzes, and verifies the quality of your code.|
|PMD||Analyzes source code and finds common programming bugs.|
|SonarQube||Inspects the quality of your code.|
Use these plugins to run tests.
|CTest Parser||Parses CTest results files.|
|JUnit Parser||Parses JUnit results files.|
|LoadRunner||Runs LoadRunner performance test scenario.|
|LoadRunner Cloud||Runs LoadRunner Cloud load tests.|
|UFT Developer Reports||Captures UFT Developer reports.|
|UFT One||Runs UFT One file system-based tests.|
|MSTest Parser||Parses MSTest results files.|
|NUnit Parser||Parses NUnit results files.|
|TestNG Parser||Parses TestNG results files.|
These plugins provide statistics, notification, and other chain functions.
|Changeset Summary||Counts the number of files added, deleted, and modified in each changeset.|
|Code Summarizer||Reports about lines in files, code languages, and other code-related information.|
|Email Notification||Sends email notifications to users.|
|Halt on Failure||Stops a chain if the previous plugin in the chain failed.|
|Microsoft Teams Notification||Adds a Microsoft Teams notification using WebHook.|
|Run another chain||Runs another chain that you have created.|
Chain plugins have the following optional attributes.
|Execution state||The following states are used: Success, Failure, Unstable, or Stopped.|
|Measurement||A set of single-valued judgments about source code. For example, 24,847 might be a measurement of lines of code, and High might be a measurement of the security risk level.|
When issues are identified, chain plugins annotate the source code and provide a severity level to indicate how serious an issue is.
Findings are displayed as a list of messages for each plugin. Messages are divided by type, such as Errors, Warnings, Failures, or Information. Some findings may include a link to a web page that provides more details. For details, see Inspect chain runs in reviews.