This email is confidential. If you are not the intended recipient, destroy all copies and do not disclose or use the information within. No warranties are given that this email does not contain viruses or harmful code.--
You received this message because you are subscribed to the Google Groups "bazel-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bazel-discus...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-discuss/489785f4-0f25-466b-8d4f-53ce59038b66%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-discuss/159f45d0-e73f-4813-9849-1b901cfa413c%40googlegroups.com.
Right now, when using bazel as a CI, there are no good tools around parsing the build results and displaying it in a manner easily navigable by people.
What the bazel team uses is excellent. I understand that there were issues around open-sourcing the code search website because of the way the work was contracted out. Even if it's the same case here, we will really appreciate any code that can be open sourced, and maybe somebody can build an open source website around it.
--
You received this message because you are subscribed to a topic in the Google Groups "bazel-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/bazel-discuss/xzRK3-zjarY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to bazel-discus...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-discuss/65e75108-9579-4a66-89a0-9a533c713468%40googlegroups.com.
If we can not get the website code, then even if we can get an example design that explains how to take the results and uploads of https://github.com/bazelbuild/continuous-integration/blob/master/buildkite/bazelci.py and make them suitable for display in a UI.
On Tuesday, July 17, 2018 at 10:00:08 PM UTC-7, James Judd wrote:
> I'll echo that sentiment and provide a friendly ping. We are still interested in seeing something like this open sourced. It would make it much easier for the team to understand build results in CI.
>
>
> I'm curious to get the CI team's opinion on this - is it something that could be open sourced?
>
>
> Best,
> James
>
>
> On Tue, Jul 17, 2018 at 7:10 PM <sbag...@grailbio.com> wrote:
> +1. We will also really benefit from any code that can be open sourced for the test results UI.
>
>
>
> Right now, when using bazel as a CI, there are no good tools around parsing the build results and displaying it in a manner easily navigable by people.
>
>
>
> What the bazel team uses is excellent. I understand that there were issues around open-sourcing the code search website because of the way the work was contracted out. Even if it's the same case here, we will really appreciate any code that can be open sourced, and maybe somebody can build an open source website around it.
>
>
>
> --
>
> You received this message because you are subscribed to a topic in the Google Groups "bazel-discuss" group.
>
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/bazel-discuss/xzRK3-zjarY/unsubscribe.
>
> To unsubscribe from this group and all its topics, send an email to bazel-discus...@googlegroups.com.
>
> To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-discuss/65e75108-9579-4a66-89a0-9a533c713468%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "bazel-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bazel-discus...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-discuss/5f157f89-d3de-49bd-938b-3d2ce286f86e%40googlegroups.com.