Create a Task that can create a Tekton Pipelines cluster to test against

[bobcatfish]

Expected Behavior

We should be testing and releasing Pipelines with Pipelines.

We should have a Task (and related Resources) defined that we can use to:

• Create a cluster to test against (currently done using boskos and triggered by e2e-tests.sh)
• Deploy Pipelines to the cluster

The Task

• Inputs:
  • git repo
  • cluster (to deploy Pipelines to and run end to end tests) (or is this an output?)
• Outputs:
  • cluster

Actual Behavior

We currently use prow and e2e-tests.sh, which also uses boskos to control clusters to test against.

Additional Info

• If possible let's try to keep using the boskos cluster we were already using
• Actually triggering this is not in scope for this issue, it's fine to test manually (we'll be linking these together in a later issue)

[afrittoli]

I would like to help, but I'll have to learn a bit more about prow to boskos and prow to tekton interaction first 😇.

AFAIK Boskos does more than creating the test cluster. It does the cleanup as well, as well as garbage collection of orphaned resources.

I wonder if we really need to re-implement Boskos in Tekton, or if we could start using a ClusterResource as an input to the test Pipeline.

[vdemeester]

/kind enhancement
/area test-infra

[afrittoli]

I wonder if we could do this in go (instead of Task) and wrap it in an interceptor, so that the body of the trigger request is enriched with the data to setup the cluster resource in the trigger template. Just an idea

[tekton-robot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tekton-robot]

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

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/test-infra repository.

[bobcatfish]

We do have some of this work in progress for our catalog testing:

• boskos-acquire
• boskos-release
• gke-cluster-create

More details in tektoncd/catalog#373