CircleCI config is difficult to manage, easy to break.

[AlanRynne]

trafficstars

CircleCI makes me lose at least a day or two each quarter - can we clean up the sharp CI and possibly figure out if there’s a better way to handle this?

There are several ways of handling this on circleCI itself. But we could also consider not using circleCI altogether in favour of github Actions?

• We could split the CI config file into smaller .yml files, but that will require the use of circleci CLI to compile the parts back into a monolithic config file.
• We could publish private Orbs with the main functionality we want, and just have the main triggers in our speckle-sharp repo!

None of these options sound very nice to me, although the first one may be worth looking into.

[AlanRynne]

Some of these concerns were already addressed when we switched to dynamic config generation in CircleCI, but the sentiment still stands.

[AlanRynne]

Closing this for now, but I'll always be keeping an eye on how to make this better.