Pipelines 1.27.5

JFrog Release Information


Released: October 04, 2022


Pipelines 1.27.5 and above requires Artifactory 7.41.6 or above.

Support for Multiple Pipeline Sources per Repository

Pipelines now supports the creation of multiple pipeline sources per repository. This change significantly improves the performance of your pipelines sync. For more information, see Adding a Pipeline Source.

Secure Project Integration Information

Project integration information is now protected when handling public Git repositories.

Allow Failure in Conditional Steps

A new boolean option called allowFailure has been introduced for conditional steps. The allowFailure option can be set for individual steps and can be used to ignore the current step’s failure while computing the final status of the run. For more information, see Adding Conditional Workflow for Steps.Conditional Workflows

New Utility Functions to Store and Restore Files between Steps in Affinity Group

Added add_affinity_group_files and restore_affinity_group_files utility functions to more easily use the affinity group workspace to share files between steps in an affinity group. For more information, see Affinity Group State Management.Affinity Group State Management

New Runs Charts

Pipelines runs charts show the behavior of the runs for the selected number of runs.

The following charts show how the runs performed:

  • Run Performance: Shows the median build time for the runs categorized based on the first and last build.

  • Execution Frequency: Shows the average runs.

  • Runs Status: Shows the run status and the time taken for each run.

For more information, see Pipelines Runs Charts.

Updated Go Build Image

Added support for Go 1.19 build image.

Support for JFrog CLI v2 Version 2.21.5

Pipelines now supports JFrog CLI v2 version 2.21.5.

Resolved Issues
  • Fixed an issue whereby, steps that produce test reports were failing to save them and timing out.

  • Fixed an issue whereby, a run was stuck in canceling when all the steps are in the final state and at least one step is in error/failure status.

  • More API calls will be retried when they fail in the TriggerPipeline native step.

  • When the re-trigger button is clicked, the new run is loaded when it is ready.

  • Improved performance when hard-deleting pipelines.