Build

The purpose of P2P build is to

• Run any local tests + static verification
• Build an immutable versioned artifact to pass through the rest of the P2P.

Pushing to the fast feedback registry

For deployed testing to take place push a versioned artifact to the registry required for fast feedback:

docker image push $(REGISTRY)/$(FAST_FEEDBACK_PATH)/<app-name>:$(VERSION)

Variables set by the P2P that you can use:

• REGISTRY
• VERSION

Parallel builds

Pass make-flags: '--jobs=4' on the application’s workflow call alongside runner-label to run independent Make recipes concurrently. Each application in a monorepo can choose its own limit. An empty input uses the optional P2P_MAKEFLAGS fallback; if both are empty, P2P adds no Make options. Declare dependencies such as push-app: build-app before opting in; see Make parallelism for configuration and an example.