[release-4.20] OCPBUGS-64857: BuildConfig inline Dockerfile fails with heredoc syntax by openshift-cherrypick-robot · Pull Request #483 · openshift/builder

openshift-cherrypick-robot · 2025-11-10T14:46:11Z

This is an automated cherry-pick of #469

/assign kunalmemane

When writing out the contents of a parsed Dockerfile, attempt to reproduce heredocs that followed instructions. Signed-off-by: Nalin Dahyabhai <nalin@redhat.com>

openshift-ci-robot · 2025-11-10T14:46:23Z

@openshift-cherrypick-robot: Jira Issue OCPBUGS-62210 has been cloned as Jira Issue OCPBUGS-64857. Will retitle bug to link to clone.
/retitle [release-4.20] OCPBUGS-64857: BuildConfig inline Dockerfile fails with heredoc syntax

Details

In response to this:

This is an automated cherry-pick of #469

/assign kunalmemane

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

openshift-ci-robot · 2025-11-10T14:46:36Z

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-64857, which is invalid:

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
expected dependent Jira Issue OCPBUGS-62210 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

This is an automated cherry-pick of #469

/assign kunalmemane

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

openshift-ci · 2025-11-10T17:46:41Z

@openshift-cherrypick-robot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/okd-scos-e2e-aws-ovn	`2aae31b`	link	false	`/test okd-scos-e2e-aws-ovn`
ci/prow/security	`2aae31b`	link	false	`/test security`

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

moebasim · 2025-11-12T12:51:56Z

/verified by mbasim@redhat.com

openshift-ci-robot · 2025-11-12T12:52:06Z

@moebasim: Jira verification commands are restricted to collaborators for this repo.

Details

In response to this:

/verified by mbasim@redhat.com

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

moebasim · 2025-11-12T12:53:19Z

/jira refresh

openshift-ci-robot · 2025-11-12T12:53:24Z

@moebasim: This pull request references Jira Issue OCPBUGS-64857, which is invalid:

expected dependent Jira Issue OCPBUGS-62210 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

moebasim · 2025-11-12T12:54:14Z

/jira refresh

openshift-ci-robot · 2025-11-12T12:54:18Z

@moebasim: This pull request references Jira Issue OCPBUGS-64857, which is invalid:

expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Verified instead
expected dependent Jira Issue OCPBUGS-62210 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

moebasim · 2025-11-12T12:55:07Z

/jira refresh

openshift-ci-robot · 2025-11-12T12:55:15Z

@moebasim: This pull request references Jira Issue OCPBUGS-64857, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.20.z) matches configured target version for branch (4.20.z)
bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
release note text is set and does not match the template
dependent bug Jira Issue OCPBUGS-62210 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-62210 targets the "4.21.0" version, which is one of the valid target versions: 4.21.0
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (mbasim@redhat.com), skipping review request.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

moebasim · 2025-11-12T12:55:39Z

/verified by mbasim@redhat.com

openshift-ci-robot · 2025-11-12T12:55:50Z

@moebasim: Jira verification commands are restricted to collaborators for this repo.

Details

In response to this:

/verified by mbasim@redhat.com

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

moebasim · 2025-11-12T13:08:01Z

/verified by @moebasim

openshift-ci-robot · 2025-11-12T13:08:11Z

@moebasim: Jira verification commands are restricted to collaborators for this repo.

Details

In response to this:

/verified by @moebasim

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

kunalmemane · 2025-11-12T13:10:06Z

/verified by @kunalmemane

openshift-ci-robot · 2025-11-12T13:10:19Z

@kunalmemane: This PR has been marked as verified by @kunalmemane.

Details

In response to this:

/verified by @kunalmemane

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

moebasim · 2025-11-12T13:19:34Z

/verified by @moebasim

openshift-ci-robot · 2025-11-12T13:19:46Z

@moebasim: Jira verification commands are restricted to collaborators for this repo.

Details

In response to this:

/verified by @moebasim

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

prabhapa · 2025-11-14T11:41:39Z

/lgtm

prabhapa · 2025-11-14T11:42:00Z

/label backport-risk-assessed

openshift-ci · 2025-11-14T11:42:03Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, prabhapa

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

~~OWNERS~~ [prabhapa]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

openshift-ci-robot · 2025-11-14T11:47:14Z

@openshift-cherrypick-robot: Jira Issue Verification Checks: Jira Issue OCPBUGS-64857
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-64857 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

This is an automated cherry-pick of #469

/assign kunalmemane

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

kunalmemane · 2025-11-14T12:21:26Z

/cherrypick release-4.19 release-4.18 release-4.17 release-4.16 release-4.15 release-4.14

openshift-cherrypick-robot · 2025-11-14T12:22:16Z

@kunalmemane: new pull request created: #485

Details

In response to this:

/cherrypick release-4.19 release-4.18 release-4.17 release-4.16 release-4.15 release-4.14

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

openshift-merge-robot · 2025-11-16T02:32:55Z

Fix included in accepted release 4.20.0-0.nightly-2025-11-15-175712

pkg/build/builder/util/dockerfile.Write: reproduce heredocs

2aae31b

When writing out the contents of a parsed Dockerfile, attempt to reproduce heredocs that followed instructions. Signed-off-by: Nalin Dahyabhai <nalin@redhat.com>

openshift-cherrypick-robot assigned kunalmemane Nov 10, 2025

openshift-cherrypick-robot mentioned this pull request Nov 10, 2025

OCPBUGS-62210: BuildConfig inline Dockerfile fails with heredoc syntax #469

Merged

openshift-ci Bot changed the title ~~[release-4.20] OCPBUGS-62210: BuildConfig inline Dockerfile fails with heredoc syntax~~ [release-4.20] OCPBUGS-64857: BuildConfig inline Dockerfile fails with heredoc syntax Nov 10, 2025

openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Nov 10, 2025

openshift-ci Bot requested review from divyansh42 and sayan-biswas November 10, 2025 14:46

openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Nov 12, 2025

openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Nov 12, 2025

openshift-ci Bot assigned prabhapa Nov 14, 2025

openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Nov 14, 2025

openshift-ci Bot added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Nov 14, 2025

openshift-merge-bot Bot merged commit 8c0a564 into openshift:release-4.20 Nov 14, 2025
9 of 11 checks passed

openshift-cherrypick-robot mentioned this pull request Nov 14, 2025

[release-4.19] OCPBUGS-65624: BuildConfig inline Dockerfile fails with heredoc syntax #485

Merged

Conversation

openshift-cherrypick-robot commented Nov 10, 2025

Uh oh!

openshift-ci-robot commented Nov 10, 2025

Uh oh!

openshift-ci-robot commented Nov 10, 2025

Uh oh!

openshift-ci Bot commented Nov 10, 2025

Uh oh!

moebasim commented Nov 12, 2025

Uh oh!

openshift-ci-robot commented Nov 12, 2025

Uh oh!

moebasim commented Nov 12, 2025

Uh oh!

openshift-ci-robot commented Nov 12, 2025

Uh oh!

moebasim commented Nov 12, 2025

Uh oh!

openshift-ci-robot commented Nov 12, 2025

Uh oh!

moebasim commented Nov 12, 2025

Uh oh!

openshift-ci-robot commented Nov 12, 2025

Uh oh!

moebasim commented Nov 12, 2025

Uh oh!

openshift-ci-robot commented Nov 12, 2025

Uh oh!

moebasim commented Nov 12, 2025

Uh oh!

openshift-ci-robot commented Nov 12, 2025

Uh oh!

kunalmemane commented Nov 12, 2025

Uh oh!

openshift-ci-robot commented Nov 12, 2025

Uh oh!

moebasim commented Nov 12, 2025

Uh oh!

openshift-ci-robot commented Nov 12, 2025

Uh oh!

prabhapa commented Nov 14, 2025

Uh oh!

prabhapa commented Nov 14, 2025

Uh oh!

openshift-ci Bot commented Nov 14, 2025

Uh oh!

Uh oh!

openshift-ci-robot commented Nov 14, 2025

Uh oh!

kunalmemane commented Nov 14, 2025

Uh oh!

openshift-cherrypick-robot commented Nov 14, 2025

Uh oh!

openshift-merge-robot commented Nov 16, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

7 participants