vRealize Code Stream automates the software release process by modeling all the necessary tasks in pipeline templates.
Overview of vRealize Code Stream
A release pipeline is a sequence of stages. Each stage is composed of multiple tasks and environments that the software must complete before it is released to production. The stages can include development, functional testing, user acceptance test (UAT), load testing (LT), systems integration testing (SIT), staging, and production. Release managers can model and build pipelines, and release engineers can run pipelines.
Each stage in a pipeline includes a set of activities. The activities can provision a machine, retrieve an artifact, deploy software, run a test, create a manual task, or run a custom workflow or script, and so on.
When the software changes satisfy a set of rules called gating rules, they are promoted to the next stage in the pipeline. The gating rules include testing rules and compliance rules. Gating rules that are associated with a pipeline are specific to an organization or an application. Users can define gating rules when a pipeline template is created.
This release improves the performance and stability of the core platform, and the integrations with vRealize Automation and Cloud Foundry.
Key Features in Previous Releases
The previous release of vRealize Code Stream simplified licensing, provided pipeline triggering utilities to enhance developer use cases, included new plug-ins to integrate with external systems over REST, and provided easier pipeline import and export capability. With simplified licensing, you can enable your vRealize Code Stream license from the VMware Application Management Interface.
The vRealize Code Stream Trigger for Git integrates vRealize Code Stream with the Git lifecycle. The Trigger for Git enables events from GitHub Enterprise or GitLab Enterprise to trigger a pipeline. When developers change their code in a GitHub or GitLab repository, the change triggers an event. That event passes through a Webhook to the trigger for Git, which triggers the pipeline. For more information about the vRealize Code Stream Trigger for Git, see https://code.vmware.com.
The vRealize Code Stream Trigger for Gerrit integrates vRealize Code Stream with the Gerrit code review lifecycle. The Trigger for Gerrit enables reviews and merges of developer code to trigger a pipeline based on events. When developers create a patch set for a code change, or merge code changes, Gerrit sends the change events to the trigger for Gerrit. The events trigger the tasks in your pipeline. For more information about the vRealize Code Stream Trigger for Gerrit, see https://code.vmware.com.
The following video explains these features.
Also a previous release of vRealize Code Stream extended Role-Based Access Control (RBAC) to pipeline templates, offered the ability to resume a failed pipeline execution from the point of failure, and supported integration with remote jFrog Artifactory instances. It also introduced a Plug-in SDK to build custom plug-ins for vRealize Code Stream.
Components of vRealize Code Stream
The following diagram shows the primary components included in vRealize Code Stream.