Add automation for all tektoncd repos

[bobcatfish]

Expected Behavior

All of the repos in tektoncd should have a minimum of prow automation applied.

We should have tide automation for:

• plumbing
• dashboard
• cli
• experimental (OWNERS files in each subdir)
• website
• catalog

We should add unit test support for:

• dashboard (Initial pre-submit script… dashboard#72)
• experimental (in each subdir?) : Add a CI on tektoncd/experimental… #37 and enable presubmit tests on experimental repository experimental#60
• catalog
• cli (Initial pre-submit script… cli#14) – a bit more than unit tests

Unit test support is going to be interesting, the easiest way to add this initially is probably to copy-paste the prow jobs as is and add exactly the script the knative-tests image expects:

plumbing/prow/config.yaml

Lines 107 to 108 in 2ff5265

	- "./test/presubmit-tests.sh"
	- "--unit-tests"

OR we could be adventurous and try using our own script.

OR be very adventurous and try our own image.

Actual Behavior

Pipelines has all the bells and whistles, the rest of the projects seem to have only a random smattering (e.g. community has tide merging, but this repo doesn't).

Additional Info

• Each project may decide to add additional automation (e.g. integration tests, coverage) which is totally cool, hopefully setting up a minimum should give them a starting point.
• The work to do here is basically copy paste in the prow config to copy the unit-test section from pipelines and duplicate it for the other repos.

[bobcatfish]

I also had to add branch protection rules to all the repos to make sure the tide check was required. Will need to back and add a requirement about the tide clause to repos that didn't have any open PRs:

• experimental
• website
• cli

[vdemeester]

/assign

[vdemeester]

@bobcatfish updated the requirements for tide (dashboard, cli and experimental) and builds checks for dashboard and cli. (website needs at least a PR before we can see the check 😅 )

For experimental, I was wondering how should be do that 🤔 each time a folder is created, we create a configuration here ? 🤔

[vdemeester]

Also, the merging options are all the same (as tektoncd/pipeline).

[bobcatfish]

For experimental, I was wondering how should be do that 🤔 each time a folder is created, we create a configuration here ? 🤔

A couple ideas:

• Have a top level script that looks for scripts in all subdirs
• Have a different prowjob for each folder (probably a bad idea)

Another issue is that when code in a dir changes, we probably want to only run the tests for that dir - but we can always deal with this iteratively XD

[vdemeester]

Once #37 is in, I think we can close this one 👼 🎉
Automation of tektoncd/plumbing itself is tracked by #1

[vdemeester]

#37 is merged 💃
/close

[tekton-robot]

@vdemeester: Closing this issue.

In response to this:

#37 is merged 💃
/close

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]

Thanks @vdemeester !!!! ❤️ ❤️ ❤️