t; > > without caring of build or anything. If for some reason it is
>> important
>> > > to
>> > > > you or anyone else from the community to build on every commit, we
>> can
>> > > open
>> > > > a ticket to change that. It will sa
rwrite the config file, it
> > > would seem easy enough to instead invoke a script that enables the
> > relevant
> > > workflows?
> > >
> > > If we choose to just stick with a single workflow, I don’t have a super
> > > strong preference for on
t; workflows?
> >
> > If we choose to just stick with a single workflow, I don’t have a super
> > strong preference for one approach or the other.
> >
> > From: Stefan Miklosovic
> > Date: Wednesday, 20 October 2021 at 16:58
> > To: dev@cassandra.apache.or
e a super
> strong preference for one approach or the other.
>
> From: Stefan Miklosovic
> Date: Wednesday, 20 October 2021 at 16:58
> To: dev@cassandra.apache.org
> Subject: Re: Save CircleCI resources with optional test jobs
> Hi Ekaterina, all,
>
> If you eventually deci
a super strong
preference for one approach or the other.
From: Stefan Miklosovic
Date: Wednesday, 20 October 2021 at 16:58
To: dev@cassandra.apache.org
Subject: Re: Save CircleCI resources with optional test jobs
Hi Ekaterina, all,
If you eventually decide to switch it to automatic build on
r the build automatically. As it is we have to traverse the
> > dependency graph manually, which is a bit weird.
> >
> > I can’t figure out a way to do this with the CircleCI API however. It
> > might be a feature request, and perhaps we can at least trigger the build
> >
dnesday, 20 October 2021 at 13:35
> To: dev
> Subject: Re: Save CircleCI resources with optional test jobs
> I thought this discussion was still ongoing, but it looks like
> CASSANDRA-16882 is now committed.
>
> Could you give some context on why at least compilation is not done
perhaps we can at least trigger the build until we get
that (which may never happen).
From: Oleksandr Petrov
Date: Wednesday, 20 October 2021 at 13:35
To: dev
Subject: Re: Save CircleCI resources with optional test jobs
I thought this discussion was still ongoing, but it looks like
CASSANDRA
I thought this discussion was still ongoing, but it looks like
CASSANDRA-16882 is now committed.
Could you give some context on why at least compilation is not done on
every commit now?
On Fri, Oct 8, 2021 at 4:12 PM Oleksandr Petrov
wrote:
> I personally rarely push tickets/post a patch in an
I personally rarely push tickets/post a patch in an raw state, but since I
almost always have to approve jobs when it gets close to commit, I don't
mind also confirming utest runs. I'd say it'd be good to run at very least
a compilation step on every commit. I think it's fine if dtests/utests/jvm
t
Hello all,
The changes in CircleCI proposed in the previous messages are implemented
in CASSANDRA-16882. They try to include the feedback from both the
reviewers and the Slack discussion at
https://the-asf.slack.com/archives/CK23JSY2K/p1631627458109000.
The patch modifies the CircleCI config to h
Hi,
CASSANDRA-16882 has patches for any of the mentioned configurations aimed
to save CircleCI resources.
There are CircleCI runs showing how each approach would look like, plus an
additional fourth option:
1. Make the entire workflow optional:
https://app.circleci.com/pipelines/github/adelapena
Hello all,
The current CircleCI configuration automatically runs the unit tests, JVM
dtests and cqhshlib tests. This is done by default for every commit or,
with some configuration, for every push.
Along the lifecycle of a ticket it is quite frequent to have multiple
commits and pushes, all runni
13 matches
Mail list logo
