Another thing worth mentioning is the overhead with providing, setting up, and
managing infrastructure. While donations of servers/VM’s works to some extent,
it’s a somewhat archaic donation policy – and this whole structure of CI gives
both the ASF and the C* project very limited choices. From
Related to instances, can we get those credits put to use that Amazon promised
to give back to the community as part of their Amazon Managed Cassandra Service
announcement?
Alternatively if there is an appetite to set something in patreon or GitHub’s
donation platform , it may be a good way to
Following Mick's format =)
** Lack of trust (aka reliability)
Mick said it best, but should also add that we have slow tests and tests
which don't do anything. Effort is needed to improve our current tests and
to make sure future tests are stable (cleaning up works, isolation, etc.);
this is
Only have a moment to respond, but Mick hit the higlights with
containerization, parallelization, these help solve cleanup, speed, and
cascading failures. Dynamic disposable slaves would be icing on that
cake, which may require a dedicated master.
One more note on jobs, or more correctly
Mick, this is fantastic!
I'll wait another day to see if anyone else chimes in. (Would also love to
hear from CassCI folks, anyone else really who has wrestled with this even
for internal forks).
On Tue, Feb 4, 2020 at 10:37 AM Mick Semb Wever wrote:
> Nate, I leave it to you to forward
Nate, I leave it to you to forward what-you-chose to the board@'s thread.
> Are there still troubles and what are they?
TL;DR
the ASF could provide the Cassandra community with an isolated jenkins
installation: so that we can manage and control the Jenkins master, as well as
ensure all
Hi folks,
The board is looking for feedback on CI infrastructure. I'm happy to take
some (constructive) comments back. (Shuler, Mick and David Capwell
specifically as folks who've most recently wrestled with this a fair bit).
Thanks,
-Nate
-- Forwarded message -
From: Dave Fisher
