Skip to content
This repository has been archived by the owner on Jun 19, 2022. It is now read-only.

Set up upgrade tests for knative-gcp #1664

Closed
nlopezgi opened this issue Sep 2, 2020 · 1 comment · Fixed by #1854
Closed

Set up upgrade tests for knative-gcp #1664

nlopezgi opened this issue Sep 2, 2020 · 1 comment · Fixed by #1854
Assignees
Labels
area/test-and-release Test infrastructure, tests or release kind/feature-request New feature or request priority/1 Blocks current release defined by release/* label or blocks current milestone release/2
Milestone

Comments

@nlopezgi
Copy link
Contributor

nlopezgi commented Sep 2, 2020

Problem
Currently the knative/eventing repo runs as part of their CI, upgrade tests.
Knative-gcp repo, however, does not have such tests.

Persona:

developer

Exit Criteria
Upgrade tests are setup for relevant resources defined in this repo.

Time Estimate (optional):
~2w

Additional context (optional)
The upgrade tests should be similar to the ones in knative/eventing repo. They should re-use as much as possible the existing scripts.

The upgrade tests should also have a setup similar to existing ones in the knative-gcp repo (e.g., e2e-tests). Specifically as related to how versions of knative/eventing are obtained.

Other useful pointers:
Recent PR enabling some upgrade tests: knative/eventing#3927
Older PRs adding upgrade tests: knative/eventing#3262, knative/eventing#3110

@nlopezgi nlopezgi added the kind/feature-request New feature or request label Sep 2, 2020
@grantr grantr added priority/1 Blocks current release defined by release/* label or blocks current milestone release/2 area/test-and-release Test infrastructure, tests or release labels Sep 14, 2020
@grantr grantr added this to the Backlog milestone Sep 14, 2020
@zhongduo
Copy link
Contributor

zhongduo commented Oct 7, 2020

/assign @zhongduo

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/test-and-release Test infrastructure, tests or release kind/feature-request New feature or request priority/1 Blocks current release defined by release/* label or blocks current milestone release/2
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants