TEP-0114: Custom Tasks Beta - Support v1beta1.CustomRun

[jerop]

In TEP-0114: Custom Tasks Beta, we proposed migrating Custom Tasks and Runs to beta.

Moving v1alpha1.Run to v1beta1.CustomRun is a required API change in TEP-0114: Custom Tasks Beta. This issue tracks this API change.

[vsinghai]

/assign

[XinruZhang]

Putting a note here as a reminder: all the references about v1alpha1.Run should be migrated to v1beta1.CustomRun, for example:

pipeline/pkg/apis/pipeline/v1alpha1/run_types.go

Lines 101 to 107 in f1b6812

	const (
	// RunCancelledByPipelineMsg indicates that the PipelineRun of which part this Run was
	// has been cancelled.
	RunCancelledByPipelineMsg RunSpecStatusMessage = "Run cancelled as the PipelineRun it belongs to has been cancelled."
	// RunCancelledByPipelineTimeoutMsg indicates that the Run was cancelled because the PipelineRun running it timed out.
	RunCancelledByPipelineTimeoutMsg RunSpecStatusMessage = "Run cancelled as the PipelineRun it belongs to has timed out."
	)

Thanks for @lbernick 's input!

[pritidesai]

Pipeline WG - Blockers:

• What should go in RunSpec?
• How to support v1alpha1 Run along with v1beta1 CustomRun?

/cc @ScrapCodes

[vdemeester]

On the second question, I would ask a question to the question : do we even want to support both ? v1alpha1.Run is alpha, we can pretty much do whatever. As already mentionned during a WG, if we give a timeline when tektoncd/pipeline will start creating v1beta1.CustomRun instead of v1alpha1.Run, announce it, it should give enough time for current CustomTask project to update to handle v1beta1.CustomRun (in addition to v1alpha1.Run or not — but that's on those project, not tektoncd/pipeline to support both APIs, or not).

[jerop]

This was completed and released in v0.42.0