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: on cluster build - workaround for Tekton issue with empty array #1214

Merged
merged 1 commit into from
Sep 7, 2022

Conversation

zroubalik
Copy link
Contributor

@zroubalik zroubalik commented Sep 5, 2022

Signed-off-by: Zbynek Roubalik [email protected]

Need to hack empty BuildEnvs array on Tekton v0.39.0+ untill tektoncd/pipeline#5149 is resolved and released.

Withouth this change on-cluster-builds fail on Tekton v0.39.0+ if there is not any Build Env specifed.

Changes

  • 🐛 on cluster build - workaround for Tekton issue with empty array

/kind bug

@knative-prow knative-prow bot added kind/bug Categorizes issue or PR as related to a bug. approved Indicates a PR has been approved by an approver from all required OWNERS files. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Sep 5, 2022
@codecov
Copy link

codecov bot commented Sep 5, 2022

Codecov Report

Merging #1214 (be9d4a7) into main (4301ca2) will decrease coverage by 0.05%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main    #1214      +/-   ##
==========================================
- Coverage   45.42%   45.36%   -0.06%     
==========================================
  Files          68       68              
  Lines        9718     9723       +5     
==========================================
- Hits         4414     4411       -3     
- Misses       4912     4919       +7     
- Partials      392      393       +1     
Impacted Files Coverage Δ
pipelines/tekton/resources.go 38.34% <0.00%> (-1.02%) ⬇️
s2i/builder.go 61.04% <0.00%> (-1.21%) ⬇️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@zroubalik zroubalik force-pushed the ocbEnvFix branch 2 times, most recently from 4609b7c to 71a8d65 Compare September 5, 2022 11:35
Copy link
Contributor

@jrangelramos jrangelramos left a comment

Choose a reason for hiding this comment

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

just one minor nit. besides that it looks ok to me

pipelines/tekton/resources.go Outdated Show resolved Hide resolved
@zroubalik zroubalik closed this Sep 5, 2022
@knative-prow knative-prow bot removed the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 5, 2022
@zroubalik zroubalik reopened this Sep 5, 2022
@knative-prow knative-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 5, 2022
@zroubalik
Copy link
Contributor Author

e2e test fails because of issue fixed in #1213

Copy link
Member

@lkingland lkingland left a comment

Choose a reason for hiding this comment

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

/lgtm
Assuming the E2Es pass of course

@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label Sep 6, 2022
@knative-prow
Copy link

knative-prow bot commented Sep 6, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lkingland, zroubalik

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:
  • OWNERS [lkingland,zroubalik]

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

@knative-prow knative-prow bot removed the lgtm Indicates that a PR is ready to be merged. label Sep 7, 2022
@zroubalik
Copy link
Contributor Author

@lkingland could you please LGTM again, I rebased this and e2e tests are passing.

@lance
Copy link
Member

lance commented Sep 7, 2022

/lgtm

@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label Sep 7, 2022
@knative-prow knative-prow bot merged commit 2ee2c61 into knative:main Sep 7, 2022
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/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants