Skip to content
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.

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

Fix Heruko buildpacks samples that failed to determine the target OS #1511

Merged
merged 1 commit into from
Feb 29, 2024

Conversation

HeavyWombat
Copy link
Contributor

Changes

Add CNB_TARGET_OS and CNB_TARGET_ARCH to fix error during the detect phase, where the target system cannot be detected:

[Error: Internal Buildpack Error]
Couldn't determine target os: environment variable not found
err:  heroku/[email protected] (1)
======== Output: heroku/[email protected] ========

There seems to be a changed behavior that was introduced in the common buildpacks library that is in use that expects these environment variables to be present to detect the target system OS and architecture.

Ref: heroku/buildpacks-procfile#214
Ref: heroku/libcnb.rs@033f612

Submitter Checklist

  • Includes tests if functionality changed/was added
  • Includes docs if changes are user-facing
  • Set a kind label on this PR
  • Release notes block has been filled in, or marked NONE

See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.

Release Notes

NONE

@HeavyWombat HeavyWombat added the kind/bug Categorizes issue or PR as related to a bug. label Feb 29, 2024
@pull-request-size pull-request-size bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Feb 29, 2024
@openshift-ci openshift-ci bot added the release-note-none Label for when a PR does not need a release note label Feb 29, 2024
Ref: heroku/buildpacks-procfile#214
Ref: heroku/libcnb.rs@033f612

Add `CNB_TARGET_OS` and `CNB_TARGET_ARCH` to fix error during the detect
phase, where the target system cannot be detected:
```
[Error: Internal Buildpack Error]
Couldn't determine target os: environment variable not found
err:  heroku/[email protected] (1)
======== Output: heroku/[email protected] ========
```

There seems to be a changed behavior that was introduced in the common
buildpacks library that is in use that expects these environment
variables to be present to detect the target system OS and architecture.

Signed-off-by: Matthias Diester <[email protected]>
@HeavyWombat HeavyWombat force-pushed the tweak/heruko-buildpacks-samples branch from 1beb274 to c2d4725 Compare February 29, 2024 15:33
@SaschaSchwarze0 SaschaSchwarze0 added this to the release-v0.13.0 milestone Feb 29, 2024
Copy link
Member

@SaschaSchwarze0 SaschaSchwarze0 left a comment

Choose a reason for hiding this comment

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

/approve
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 29, 2024
Copy link
Contributor

openshift-ci bot commented Feb 29, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: SaschaSchwarze0

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

The pull request process is described here

Needs approval from an approver in each of these files:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 29, 2024
@SaschaSchwarze0 SaschaSchwarze0 added kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. and removed kind/bug Categorizes issue or PR as related to a bug. labels Feb 29, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit d084af1 into main Feb 29, 2024
14 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the tweak/heruko-buildpacks-samples branch February 29, 2024 16:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. lgtm Indicates that a PR is ready to be merged. release-note-none Label for when a PR does not need a release note size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants