A set of workflows that publish:

• https://hub.docker.com/repository/docker/temporaliotest/auto-setup
• https://hub.docker.com/repository/docker/temporaliotest/server
• https://hub.docker.com/repository/docker/temporaliotest/admin-tools

There are 3 distinct phases:

All build steps require a set of Docker base images. They are released by a user whenever a new version of a base image is needed.

• release-base-image: build and release a single Docker base image (temporalio/base-*) to DockerHub temporalio
• release-all-base-image: build and release all Docker base images (temporalio/base-*) to DockerHub temporalio

Read more details about base images.

For every commit to Temporal Server's main and release branch, its Trigger Publish will invoke update-submodules to update all submodules to their latest commit - and run the following actions:

• lint: lint repo's shell scripts
• docker: build Docker images and publish to DockerHub temporaliotest
• docker-build-only: build Docker images, but don't publish (used by features-integration workflow)
• features-integration: run integration tests against features repo

Users can publish any of the previously built images via:

• release-admin-tools: copy admin-tools image from DockerHub temporaliotest to DockerHub temporalio
• release-temporal: copy server and auto-setup images from DockerHub temporaliotest to DockerHub temporalio

Replace YOUR_TAG and YOUR_CHECKOUT_COMMIT to build manually:

git checkout YOUR_CHECKOUT_COMMIT
docker build . -f auto-setup.Dockerfile -t temporalio/auto-setup:YOUR_TAG