Question: How to use / For what to use Parallelism in CircleCI

[Szandor72]

I have successfully set everything up to use SalesforceDX Beta, CircleCI and the CircleCI GitHub Trigger that initiates builds in multiple containers.

What I am missing is how to use this feature correctly/efficiently. 3 containers, creating 3 scratch orgs doing all the same thing. I need some inspiration, push into the right direction where to investigate further.

(Ive put this question here rather with CumulusCI since I know Salesforce.org has since moved to MrBelvedereCI.)

[jlantz]

If I were looking at building a CircleCI implementation, I'd need to take a look at all the new 2.0/pipelines stuff they've added recently. It's possible that removes the need for the circleci-github-trigger app. The purpose of that app was to get around a prior limitation in CircleCI's configurations. We wanted feature builds to run with 1 container and master builds to run with as many as 8 containers (multiple beta test environments in parallel). The parallelism is (was?) only configurable on a repository rather than on individual build types or branches. As a result, to have an 8 container master build meant all feature builds needed to be 8 container too. The circleci-github-trigger can run feature builds and set the parallelization to 1 so only one container gets used for the build while master builds still run with 8.

[Szandor72]

That was enlightening! My idea was to spread out feature builds when master to feature happens. It seems to me too that some of this should be doable with circleci 2.0.