optimize: Docker Build Times

[kalverra]

• Increase concurrency on loopinstall builds in CI
• Fix cache-map

---

_{Stack created with GitHub Stacks CLI • Give Feedback 💬}

[github-actions]

✅ No conflicts with other open PRs targeting develop

[Copilot]

Pull request overview

Risk Rating: MEDIUM

This PR targets faster Docker image builds in CI by increasing loopinstall parallelism for remote plugin installation and adjusting the CI cache-map to persist the Go build cache more directly.

Changes:

• Add CL_LOOPINSTALL_CONCURRENCY as a configurable knob (Make + Docker build args/env) and wire it into go tool loopinstall.
• Increase default concurrency used in Docker builds (default build arg set to 16).
• Update the integration tests workflow cache-map entry for the Go build cache.

Areas needing scrupulous human review:

• .github/workflows/integration-tests.yml cache-map format and key naming (depends on behavior/schema of the external ctf-build-image action).

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File	Description
plugins/chainlink.Dockerfile	Adds a build arg/env for CL_LOOPINSTALL_CONCURRENCY and passes it into plugin install make targets.
GNUmakefile	Introduces CL_LOOPINSTALL_CONCURRENCY and uses it for go tool loopinstall concurrency.
core/chainlink.Dockerfile	Mirrors the plugin Dockerfile changes to control loopinstall concurrency during image builds.
.github/workflows/integration-tests.yml	Changes the build step cache-map to target /root/.cache/go-build for the Go build cache.

Suppressed comments (2)

GNUmakefile:104

• In the output-dir branch, $(LOOPINSTALL_TESTING_ARGS) already includes the --output-installation-artifacts $(CL_LOOPINSTALL_OUTPUT_DIR)/testing.json flag/value, so passing it again explicitly is redundant.

install-plugins-testing: ## Build & install testing only LOOPP binaries (plugins).
	if [ -n "$(CL_LOOPINSTALL_OUTPUT_DIR)" ]; then \
		GOPRIVATE=github.com/smartcontractkit/* go tool loopinstall --concurrency $(CL_LOOPINSTALL_CONCURRENCY) $(LOOPINSTALL_TESTING_ARGS) --output-installation-artifacts $(CL_LOOPINSTALL_OUTPUT_DIR)/testing.json ./plugins/plugins.testing.yaml; \
	else \

GNUmakefile:96

• In the output-dir branch, $(LOOPINSTALL_PRIVATE_ARGS) already includes the --output-installation-artifacts $(CL_LOOPINSTALL_OUTPUT_DIR)/private.json flag/value, so the explicit --output-installation-artifacts .../private.json here is redundant.

	if [ -n "$(CL_LOOPINSTALL_OUTPUT_DIR)" ]; then \
		GOPRIVATE=github.com/smartcontractkit/* go tool loopinstall --concurrency $(CL_LOOPINSTALL_CONCURRENCY) $(LOOPINSTALL_PRIVATE_ARGS) --output-installation-artifacts $(CL_LOOPINSTALL_OUTPUT_DIR)/private.json ./plugins/plugins.private.yaml; \
	else \

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[trunk-io]

   

Failed Test	Failure Summary	Logs
Test_CCIP_Messaging_EVM2Sui_Success/Message_to_Sui	The test failed because it timed out waiting for a commit report on the chain, indicating a synchronization or response delay.	Logs ↗︎
Test_CCIP_Messaging_EVM2Sui_Success	The test failed without a specific error message, likely due to an unexpected issue during execution.	Logs ↗︎

View Full Report ↗︎ ⋅ Docs

[chainchad]

Was this an accidentally committed file?

[cl-sonarqube-production]

Quality Gate failed

Failed conditions
12 New Major Issues (required ≤ 5)
28.44% Technical Debt Ratio on New Code (required ≤ 4%)
D Maintainability Rating on New Code (required ≥ A)

See analysis details on SonarQube

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE