registry/tests/integration/run.sh
Radoslav Dimitrov b0a79c110c
Use ko in favour of docker build (#708)
<!-- Provide a brief summary of your changes -->

## Motivation and Context
<!-- Why is this change needed? What problem does it solve? -->
The following PR leverages ko instead of docker build for building the
container image.

The motivation for the move is that ko has been one of the widely
adopted ways to build Go applications, but overall its benefits are:
* Build time is much faster - around 70-80%
* The resulting image size is much smaller (also more secure) - around
50% smaller

The changes in this PR are:
* Updated the workflows for staging and release to prod to use it
* Updated the local development + the integration tests to use it (the
integration tests overwrite the base image from chainguards one to
alpine mostly because we rely on wget to check the health status and you
don't get that in the stripped down one)
 
From the user point of view everything should continue to work as it is.
 
## How Has This Been Tested?
<!-- Have you tested this in a real application? Which scenarios were
tested? -->

## Breaking Changes
<!-- Will users need to update their code or configurations? -->

## Types of changes
<!-- What types of changes does your code introduce? Put an `x` in all
the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)
- [ ] Documentation update

## Checklist
<!-- Go over all the following points, and put an `x` in all the boxes
that apply. -->
- [ ] I have read the [MCP
Documentation](https://modelcontextprotocol.io)
- [ ] My code follows the repository's style guidelines
- [ ] New and existing tests pass locally
- [ ] I have added appropriate error handling
- [ ] I have added or updated documentation as needed

## Additional context
<!-- Add any other context, implementation notes, or design decisions
-->

---------

Signed-off-by: Radoslav Dimitrov <radoslav@stacklok.com>
2025-10-29 15:16:11 +00:00

49 lines
1.8 KiB
Shell
Executable file

#!/bin/bash
set -e
# Use a unique project name to avoid conflicts with dev environment
export COMPOSE_PROJECT_NAME=registry-integration-test
cleanup() {
echo "========== registry logs =========="
docker logs registry-integration-test || true
echo "=========== cleaning up ==========="
# Clean up integration test containers and volumes
docker compose -f docker-compose.yml -f tests/integration/docker-compose.integration-test.yml down -v || true
# Force remove containers by name as backup (in case compose context is confused)
docker rm -f registry-integration-test postgres-integration-test 2>/dev/null || true
# Clean up any leftover volumes that might have been created
docker volume prune -f || true
echo "Cleanup completed"
}
go build -o ./bin/publisher ./cmd/publisher
# Build the registry image with ko, forcing a rebuild to ensure latest code
# Use Alpine for integration tests because health checks need wget (production uses static image)
echo "Building registry image with ko..."
VERSION=dev-$(git rev-parse --short HEAD) \
GIT_COMMIT=$(git rev-parse HEAD) \
BUILD_TIME=$(date -u +%Y-%m-%dT%H:%M:%SZ) \
KO_DOCKER_REPO=ko.local \
KO_DEFAULTBASEIMAGE=alpine:latest \
ko build --preserve-import-paths --tags=dev --sbom=none ./cmd/registry
# Tag the ko.local image with the tags expected by docker-compose
docker tag ko.local/github.com/modelcontextprotocol/registry/cmd/registry:dev registry
docker tag ko.local/github.com/modelcontextprotocol/registry/cmd/registry:dev modelcontextprotocol/registry:dev
trap cleanup EXIT
# Clean up any leftover containers from previous runs
echo "Pre-cleanup: removing any leftover containers..."
cleanup
docker compose -f docker-compose.yml -f tests/integration/docker-compose.integration-test.yml up --wait --wait-timeout 60
go run tests/integration/main.go