yuzhipeng

I find that the e2e-tests-upgrade.sh script is referenced here as a cron job but I don't find the related running job in tektoncd/pipeline github actions. https://github.com/tektoncd/plumbing/blob/c5b0f73a1b5e2ca0025d21ac9b7d69a3f7843506/prow/config.yaml#L1829 Could you help show...

> Looking at our [prow dashboard](https://prow.tekton.dev/?type=periodic&job=ci-tekton-pipeline-upgrade-tests), upgrade tests have been failing with `fatal: destination path '/home/prow/go/src/github.com/google/licenseclassifier' already exists and is not an empty directory.` I'm guessing they've been broken for...

Hi, @lbernick @afrittoli looks like there will be a large change for the e2e upgrade test. I am interested in e2e upgrade test. Is there anything I can do to...

> > I am sorry I don't understand what moving them to Tekton means. Is it something like dogfooding? Another CI system based on Tekton? > > What I meant...

I find that Prow job will run the command `/usr/local/bin/entrypoint.sh` first Then I pull the image to find out if the files `/home/prow/go/src/github.com/google/licenseclassifier` exist. Looks like we do not need...

I made a change in https://github.com/tektoncd/plumbing/pull/1175 and maybe it can resolve the problem when running the e2e-upgrade-test.sh.

+1