Create 'next' releases on NPM & Dockerhub to use with Canary flow #2366
Assignees
Labels
T-testing
Type: Testing. More tests need to be added.
Comments
spypsy
added a commit
that referenced
this issue
Oct 13, 2023
Fixes #2366 # Checklist: Remove the checklist to signal you've completed it. Enable auto-merge if the PR is ready to merge. - [ ] If the pull request requires a cryptography review (e.g. cryptographic algorithm implementations) I have added the 'crypto' tag. - [ ] I have reviewed my diff in github, line by line and removed unexpected formatting changes, testing logs, or commented-out code. - [ ] Every change is related to the PR description. - [ ] I have [linked](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue) this pull request to relevant issues (if any exist).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We currently deploy to production (NPM & Dockerhub) after e2e flow has finished and once the deployment is finished, we run a set of 'canary' tests on deployed artifacts.
This is an issue as we're only catching some errors after the deployments have been made available to the public. Instead we should:
run e2e -> Deploy artifacts under
nextversion -> Pullnextversion to run canary tests -> once canary test suite is successful, deploylatestversioned artifactsThe text was updated successfully, but these errors were encountered: