I recently had to fix at least two problems that could've been prevented by
running tests and checks that are about to be turned off by default ([1]
and [2]).
I'd like to point out that this has happened while checks were
theoretically enabled, and both problems could've been prevented. This
doesn
Hi Aleks,
Thanks for those fixes and pointing out this issue.
I didn’t ask for tests not to be used and disabled. I asked whether we can make
them not to run on every single push to circleci as they are not always needed.
Intermediate pushes just to save pieces of work do not require immediate CI
If you just want to disable them for your own branch/branches - I don't see
any problem with that, I'm just not sure if it's a good default.
In a similar spirit, I know that some folks are running the script to set
up HIGHRES environment for circle ci every time they create a branch even
though it
I think there's more we can do to customize the circie setup, and am also a
hard -1 on disabling testing by default. We should figure out a way to opt
out of it, but the default should be on.
On Wed, Mar 25, 2020 at 7:51 AM Oleksandr Petrov
wrote:
> If you just want to disable them for your ow
Seems there's not an easy consensus. Rather than digging into any data and
reasoning behind the differing opinions that have been shared, we should
probably just look into further Circle config and/or local scripting to
flip bits in the config on branch creation for people that want auto
testing on
>
> we should probably just look into further Circle config and/or local
> scripting to flip bits in the config on branch creation for people that
> want auto testing on push disabled
If there are improvements we can make to the config to allow opt-out, I
am +1 to adding them (not uncommon to fla
It has been a few years, but I think we came to basically the same
conclusion on build/test skipping in autojobs for CassCI. Most wanted
the job runs all the time, but a few wanted to skip runs for scratch or
WIP branches, in order to preserve resources when they didn't care what
the result was
I recently had to fix at least two problems that could've been prevented by
> running tests and checks that are about to be turned off by default ([1]
> and [2]).
>
> I'd like to point out that this has happened while checks were
> theoretically enabled, and both problems could've been prevented. T
