Pipelines 1.26.0

JFrog Release Information


Released: September 01, 2022

Helm v2 and JFrog CLI v1 Deprecated

Helm v2 Deprecated

Helm v2 is deprecated and will be removed. We recommend moving to Helm v3, which is already pre-installed in the default build images. If you are using the HelmDeploy or HelmPublish native steps, you can choose the version in your YAML with the helmVersion: 3 tag.HelmDeployHelmPublish

JFrog CLI v1 Deprecated

JFrog CLI v1 is deprecated and will be removed. We recommend moving your pipelines to JFrog CLI v2. To make this transition as smooth as possible, all native steps have already been enhanced to support v2. To update your pipeline to switch to v2, simply add jfrogCliVersion: 2 to your pipelines.configuration section in your YAML. This will cause the jfrog command to point to v2 instead of v1.


Pipelines 1.26.0 and above requires Artifactory 7.41.6 or above.

New UI enabled by default

The Pipeline and Run views now use the new UI by default. The new look and feel were introduced in Pipelines 1.24.0.

Test Tab Enhancements

In the Run view, the test tab has been enhanced:

  • Shows the test results summary, with an aggregate count for Success, Failure, Error, and Skipped

  • Includes a tab for each of the test results section - Success, Failure, Error, and Skipped and each tab:

    • Includes a list of test suites and test cases with the test name, duration, and path details

    • Shows a summary of test statuses (Success, Failure, Error, and Skipped) at the test suite level

    • Shows error messages for error and failure tests

For more information, see Tests Tab.

Re-Trigger Run Option

The Run view now includes a re-trigger button, which enables you re-trigger any run using either the run's original settings or customized settings.

YAML Validator

Pipelines introduces YAML validator, which enables you to validate your YAMLs before committing them to the SCM. The YAML validator can be used to validate your YAMLs for both semantic and syntactic errors. For more information, see Validating YAML.

Native Steps Enhanced to Utiliize Affinity Groups

A new get_affinity_group_step_names utility function has been introduced to find steps of a particular type in the same affinity group. For information, see get_affinity_group_step_names.Step Properties

In addition, NpmBuild and NpmPublish, and GoBuild and GoPublishBinary native steps will now store files locally when in the same affinity group to reduce the time required to run these steps.

Logstash Integration to reqKick

Added build node and Logstash integration for Pipelines agent logs. For more information, see Sending Pipelines Nodes Agent Logs to Logstash.Sending Pipelines Nodes Agent Logs to Logstash

Get Pipeline Sync Status API Search Improvements

The GET pipelineSyncStatuses API has been updated with a new parameter called pipelineSourceBranchPattern to support search by branch name regex and latest status. For more information, see Get Pipeline Sync Status.Get a Pipeline Sync Status

Global Environment Variable in Pipelines

Pipelines now provides the ability to expose global environment variables to the entire Pipelines ecosystem. The global environment variables are available for use in runs and steps. For information, see Environment Variables API.ENVIRONMENT VARIABLES

Hello World OOTB Template

A new global template called HelloWorld is now available for use out of the box. The template showcases a few of the basic features of Pipelines:

  • Parallel steps

  • Reading and writing variables that persist across different steps in your pipeline

  • Reading from and writing to resources

  • Setting environment variables

  • Optional GitRepo resource so that users can experiment via the values.yml

Additionally, a sample pipeline that uses this template will be pre-installed for Pipelines users who have not yet created any pipeline source. For more information, see Hello World Global Template.Global Templates

Custom Dynamic Nodes on SaaS

SaaS users can now create custom dynamic nodes (using user-defined integrations) and customize all the relevant settings. Users can select any cloud provider with no restrictions on settings, such as machine type, region, and others.

Ability to Change Resource Static Fields

Lifted restrictions on updating some tags from their original values in resource configurations. The following resource tags can now be updated: imageName tag for Image resource, fileLocation and fileName tags for RemoteFile resource, and path tag for GitRepo resource.

Resolved Issues
  • Fixed an issue whereby, proxy settings were not included in the environment when running steps on the host on a static Linux node.