Workflow: Use unique container names to avoid build conflicts
Some checks failed
Build Tamigo CLI / Build Linux Binary (push) Successful in 49s
Build Tamigo CLI / Build Windows Binary (push) Failing after 16s

This commit is contained in:
Daniel Dybing
2026-03-11 14:22:21 +01:00
parent 334ceae3ea
commit 4577d9f6b9
2 changed files with 24 additions and 17 deletions

View File

@@ -40,23 +40,28 @@ jobs:
steps:
- uses: actions/checkout@v4
- name: Build Windows executable via Docker (Stable)
- name: Build Windows executable via Docker (Unique Names)
run: |
# Use a standard Wine-based PyInstaller image
docker create --name builder cdrx/pyinstaller-windows
# Ensure unique container name for this run
CONTAINER_NAME="builder-${{ github.run_id }}"
# Copy source code into the container
docker cp . builder:/src
# Clean up any existing container with this name just in case
docker rm -f $CONTAINER_NAME || true
# Run the build using the image's internal logic but specifying our requirements
# Most of these images default to running 'pyinstaller' on the /src folder
docker start -a builder
# Create container
docker create --name $CONTAINER_NAME cdrx/pyinstaller-windows
# Copy the results back
docker cp builder:/src/dist .
# Copy source code
docker cp . $CONTAINER_NAME:/src
# Run build
docker start -a $CONTAINER_NAME
# Copy results
docker cp $CONTAINER_NAME:/src/dist .
# Clean up
docker rm builder
docker rm $CONTAINER_NAME
- name: Debug - List output files
run: ls -R dist/