Pipelines 1.20

JFrog Release Information
Content Type
Release Notes
ft:sourceType
Paligo
Pipelines 1.20.8

Released: January 10, 2022

Note

Pipelines 1.20.8 requires Artifactory 7.29.8 and above.

Resolved Issues

  • Fixed an issue whereby, artifacts related to signed pipelines were not getting uploaded.

Pipelines 1.20.7

Released: December 31, 2021

Note

Pipelines 1.20.7 requires Artifactory 7.29.8 and above.

Highlights
Support for PostgreSQL Client 12.7

Pipelines installer now installs PostgreSQL client 12.7.

Resolved Issues

  • Fixed an issue where two parallel pipeline source sync requests resulted in resource not being created and caused pipeline sync to fail.

  • Fixed an issue with default W19 images whereby GCP integrations were not working.

  • Fixed an issue that was not allowing node pools and Project integration from the default Project to be shared with other Projects.

  • Fixed an issue that caused native Maven steps to fail when using default u20 build images.

  • Fixed an issue where multiple concurrent updates to the same incoming webhook resource caused the payload to be incorrect.

  • Fixed security issues related to Alpine and Azure.

  • Fixed an issue where RHEL 7 installation failed on GCP due to missing OpenSSL.

Pipelines 1.20.4

Released: December 20, 2021

Note

Pipelines 1.20.4 requires Artifactory 7.29.8 and above.

Note

As of this release, public access has been removed from routes used by nodes. As a result of this, Pipelines versions without authentication token (prior to Pipelines 1.10.1) might face issues with builds. For the builds to work correctly:

Highlights
Custom VM Images

Pipelines now supports custom VM images. A custom VM image enables you to use your own image as a node in Pipelines. Nodes launched using this new custom VM image would include all the customizations you made when you created the image. For more information, see Creating Custom VM Images.

Share Node Pools across Projects

Projects admins can now share node pools across multiple projects to allow members in more than one project to use them. A classic use case for sharing a node pool is the need to share computing resources when running pipelines from multiple projects. A node pool can be shared with a single project or across multiple projects. For more information, see Sharing Node Pools across Multiple Projects.Managing Pipelines Node Pools

Change Machine Type in Dynamic Nodes Pools

Pipelines now supports changing machine image type in dynamic node pools.

Dynamic Ubuntu 16 build nodes deprecated

This release of Pipelines removes support for dynamic Ubuntu 16 build nodes. After upgrading to 1.20.4, either remove any Ubuntu 16 node pools or change the machine image to a different OS.

Pipelines in Search Toolbar

Added the ability to select Pipelines and search for pipelines using the main search toolbar. The search can be filtered using Name, Branch, Triggered Before, and Triggered After. For more information, see Application SearchApplication Search

Searching for Pipelines.Searching for Pipelines

New Canvas and Butterfly Graphs

The graph view in Pipelines has now been updated to use canvas and butterfly graphs to provide a much smoother and faster experience.

Faster Pipeline Sync

Improved data fetching for faster pipeline sync.

Resolved Issues

  • Fixed an issue whereby, wrong run variables were used. When more than one run was triggered, values from one run were sometimes used by another run.

  • Fixed an issue whereby, authorized users were unable to approve a pending Approval Gates step.

  • Fixed an issue whereby, permissions were not working for named pipeline sources under the default Project.

  • Fixed an issue whereby, some data was missing from test reports in junit v1 formatted reports.

  • Fixed an issue that was causing GitRepo resource versions to sometimes lack the beforeCommitSha property.

  • Fixed an issue where some runs would not be triggered when over 100 resources were updated by a single webhook.

  • Fixed an issue where there was an error in the pod for K8s nodes and initializedAt field was not getting populated for the node.

  • Fixed an issue related to custom certificates.

  • Pipelines on-prem only: Fixed an issue whereby, on-prem users with self-managed k8s clusters could run only a single k8s pod on one build node. Users can now run multiple pods on a single build node.

  • Updated several third-party dependencies to improve security and stability.

Resolved Vulnerabilities

This release contains resolved CVEs - security vulnerability issues.