Bump Tekton Release to v0.25.0

[qu1queee]

Changes

Bump to latest stable Tekton Release.

The v0.24 have 3 patches, I only found one breaking change, as follows:

• Related to https://github.com/tektoncd/pipeline/pull/3878, we are not affected on the removal of a HOME env var with /tekton/home value, neither the removal of default workingDir with /workspace value. I modified our strategies where the ENV var was needed.

Regarding v0.25.0, I didnt find any significant change for SHP.

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

Bump Tekton to v0.25.0 release

[SaschaSchwarze0]

fyi @qu1queee v0.25.0 got released today. Don't see anything in its release notes that would block us from directly going there.

[imjasonh]

Do we also want to bump https://github.com/shipwright-io/build/blob/main/Makefile#L36 ?

This makes me think we might want to automate this so we don't forget other places this version is specified. 🤔

[qu1queee]

Yes, this PR will include all related changes. The automation is nice, but as we have hard dependencies to Tekton, I like to review manually the upcoming changes when working on the bump. I will add this topic to #812 for now.

[SaschaSchwarze0]

Adding hold as we might want to do this after v0.5.1 while we are not prepared to build a release from a non-main branch? Also omitting risk by claiming support for a very fresh Tekton version. But open to get it into v0.5.1. Just think we should agree on that before we merge.

fyi @HeavyWombat the env var override in our buildkit experiments that we manually had to do to revert the Tekton override is then becoming obsolete.

/approve
/hold

[qu1queee]

@SaschaSchwarze0

Adding hold as we might want to do this after v0.5.1 while we are not prepared to build a release from a non-main branch? Also omitting risk by claiming support for a very fresh Tekton version. But open to get it into v0.5.1. Just think we should agree on that before we merge.

it does make sense, lets merge after.

[qu1queee]

@SaschaSchwarze0 this one should be now ready to get in, fyi

[SaschaSchwarze0]

Hi @qu1queee, I tested this in my local cluster where Tekton is at v0.25 as well and I get BuildKit only working by also setting the HOME environment variable explicitely to /tekton/home as you do for the other build strategies. I also guess that we must set the environment variable here: runtime_image.go#L198-L202, I know the feature is deprecated, but it is still there.

[qu1queee]

@SaschaSchwarze0 correct, buildkit didnt worked for me either. Done.

[SaschaSchwarze0]

/approve
/lgtm

[openshift-ci]

[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:

• OWNERS [SaschaSchwarze0]

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