Macintosh-Tools
/
Retro68
mirror of https://github.com/autc04/Retro68.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
Retro68/azure-pipelines.yml

55 lines
1.7 KiB
YAML
Raw Normal View History

Add an azure build
2019-09-27 21:06:18 +00:00
trigger:
- master
start experimenting
2022-01-03 20:51:35 +00:00
Add an azure build
2019-09-27 21:06:18 +00:00
jobs:
- job: Linux
pool:
azure-pipelines.yml: switch from host build to container build This has two main advantages: firstly it means that the Dockerfile is being tested as part of the pipeline when changes are merged into master, and secondly it allows testing of Linux builds without requiring a separate job for Docker that can consume even more CI minutes. In order to test the container image it is necessary to manually start the build image using docker run, execute the tests, and then copy the results back to the host ready for publishing. Note that since the base OS image is now handled by docker we can switch the host to use the 'ubuntu-latest' image rather than the older 'ubuntu-20.04' image.
2022-10-21 14:00:55 +00:00
vmImage: 'ubuntu-latest'
increase timeouts on azure
2022-01-17 20:39:58 +00:00
timeoutInMinutes: 90
use variable group
2023-12-16 18:05:30 +00:00
variables:
- group: Tokens
Add an azure build
2019-09-27 21:06:18 +00:00
steps:
- checkout: self
submodules: true
reactivate actual build
2023-12-16 19:39:52 +00:00
azure-pipelines.yml: switch from host build to container build This has two main advantages: firstly it means that the Dockerfile is being tested as part of the pipeline when changes are merged into master, and secondly it allows testing of Linux builds without requiring a separate job for Docker that can consume even more CI minutes. In order to test the container image it is necessary to manually start the build image using docker run, execute the tests, and then copy the results back to the host ready for publishing. Note that since the base OS image is now handled by docker we can switch the host to use the 'ubuntu-latest' image rather than the older 'ubuntu-20.04' image.
2022-10-21 14:00:55 +00:00
- task: Docker@2
inputs:
command: build
reactivate actual build
2023-12-16 19:39:52 +00:00
repository: ghcr.io/autc04/retro68-build
azure-pipelines.yml: switch from host build to container build This has two main advantages: firstly it means that the Dockerfile is being tested as part of the pipeline when changes are merged into master, and secondly it allows testing of Linux builds without requiring a separate job for Docker that can consume even more CI minutes. In order to test the container image it is necessary to manually start the build image using docker run, execute the tests, and then copy the results back to the host ready for publishing. Note that since the base OS image is now handled by docker we can switch the host to use the 'ubuntu-latest' image rather than the older 'ubuntu-20.04' image.
2022-10-21 14:00:55 +00:00
tags: latest
reactivate actual build
2023-12-16 19:39:52 +00:00
arguments: --target build
run azure tests for macOS, clean up azure-pipelines.yml, remove disabled "Timeout" test case
2019-09-29 08:36:10 +00:00
displayName: 'Build'
reactivate actual build
2023-12-16 19:39:52 +00:00
- task: Docker@2
inputs:
command: build
repository: ghcr.io/autc04/retro68
tags: latest
arguments: --target release
displayName: 'Build release'
- script: |
docker run --name retro68-build --rm -i -d ghcr.io/autc04/retro68-build:latest
docker exec -i retro68-build /bin/bash <<"EOF"
cd /Retro68-build
curl -L -O https://github.com/autc04/executor/releases/download/v0.1.0/Executor2000-0.1.0-Linux.tar.bz2
tar xfvj Executor2000-0.1.0-Linux.tar.bz2 Executor2000-0.1.0-Linux/bin/executor-headless
echo "executor-path=`pwd`/Executor2000-0.1.0-Linux/bin/executor-headless" > ~/.LaunchAPPL.cfg
echo "emulator=executor" >> ~/.LaunchAPPL.cfg
ctest --no-compress-output -T test -E Carbon || true
EOF
mkdir build && docker cp retro68-build:/Retro68-build/Testing build
docker stop retro68-build
displayName: Run Tests using Executor 2000
- task: PublishTestResults@2
inputs:
testResultsFormat: 'CTest'
testResultsFiles: build/Testing/**/*.xml
buildPlatform: 'x86_64-linux'
use variable group
2023-12-16 18:05:30 +00:00
- script: |
docker login ghcr.io/autc04 -u autc04 -p $GHCR_TOKEN
reactivate actual build
2023-12-16 19:39:52 +00:00
docker push ghcr.io/autc04/retro68
use variable group
2023-12-16 18:05:30 +00:00
env:
GHCR_TOKEN: $(GHCR_TOKEN)
displayName: 'Push release to GHCR'
reactivate actual build
2023-12-16 19:39:52 +00:00
# condition: and(succeeded(), eq(variables['Build.SourceBranch'], 'refs/heads/master'))