-
Notifications
You must be signed in to change notification settings - Fork 102
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
Sunset prow #767
Comments
@justinbarrick @jbarrick-mesosphere could you please help us to figure out how to do this? |
As I'm no longer on the DevProd team, your best contact would be @orsenthil or @cgawron1. |
@alenkacz - I could help you with this here. |
@orsenthil thanks! You could either give us guidance in how to do it (disable it in all kudo repos etc.) or you could do it for us if you have time. Any of that works for me :) |
@orsenthil ping |
We may have to use the API to clear the checks by hand. :thinking_face:
…On Tue, Sep 17, 2019 at 9:01 AM Alena Varkockova ***@***.***> wrote:
@orsenthil <https://github.com/orsenthil> ping
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#767?email_source=notifications&email_token=AACZIW6HH2GLHD7NCLHMVMTQKDIJ3A5CNFSM4IU4I3XKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD64ODEY#issuecomment-532210067>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AACZIW6MQ4X2VK7XSS6JZFDQKDIJ3ANCNFSM4IU4I3XA>
.
|
@alenkacz - Let's start with disabling the payload delivery to prow. I will bring down the prow instance. I wanted to talk to you bit to understand the reasoning behind this decision and see if there is any need that we could address. But it is okay start with disabling the payload send from the GH settings. I don't have access to the GitHub settings, any org member should do that. |
@orsenthil I already disabled the webhook over the weekend so there should be no payload also prow is no longer running anything on our PRs... |
Done pending followup with @orsenthil |
Before deleting, @alenkacz and I had scaled the cluster down
And now it is deleted.
|
What would you like to be added:
It's not currently bringing any value and we decided not to push it forward. Remove it from out build statuses and PRs.
Why is this needed:
** Steps **
[ ] Delete Prow GKE Cluster
[ ] Remove it from Github Worklow
[ ] Use Github approvals/etc
The text was updated successfully, but these errors were encountered: