It looks like you can configure at the branch level and disable. https://discuss.circleci.com/t/is-there-a-way-to-prevent-automatic-build-on-a-branch/4085
On Tue, Mar 24, 2020, 2:04 PM Benedict Elliott Smith <bened...@apache.org> wrote: > You can have two repositories, one that triggers CI and one that doesn't, > if you're that paranoid > > On 24/03/2020, 21:03, "Joshua McKenzie" <jmcken...@apache.org> wrote: > > > > > You could push to the repository that triggers CI less frequently? > > For the paranoid among us or those that work on a variety of machines > over > time, this does represent a sub-optimal arrangement. > > > On Tue, Mar 24, 2020 at 4:38 PM Benedict Elliott Smith < > bened...@apache.org> > wrote: > > > You could push to the repository that triggers CI less frequently? I > > don't think it cares about commits, but pushes. > > > > I think some people like to see feedback promptly, without having to > go in > > manually until a dtest run is needed closer to patch completion. > > Unfortunately this is a situation where defaults inherently cannot > serve > > everyone equally well. > > > > FWIW, I don't mind either way. CircleCI gives me a headache anyway, > so > > I'm not sure you're solving the underlying problem 😊 > > > > > > On 24/03/2020, 20:23, "Ekaterina Dimitrova" < > > ekaterina.dimitr...@datastax.com> wrote: > > > > Hi both, > > Yes, Josh, that's what I meant. No disabling of tests or running > out of > > responsibility to submit patch after a full proper CI run. > > I am a person who does a lot of commits before final squash and > > honestly, > > looking now at my Circle history - I have a headache. > > Ekaterina Dimitrova | Software Engineer > > ekaterina.dimitr...@datastax.com | datastax.com > > < > > > http://datastax.com/?utm_campaign=FY20Q2_CONSTELLATION&utm_+medium=email&utm_source=signature > > > > > > > > > > > > >> *From:* David Capwell <dcapw...@gmail.com> > > >> *Date:* 24 March 2020, 15:34:36 GMT-4 > > >> *To:* dev@cassandra.apache.org > > >> *Subject:* *Re: CircleCI config change?* > > >> *Reply-To:* dev@cassandra.apache.org > > >> > > >> > > >> > > >> > > >> I want to change it so it could be a manual choice whether to > do it > > or > > >> not. > > >> > > >> > > >> > > >> Could you explain the motivations for disabling the tests by > > default? My > > >> personal stance is all tests should run (we disable a lot, at > least > > HIGHER > > >> should enable all...), not a fan of disabling tests. > > >> > > >> On Tue, Mar 24, 2020 at 12:14 PM Ekaterina Dimitrova < > > >> ekaterina.dimitr...@datastax.com> wrote: > > >> > > >> Hello everyone, > > >> > > >> Hope this email finds you well! > > >> > > >> > > >> Just a heads up that I plan to open a Jira and change the > CircleCI > > config. > > >> > > >> Currently unit tests and in-jvm tests are triggered > automatically > > on every > > >> > > >> commit. > > >> > > >> I want to change it so it could be a manual choice whether to > do it > > or > > >> not. > > >> > > >> > > >> Anyone against that who really needs the current setup? Is > there any > > >> > > >> background information I miss? > > >> > > >> > > >> Ekaterina Dimitrova | Software Engineer > > >> > > >> ekaterina.dimitr...@datastax.com | datastax.com > > >> > > >> < > > >> > > >> > > >> > > > http://datastax.com/?utm_campaign=FY20Q2_CONSTELLATION&utm_+medium=email&utm_source=signature > > >> > > >> > > >> > > >> > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > > For additional commands, e-mail: dev-h...@cassandra.apache.org > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > >
