Automate upgrade testing #349
Labels
enhancement
New feature or request
Milestone
Comments
kuritka
added a commit
that referenced
this issue
Apr 7, 2021
Permutation workflow is executed per each push - deploy recent k8gb version to k3d cluster - build docker from branch - helm install created docker to k3d cluster - run terratests I had to add new targets to MAkefile and because of code repetition I made necessary refactoring related to #349
kuritka
added a commit
that referenced
this issue
Apr 7, 2021
Permutation workflow is executed per each push - deploy recent k8gb version to k3d cluster - build docker from branch - helm install created docker to k3d cluster - run terratests I had to add new targets to MAkefile and because of code repetition I made necessary refactoring related to #349
kuritka
added a commit
that referenced
this issue
Apr 7, 2021
Permutation workflow is executed per each push - deploy recent k8gb version to k3d cluster - build docker from branch - helm install created docker to k3d cluster - run terratests I had to add new targets to MAkefile and because of code repetition I made necessary refactoring related to #349
kuritka
added a commit
that referenced
this issue
Apr 7, 2021
Permutation workflow is executed per each push - deploy recent k8gb version to k3d cluster - build docker from branch - helm install created docker to k3d cluster - run terratests I had to add new targets to MAkefile and because of code repetition I made necessary refactoring related to #349
kuritka
added a commit
that referenced
this issue
Apr 7, 2021
Permutation workflow is executed per each push - deploy recent k8gb version to k3d cluster - build docker from branch - helm install created docker to k3d cluster - run terratests I had to add new targets to MAkefile and because of code repetition I made necessary refactoring related to #349
kuritka
added a commit
that referenced
this issue
Apr 7, 2021
Permutation workflow is executed per each push - deploy recent k8gb version to k3d cluster - build docker from branch - helm install created docker to k3d cluster - run terratests I had to add new targets to MAkefile and because of code repetition I made necessary refactoring related to #349
Merged
kuritka
added a commit
that referenced
this issue
Apr 7, 2021
Permutation workflow is executed per each push - deploy recent k8gb version to k3d cluster - build docker from branch - helm install created docker to k3d cluster - run terratests I had to add new targets to MAkefile and because of code repetition I made necessary refactoring related to #349
kuritka
added a commit
that referenced
this issue
Apr 7, 2021
Permutation workflow is executed per each push - deploy recent k8gb version to k3d cluster - build docker from branch - helm install created docker to k3d cluster - run terratests I had to add new targets to MAkefile and because of code repetition I made necessary refactoring related to #349
kuritka
added a commit
that referenced
this issue
Apr 7, 2021
Permutation workflow is executed per each push - deploy recent k8gb version to k3d cluster - build docker from branch - helm install created docker to k3d cluster - run terratests I had to add new targets to MAkefile and because of code repetition I made necessary refactoring related to #349
kuritka
added a commit
that referenced
this issue
Apr 7, 2021
Upgrade testing workflow is executed per each push - deploy recent k8gb version to k3d cluster - build docker from branch - helm install created docker to k3d cluster - run terratests I had to add new targets to MAkefile and because of code repetition I made necessary refactoring related to #349
kuritka
added a commit
that referenced
this issue
Apr 7, 2021
Upgrade testing workflow is executed per each push - deploy recent k8gb version to k3d cluster - build docker from branch - helm install created docker to k3d cluster - run terratests I had to add new targets to MAkefile and because of code repetition I made necessary refactoring related to #349
kuritka
added a commit
that referenced
this issue
Apr 7, 2021
Upgrade testing workflow is executed per each push - deploy recent k8gb version to k3d cluster - build docker from branch - helm install created docker to k3d cluster - run terratests I had to add new targets to MAkefile and because of code repetition I made necessary refactoring related to #349
kuritka
added a commit
that referenced
this issue
Apr 8, 2021
Upgrade testing workflow is executed per each push - deploy recent k8gb version to k3d cluster - build docker from branch - helm install created docker to k3d cluster - run terratests I had to add new targets to MAkefile and because of code repetition I made necessary refactoring related to #349
kuritka
added a commit
that referenced
this issue
Apr 8, 2021
Upgrade testing workflow is executed per each push - deploy recent k8gb version to k3d cluster - build docker from branch - helm install created docker to k3d cluster - run terratests I had to add new targets to MAkefile and because of code repetition I made necessary refactoring related to #349
kuritka
added a commit
that referenced
this issue
Apr 8, 2021
Upgrade testing workflow is executed per each push - deploy recent k8gb version to k3d cluster - build docker from branch - helm install created docker to k3d cluster - run terratests I had to add new targets to MAkefile and because of code repetition I made necessary refactoring related to #349
kuritka
added a commit
that referenced
this issue
Apr 8, 2021
Upgrade testing workflow is executed per each push - deploy recent k8gb version to k3d cluster - build docker from branch - helm install created docker to k3d cluster - run terratests I had to add new targets to MAkefile and because of code repetition I made necessary refactoring related to #349
kuritka
added a commit
that referenced
this issue
Apr 8, 2021
Upgrade testing workflow is executed per each push - deploy recent k8gb version to k3d cluster - build docker from branch - helm install created docker to k3d cluster - run terratests I had to add new targets to MAkefile and because of code repetition I made necessary refactoring related to #349
kuritka
added a commit
that referenced
this issue
Apr 9, 2021
Upgrade testing workflow is executed per each push - deploy recent k8gb version to k3d cluster - build docker from branch - helm install created docker to k3d cluster - run terratests I had to add new targets to MAkefile and because of code repetition I made necessary refactoring related to #349
kuritka
added a commit
that referenced
this issue
Apr 9, 2021
Upgrade testing workflow is executed per each push - deploy recent k8gb version to k3d cluster - build docker from branch - helm install created docker to k3d cluster - run terratests I had to add new targets to MAkefile and because of code repetition I made necessary refactoring related to #349 Signed-off-by: kuritka <[email protected]>
kuritka
added a commit
that referenced
this issue
Apr 9, 2021
Upgrade testing workflow is executed per each push - deploy recent k8gb version to k3d cluster - build docker from branch - helm install created docker to k3d cluster - run terratests I had to add new targets to MAkefile and because of code repetition I made necessary refactoring related to #349 Signed-off-by: kuritka <[email protected]>
kuritka
added a commit
that referenced
this issue
Apr 9, 2021
We execute upgrade testing workflow per each push - deploy recent k8gb version to k3d cluster - build docker from branch - helm install created docker to k3d cluster - run terratests I had to add new targets to MAkefile and because of code repetition I made necessary refactoring related to #349 Signed-off-by: kuritka <[email protected]>
This was
linked to
pull requests
Apr 9, 2021
Merged
|
@kuritka @somaritane @k0da I guess we can close this one or do you envision more work in this area in foreseeable future? |
@ytsarev yep, I think we can close this one, the scope is pretty much fulfilled by #429 and #435. Just one thing, as I mentioned earlier, "Permutation" and "permutation testing" are quite a broad terms, let's rename the issue with "Automate upgrade testing" in order to avoid confusions. |
|
@somaritane I was just trying to sound smart :D Closing this one |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To avoid regressions connected with the upgrade procedure we need to automatically test upgrade from current to future release before stabilizing the new version.
The text was updated successfully, but these errors were encountered: