Components

A component is the key link between your source code and downstream features of the CloudBees platform, enabling secure, robust, and efficient software delivery. As a foundational element of the platform, a component may be as simple as a piece of software built and deployed from source code, or it can be part of a complex project composed of many connected components. Use the flexibility of a component to create and manage complex CI/CD workflows.

Components are defined by the following attributes:

Every component is created within an organization.
Every component is connected to a single code repository via an SCM integration.

Component details

View the components in your organization by selecting Components. Refer to Manage components to learn more about how to access and manage components in your organization. Select the Component name link next to the status icon to review detailed information for that component.

In the component details screen, use the tabbed navigation to access all the activities linked to a component.

Summary: Review a snapshot of component activity, including builds and deployments.
Runs: Review workflow executions and implicit scans.
Workflows: Review and edit workflow YAML files.
Security overview: Review vulnerabilities remediation trends and severity of findings.
Security center: Review issues identified by security tools.
Artifacts: Review details of generated artifacts and deployment history.
Environment inventory: Review artifact versions organized by their environment.
Properties: Review and update key/value pairs created in or inherited by the component.

Figure 1. An example component with tabs highlighted.

Component summary

Get a comprehensive view of activity for a component in the Summary. This dashboard includes commit, build, and deployment information, and provides detailed security scan results. Refer to Component summary to learn more.

Runs

Review details of every workflow execution in a component on Runs. This view includes trigger information, links to the workflow composer, the run completion date, and the run duration.

Figure 2. An example component run list with breadcrumbs and run highlighted.

If you have implemented implicit security scanning, the analysis runs are available in this list, as shown in the example above. To learn more about configuring implicit security scans, refer to Manage security tools.

This list is not identical to viewing runs by selecting Runs on the left pane, and then filtering by your component, as in the example below. This list does not include implicit security analyses.

Select the link next to a run status to view detailed information for that run. To learn more, refer to Runs.

Figure 3. An example run list with breadcrumbs and filter highlighted.

Workflows

View and manage workflows within a component.

Figure 4. An example component workflow list.

As in the above example, perform any of the following:

Switch to a different component using the breadcrumbs.
Select the workflow name to view the workflow YAML file.
Select Edit YAML to update the workflow YAML file.

For more information, refer to:

Manage workflows.
CloudBees DSL syntax for workflow YAML files.

Security overview

View security metrics for a component in Security overview, to assist with continuous security-posture management.

To learn more, refer to Security overview.

Security center

Review security issues and findings for a component in Security center.

An implicit security analysis is triggered when:

The component is created.
A commit is made to the repository linked with the component.

Refer to Security center for more information.

Artifacts

View a list of all artifacts generated by executed workflows in a component. To collect artifact data, a workflow must contain an action to register an artifact. In Artifacts, choose to list either the full version history or only the latest versions.

Figure 5. An example component artifact list of just the latest versions.

The above component artifact list example displays items not available in the Runs Build artifacts list:

The option to display the full version history. The default display (toggled off) shows only the latest versions.
A link to the associated run.
The date and time the artifact was created.
The deployment history, if applicable. Select to access details of all deployments for that artifact.

Figure 6. Deployment history of an example artifact.

To learn more, refer to:

Environment inventory

In the Environment inventory, get information on every artifact version in a component, organized by their environment. Artifacts are displayed only if they have been generated by running a workflow that has been configured to collect artifact data.

For more information, refer to:

Properties

View a list of properties associated with a component. Properties created both at the organization level (inherited) and on the component level (original) are displayed in Properties.

For more information, refer to Properties.

Component ID

Every component is identified by a unique multi-hexadecimal ID (UUID).

To locate the component ID, select a component from Components. Within the platform URL in your browser address bar, the component ID is displayed after componentId=.

In the example below, <COMPONENT_ID> is the component ID:

https://cloudbees.io/<YOUR_TENANT>/<ORGANIZATION_ID>/components/<COMPONENT_ID>?componentId=<COMPONENT_ID>&organizationId=<ORGANIZATION_ID>▼

The component ID is required for using some platform features, including: