Makefile

all: build
.PHONY: all

# Include the library makefile
include $(addprefix ./vendor/github.com/openshift/build-machinery-go/make/, \
	golang.mk \
	targets/openshift/bindata.mk \
	targets/openshift/images.mk \
	targets/openshift/deps.mk \
)

IMAGE_REGISTRY :=registry.ci.openshift.org

# This will call a macro called "build-image" which will generate image specific targets based on the parameters:
# $0 - macro name
# $1 - target name
# $2 - image ref
# $3 - Dockerfile path
# $4 - context directory for image build
$(call build-image,openshift-tests,$(IMAGE_REGISTRY)/ocp/4.6:tests,./images/tests/Dockerfile.rhel,.)

# Old-skool build tools.
#
# Targets (see each target for more information):
#   all: Build code.
#   build: Build code.
#   check: Run verify, build, unit tests and cmd tests.
#   test: Run all tests.
#   run: Run all-in-one server
#   clean: Clean up.

# Tests run using `make` are most often run by the CI system, so we are OK to
# assume the user wants jUnit output and will turn it off if they don't.
JUNIT_REPORT ?= true

build-docs:
	hack/generate-docs.sh
.PHONY: build-docs

openshift-tests: GO_BUILD_PACKAGES :=./cmd/openshift-tests
openshift-tests: build
.PHONY: openshift-tests

# run repo-specific checks.
#
# Example:
#   make verify-origin
verify-origin:
	hack/verify-jsonformat.sh
	hack/verify-generated.sh
	hack/verify-tls-ownership.sh
.PHONY: verify-origin verify
verify: verify-origin verify-apm verify-shared

# Verify the test/shared module, which is a separate Go module and therefore
# not covered by the root module's checks: run its linter (self-pinned via
# the go.mod tool directive) and verify its dependency hygiene. This runs as
# part of `make verify` (the CI verify job) because the dedicated lint job
# only lints the root module.
verify-shared:
	$(MAKE) -C test/shared lint verify-deps
.PHONY: verify-shared

# Refresh go.mod, go.sum and vendor/
# Calls the same in test/shared recursively
update-gomod: shared-update-gomod
	go mod tidy
	go mod vendor
.PHONY: update-gomod

shared-update-gomod:
	$(MAKE) -C test/shared update-gomod
.PHONY: shared-update-gomod

# Update all generated artifacts.
#
# Example:
#   make update
update: update-tls-ownership update-bindata
	hack/update-generated.sh
.PHONY: update

# Update TLS artifacts
#
# Example:
#    make update-tls-ownership
update-tls-ownership:
	hack/update-tls-ownership.sh
.PHONY: update-tls-ownership

# Update external examples
#
# Example:
#	make update-examples
update-examples:
	hack/update-external-examples.sh
	$(MAKE) update-bindata
.PHONY: update-examples

# Run tools tests.
#
# Example:
#   make test-tools
test-tools:
	hack/test-tools.sh
.PHONY: test-tools

# Run extended tests.
#
# Args:
#   SUITE: Which Bash entrypoint under test/extended/ to use. Don't include the
#          ending `.sh`. Ex: `core`.
#   FOCUS: Literal string to pass to `--ginkgo.focus=`
# The FOCUS env variable is handled by the respective suite scripts.
#
# Example:
#   make test-extended SUITE=core
#   make test-extended SUITE=conformance FOCUS=pods
#
SUITE ?= conformance
test: test-tools
	test/extended/$(SUITE).sh
.PHONY: test

# test-unit is imported from openshift/build-machinery-go.
# We're just adding an additional dependency to it.
test-unit: shared-test-unit

shared-test-unit:
	$(MAKE) -C test/shared test-unit
.PHONY: shared-test-unit

# This will call a macro called "add-bindata" which will generate bindata specific targets based on the parameters:
# $0 - macro name
# $1 - target suffix
# $2 - input dirs
# $3 - prefix
# $4 - pkg
# $5 - output
# It will generate targets {update,verify}-bindata-$(1) logically grouping them in unsuffixed versions of these targets
# and also hooked into {update,verify}-generated for broader integration.
$(call add-bindata,bindata,-ignore ".*\.(go|md)$$$$" examples/db-templates examples/image-streams examples/sample-app examples/quickstarts/... examples/hello-openshift examples/jenkins/... examples/quickstarts/cakephp-mysql.json test/extended/testdata/... e2echart,testextended,testdata,test/extended/testdata/bindata.go)

# Requires uv (installed in devcontainer). Regenerates CLAUDE.md, AGENTS.md, etc.
# NB: the linter parses this file as shell and cannot cope with make functions.
# shellcheck disable=SC1009,SC1050,SC1072,SC1073
# apm-cli >= 0.35 keeps per-user state in ~/.apm (lifecycle lock, config) and
# does not honour APM_HOME for it. CI containers run with an empty HOME, which
# resolves to /, so point HOME at a scratch dir alongside the uv caches.
_uvx_env = $(if $(filter true,$(CI)),HOME=/tmp/apm-home UV_CACHE_DIR=/tmp/uv-cache UV_TOOL_DIR=/tmp/uv-tools)
# vendor/ trees are walked by apm compile; excluding them keeps regeneration fast.
# Nested AGENTS.md files are generated too, so they are listed explicitly.
_apm_generated = .claude .cursor .gemini .opencode .agents .github/instructions .github/prompts \
	.mcp.json opencode.json apm.lock.yaml AGENTS.md CLAUDE.md GEMINI.md test/shared/AGENTS.md
apm:
	$(_uvx_env) uvx --from apm-cli@0.35.0 apm install
	$(_uvx_env) uvx --from apm-cli@0.35.0 apm compile
.PHONY: apm

verify-apm: apm
	@if [ -n "$$(git status --porcelain -- $(_apm_generated))" ]; then \
		echo "ERROR: Generated APM files are out of date. Run 'make apm' and commit the results."; \
		git status --short -- $(_apm_generated); \
		exit 1; \
	fi
.PHONY: verify-apm