Skip to content

[RHDEVDOCS-6475] Pipelines 1.17.2 Release Notes #94997

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: pipelines-docs-1.17
Choose a base branch
from
Open

[RHDEVDOCS-6475] Pipelines 1.17.2 Release Notes #94997

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions modules/op-release-notes-1-17.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -292,3 +292,18 @@ With this update, {pipelines-title} General Availability (GA) 1.17.1 is availabl
value: '--build-arg EXAMPLE="abc def"'
# ...
----

[id="release-notes-1-17-2_{context}"]
== Release notes for {pipelines-title} General Availability 1.17.2

With this update, {pipelines-title} General Availability (GA) 1.17.2 is available on {OCP} 4.12, 4.14, 4.15, 4.16, 4.17, and 4.18 versions.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
With this update, {pipelines-title} General Availability (GA) 1.17.2 is available on {OCP} 4.12, 4.14, 4.15, 4.16, 4.17, and 4.18 versions.
With this update, {pipelines-title} General Availability (GA) 1.17.2 is available from {OCP} 4.12 to {OCP} 4.18.

Previous release stated "and later versions" but maybe it should also be more precise?


[id="fixed-issues-1-17-2_{context}"]
=== Fixed issues

* Before this update, the `skopeo-copy` task required you to explicitly set the `source_image_url` and `destination_image_url` parameters. This requirement prevented the use of the `images_url` workspace with a `url.txt` file for batch image copying. With this update, both parameters default to empty values and are excluded from strict validation, allowing the task to fall back to the `url.txt` method as intended.

* Before this update, when you used matrixed tasks in a fan-out and fan-in pattern, the `PipelineRun` execution failed with the following error: `invalid result reference in pipeline task 'printer': unable to validate result referencing pipeline task 'platforms': task spec not found`. This issue occurred when a downstream task attempted to reference aggregated results from a matrixed task using the following syntax: `$(tasks.<taskName>.results.<resultName>[*])`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* Before this update, when you used matrixed tasks in a fan-out and fan-in pattern, the `PipelineRun` execution failed with the following error: `invalid result reference in pipeline task 'printer': unable to validate result referencing pipeline task 'platforms': task spec not found`. This issue occurred when a downstream task attempted to reference aggregated results from a matrixed task using the following syntax: `$(tasks.<taskName>.results.<resultName>[*])`.
* Before this update, when you used matrixed tasks in a fan-out and fan-in pattern, the `PipelineRun` execution failed with the following error: `invalid result reference in pipeline task 'printer': unable to validate result referencing pipeline task 'platforms': task spec not found`. This issue occurred when a downstream task attempted to reference aggregated results from a matrixed task by using the following syntax: `$(tasks.<taskName>.results.<resultName>[*])`.

With this update, {pipelines-shortname} correctly resolves and validates result references from matrixed tasks. This enables dynamic fan-out and fan-in task orchestration using arrays and matrix expressions without triggering validation errors.

* Before this update, there was no upgrade path from {pipelines-shortname} 1.16.x to later versions. With this update, the issue is fixed.