kubernetes-sigs / hydrophone

Hydrophone is a lightweight Kubernetes conformance tests runner
Apache License 2.0
65 stars 30 forks source link

Add a brew repo #142

Closed cprivitere closed 2 weeks ago

cprivitere commented 7 months ago

Hey all, would like to start using this instead of sonobuoy, however you don't have a brew package yet. Would love to see that get added.

dims commented 7 months ago

@cprivitere no we don't yet. would you have cycles to help with that? (would be awesome!!)

reetasingh commented 7 months ago

@dims @cprivitere @rjsadow I am interested in working on this . I can assign this issue to myself if @cprivitere is fine with that

cprivitere commented 7 months ago

I sure don't mind. I don't really have the cycles at the moment.

reetasingh commented 7 months ago

PR opened https://github.com/Homebrew/homebrew-core/pull/162309

reetasingh commented 7 months ago

@cprivitere @dims @rjsadow looks like we need more adoption for hydrophone to make it available on homebrew , see comment https://github.com/Homebrew/homebrew-core/pull/162309#issuecomment-1937488462

dims commented 7 months ago

@reetasingh no worries. if enough folks chime in here or there (or we get some data on downloads) then we can ask them to revisit. thanks for trying!

dims commented 7 months ago

(ya, no need for that personal tap thing now)

cprivitere commented 6 months ago

When they say personal tap they just mean "not managed by the brew maintainers". This is what I expected us to create, a brewfile inside this repo that people could tap with brew tap kubernetes-sigs/hydrophone (or hydrophone-brew or kubernetes-tap or who knows what else, if separation is desired) and use to get updates. goreleaser can create them for you.

dims commented 6 months ago

@cprivitere that does not sound too bad! :)

reetasingh commented 5 months ago

@cprivitere I have created a draft PR https://github.com/kubernetes-sigs/hydrophone/pull/178 PTAL

k8s-triage-robot commented 2 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 1 month ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 2 weeks ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot commented 2 weeks ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes-sigs/hydrophone/issues/142#issuecomment-2333044053): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ 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-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.