-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: No longer push to Docker Hub on release #2562
Conversation
No longer push to Docker Hub on release as per kedacore/governance#16 Signed-off-by: Tom Kerkhove <kerkhove.tom@gmail.com>
No longer push to Docker Hub on release as per kedacore/governance#16 Signed-off-by: Tom Kerkhove <kerkhove.tom@gmail.com>
No longer push to Docker Hub on release as per kedacore/governance#16 Signed-off-by: Tom Kerkhove <kerkhove.tom@gmail.com>
No longer push to Docker Hub on release as per kedacore/governance#16 Signed-off-by: Tom Kerkhove <kerkhove.tom@gmail.com>
/run-e2e * Update: You can check the progres here |
@JorTurFer How do I run all e2e tests again? |
They are already running @tomkerkhove. You can trigger them again posting the command again, but you should wait till current execution ends (because it finishes or you cancel it) |
/run-e2e * |
@JorTurFer All jobs are successful in the e2e run but it reports failure. Do you know why? Is it related to the run duration? |
On June 21, 2021, GitHub Container Registry became generally available which means that we will no longer push to Docker Hub on release as per kedacore/governance#16 and our announcement in March 2021.
Checklist
Fixes kedacore/governance#16