search

kubernetes-retired / service-catalog

Consume services in Kubernetes using the Open Service Broker API
https://svc-cat.io
Apache License 2.0
1.05k stars 385 forks source link

Make e2e run on prow (was: jenkins stuck for a week - who has perms?) #2184

Closed MHBauer closed 5 years ago

MHBauer commented 6 years ago

Jenkins seems stuck processing https://github.com/kubernetes-incubator/service-catalog/pull/2177#issuecomment-403530453 for the last week. No newer PRs have been handled.

https://service-catalog-jenkins.appspot.com/job/service-catalog-master-testing/

Is @kibbles-n-bytes the only person with permissions? Is the only solution here moving towards prow?

carolynvs commented 6 years ago

Closing - We don't use jenkins anymore.

MHBauer commented 6 years ago

This means there are no e2e tests running. No testing with a kubernetes deployment is being done in an automated fashion.

carolynvs commented 6 years ago

Thanks for clarifying. Do you happen to know if they were explicitly turned off or if I should be investigating when they stopped running and why?

MHBauer commented 6 years ago

Only run by jenkins and not yet running in prow. Never made the transition.

carolynvs commented 6 years ago

I don't think that Jenkins server exists anymore... 🤦‍♀️ I'll put this on Monday's SIG agenda.

MHBauer commented 6 years ago

maybe a new issue for @jeremyrickard ?

MHBauer commented 5 years ago

AI for a Campbell in October 1, 2018 sig meeting? I haven't watched it.

fejta-bot commented 5 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale

fejta-bot commented 5 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten

MHBauer commented 5 years ago

@jberkhahn

I think this is better served by having a discussion in the weekly meeting about whether anybody still cares about running these tests at all, and opening a new issue without the baggage this one has.

/close

On 8/6/19 9:29 AM, fejta-bot wrote:

Stale issues rot after 30d of inactivity. Mark the issue as fresh with |/remove-lifecycle rotten|. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with |/close|.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_fejta&d=DwMCaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=gSVznMk4DixLVQ8USuNSH0RuT_4psswDPWAf-45M48c&m=zM3j1dPpuq5E0WkZWiRhhMxEVIz4y2wJ8gYsnxRHXT8&s=ISDAh1FCYRistebjX_gYboildPOU4pF9JLD0o8-oF6E&e=. /lifecycle rotten

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_kubernetes-2Dsigs_service-2Dcatalog_issues_2184-3Femail-5Fsource-3Dnotifications-26email-5Ftoken-3DADFYGAPGQO4BDUOVQAZ5GL3QDGRFPA5CNFSM4FJAKXGKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3VWVAY-23issuecomment-2D518744707&d=DwMCaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=gSVznMk4DixLVQ8USuNSH0RuT_4psswDPWAf-45M48c&m=zM3j1dPpuq5E0WkZWiRhhMxEVIz4y2wJ8gYsnxRHXT8&s=shy1ebUmE0bHeLd6SMHAb1ydWTce2A9ohTBTBk6-MyM&e=, or mute the thread https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_ADFYGAKXPXZJ7YVYIYSE233QDGRFPANCNFSM4FJAKXGA&d=DwMCaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=gSVznMk4DixLVQ8USuNSH0RuT_4psswDPWAf-45M48c&m=zM3j1dPpuq5E0WkZWiRhhMxEVIz4y2wJ8gYsnxRHXT8&s=nbk3SyRC-gb3gNYHnIzDOKGqyVSwQ14hJCYnS3bOgMU&e=.

k8s-ci-robot commented 5 years ago

@MHBauer: Closing this issue.

In response to [this](https://github.com/kubernetes-sigs/service-catalog/issues/2184#issuecomment-518750676): >@jberkhahn > >I think this is better served by having a discussion in the weekly >meeting about whether anybody still cares about running these tests at >all, and opening a new issue without the baggage this one has. > >/close > >On 8/6/19 9:29 AM, fejta-bot wrote: >> >> Stale issues rot after 30d of inactivity. >> Mark the issue as fresh with |/remove-lifecycle rotten|. >> Rotten issues close after an additional 30d of inactivity. >> >> If this issue is safe to close now please do so with |/close|. >> >> Send feedback to sig-testing, kubernetes/test-infra and/or fejta >> . >> /lifecycle rotten >> >> — >> You are receiving this because you authored the thread. >> Reply to this email directly, view it on GitHub >> , >> or mute the thread >> . >> > > Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.