> I think it would be good to have a build infra section under https://beam.apache.org/contribute/ that contains the dashboard link and other related information.
I previously wrote a page for the wiki: https://cwiki.apache.org/confluence/display/BEAM/Community+Metrics . I chose the wiki over website because Community Metrics is Beam contributor-focused (as opposed to for Beam users), and not tied to a release. If it would fit better on the website, we can move it. > Hmm, currently blank for me. Interesting. Works for me now. We have prober tests that verify that the infrastructure is healthy: https://builds.apache.org/job/beam_Prober_CommunityMetrics/ I wonder what happened in this case. > Also a hardcoded i.p. ? We should get it a proper DNS and health check, perhaps? Yes, ugly indeed. Mikhail was previously looking into getting an SSL cert for HTTPS / login support; a proper domain name seems appropriate too. I believe the previously roadblock was finding funding for it. On Sat, Feb 16, 2019 at 7:50 PM Kenneth Knowles <[email protected]> wrote: > Hmm, currently blank for me. Also a hardcoded i.p. ? We should get it a > proper DNS and health check, perhaps? > > Kenn > > On Sat, Feb 16, 2019 at 9:14 AM Thomas Weise <[email protected]> wrote: > >> This is super useful information. >> >> I think it would be good to have a build infra section under >> https://beam.apache.org/contribute/ that contains the dashboard link and >> other related information. >> >> WDYT? >> >> >> On Mon, Oct 29, 2018 at 3:26 AM Maximilian Michels <[email protected]> >> wrote: >> >>> Hi Scott, >>> >>> Thanks for sharing the progress. The test metrics are super helpful. I'm >>> particularly looking forward to the PR metrics which could be useful for >>> improving interaction within the community and with new contributors. >>> >>> -Max >>> >>> On 26.10.18 07:36, Scott Wegner wrote: >>> > I want to summarize some of the great work done this summer by >>> Mikhail, >>> > Udi, and Huygaa to visualize and track some project/community health >>> > metrics for Beam. Specifically, they've helped to build dashboards for: >>> > * Test suite health (pre-commit speed, post-commit reliability) >>> > * Pull Request health (code review latency, PR load per reviewer) >>> > >>> > Check it out here: https://s.apache.org/beam-community-metrics, and >>> > please leave feedback on this thread or under our umbrella JIRA item: >>> > BEAM-5862. >>> > >>> > There's some new infrastructure behind this which is hosted alongside >>> > our Jenkins resources on Google Cloud. I want to ensure this doesn't >>> > become a burden for the community, so I've written up a maintenance >>> plan >>> > here: https://s.apache.org/beam-community-metrics-infra. That link >>> > contains more details on the metrics pipeline architecture components, >>> > the design discussions which lead to building them, and my proposal >>> for >>> > documenting and monitoring the infrastructure. >>> > >>> > There was a ton of discussion [1][2][3] that helped shape the >>> dashboards >>> > we've come up with. There's a whole lot we didn't get to, but the >>> source >>> > code is documented and checked-in [4], and I encourage others in the >>> > community to add to it. >>> > >>> > Thanks, >>> > Scott >>> > >>> > [1] >>> > >>> https://lists.apache.org/thread.html/b73cc4f0f05f4654eed2250aa95f205e7ab45253d98add0240911031@%3Cdev.beam.apache.org%3E >>> > [2] >>> > >>> https://lists.apache.org/thread.html/3bb4aa777751da2e2d7e22666aa6a2e18ae31891cb09d91718b75e74@%3Cdev.beam.apache.org%3E >>> > [3] >>> > >>> https://lists.apache.org/thread.html/6cc942a34867ce7603392246c518c35410e828e9d2f17fdc547576ea@%3Cdev.beam.apache.org%3E >>> > [4] https://github.com/apache/beam/tree/master/.test-infra/metrics >>> > >>> > >>> > Got feedback? tinyurl.com/swegner-feedback >>> > <https://tinyurl.com/swegner-feedback> >>> >> -- Got feedback? tinyurl.com/swegner-feedback
