> I recall getting a direct email to me if I contributed a
> change to a CI failure. I would like this. I would also like a dev
> list email periodically (weekly?) listing the CI job status
+1 to any effort that aims to summarize "builds@".
Even for folks that check "builds@" regularly it can b
We could add (yet) another Github workflow validation. Or maybe take
the Docker one, which looks at certain paths (including bin/solr), and
generalizes to be not just testing docker but also running BATS
integration tests. Then think of this as the "integration test"
build. The "paths" it looks
I think a weekly heads up would be great to have.
You mention “PR validation doesn’t run BATS tests”…. Maybe it should? We’ve
had a lot of churn in the CLI, and we’ll probably continue to have that till
10x comes out, so that would be a nice check. Plus, if we add more
integration style
I'm concerned that too few people look at the bui...@solr.apache.org
>From time to time I go look but we have no notifications other than
emailing that list.
If hypothetically nobody looked, we might as well not have CI at all;
we'd only have PR based validation. We'd lose out on historic test
fa
