From a5ac9c164bc0d16a879bef1cab1ccdaeac205bdc Mon Sep 17 00:00:00 2001
From: Artem Makhortov <13339874+artmakh@users.noreply.github.com>
Date: Thu, 3 Oct 2024 17:22:37 +0700
Subject: [PATCH] feat(ci): Add external-node build to Makefile (#3002)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

## What ❔

Add external-node build to Makefile

## Why ❔

<!-- Why are these changes done? What goal do they contribute to? What
are the principles behind them? -->
<!-- Example: PR templates ensure PR reviewers, observers, and future
iterators are in context about the evolution of repos. -->

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [x] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zk_supervisor fmt` and `zk_supervisor
lint`.
---
 docker/Makefile             | 8 ++++++--
 docs/guides/build-docker.md | 2 ++
 2 files changed, 8 insertions(+), 2 deletions(-)

diff --git a/docker/Makefile b/docker/Makefile
index 444a94ce221..c469587c8ff 100644
--- a/docker/Makefile
+++ b/docker/Makefile
@@ -56,7 +56,7 @@ check-tools: check-nodejs check-yarn check-rust check-sqlx-cli check-docker chec
 # Check that contracts are checkout properly
 check-contracts:
 	@if [ ! -d ../contracts/l1-contracts/lib/forge-std/foundry.toml ] || [ -z "$$(ls -A ../contracts/l1-contracts/lib/forge-std/foundry.toml)" ]; then \
-		echo "l1-contracts git submodule is missing. Please re-download repo with `git clone --recurse-submodules https://github.com/matter-labs/zksync-era.git`"; \
+		echo "l1-contracts git submodule is missing. Please re-download repo with 'git clone --recurse-submodules https://github.com/matter-labs/zksync-era.git'"; \
 		exit 1; \
 	fi
 
@@ -93,9 +93,12 @@ build-witness-generator: check-tools prepare-keys
 	$(DOCKER_BUILD_CMD) --file witness-generator/Dockerfile --load \
 		--tag witness-generator:$(PROTOCOL_VERSION) $(CONTEXT)
 
+build-external-node: check-tools prepare-contracts
+	$(DOCKER_BUILD_CMD) --file external-node/Dockerfile --load \
+		--tag external-node:$(PROTOCOL_VERSION) $(CONTEXT)
 
 # Build all containers
-build-all: build-contract-verifier build-server-v2 build-witness-generator build-circuit-prover-gpu cleanup
+build-all: build-contract-verifier build-server-v2 build-witness-generator build-circuit-prover-gpu build-external-node cleanup
 
 # Clean generated images
 clean-all:
@@ -104,3 +107,4 @@ clean-all:
 	docker rmi server-v2:$(PROTOCOL_VERSION) >/dev/null 2>&1
 	docker rmi prover:$(PROTOCOL_VERSION) >/dev/null 2>&1
 	docker rmi witness-generator:$(PROTOCOL_VERSION) >/dev/null 2>&1
+	docker rmi external-node:$(PROTOCOL_VERSION) >/dev/null 2>&1
diff --git a/docs/guides/build-docker.md b/docs/guides/build-docker.md
index a9e8f5d3e76..5dd9cff022b 100644
--- a/docs/guides/build-docker.md
+++ b/docs/guides/build-docker.md
@@ -25,6 +25,7 @@ contract-verifier:2.0
 server-v2:2.0
 prover:2.0
 witness-generator:2.0
+external-node:2.0
 ```
 
 Alternatively, you may build only needed components - available targets are
@@ -34,6 +35,7 @@ make -C ./docker build-contract-verifier
 make -C ./docker build-server-v2
 make -C ./docker build-circuit-prover-gpu
 make -C ./docker build-witness-generator
+make -C ./docker build-external-node
 ```
 
 ## Building updated images