RPCS3/rpcs3
1
0
Fork 0
mirror of https://github.com/RPCS3/rpcs3.git synced 2024-11-22 02:32:36 +01:00
Code Issues Releases Wiki Activity
cd94d9849d
rpcs3/azure-pipelines.yml

108 lines
2.7 KiB
YAML
Raw Normal View History

Azure (#7673) * Set up CI with Azure Pipelines
2020-03-02 23:55:05 +01:00
trigger:
Properly setup Azure Pipelines using current system Also sets up Azure artifacts (including for PRs) for AppImages
2020-03-03 03:42:28 +01:00
branches:
include:
- master
tags:
exclude:
- '*'
Try to re-enable Azure Pipelines for PRs
2020-03-14 20:50:17 +01:00
pr:
branches:
include:
- master
Properly setup Azure Pipelines using current system Also sets up Azure artifacts (including for PRs) for AppImages
2020-03-03 03:42:28 +01:00
jobs:
- job: Linux_Build
strategy:
matrix:
Clang:
COMPILER: clang
GCC:
COMPILER: gcc
DEPLOY_APPIMAGE: true
variables:
CCACHE_DIR: $(Pipeline.Workspace)/ccache
CI: Maintenance - Rename .travis dir to .ci, since it isn't just for Travis - Convert Linux build scripts to posix sh - Clean up some scripts per shellcheck
2020-04-07 04:53:23 +02:00
IS_AZURE: true
Properly setup Azure Pipelines using current system Also sets up Azure artifacts (including for PRs) for AppImages
2020-03-03 03:42:28 +01:00
pool:
vmImage: 'ubuntu-latest'
steps:
CI: Update Azure cache task to newer version
2020-03-28 21:13:55 +01:00
- task: Cache@2
Properly setup Azure Pipelines using current system Also sets up Azure artifacts (including for PRs) for AppImages
2020-03-03 03:42:28 +01:00
inputs:
key: ccache | $(Agent.OS) | $(COMPILER)
path: $(CCACHE_DIR)
CI: Port Windows build to Azure Pipelines (#7757) * CI: Port Windows build to Azure Pipelines from Appveyor * CI: Split Windows build into scripts * CI: Remove Appveyor * CI: Add GitHub Release deployment to Azure Windows Build * VCS: Add full branch name function to rpcs3_version The STRINGIZE macro was a little awkward, and difficult to control at configure time. Since other version information is already included, the full branch name is now added as a function. It's runtime instead of compile-time checking, but it seems worth it. * CI: Overhaul Windows setup script Previously, there was no way of forcing a re-download of cached dependencies when they were replaced by new ones. In addition, there was really no verification of downloads or cache. Now, changing a few lines at the top of the file will automagically force a cache update.
2020-03-27 14:37:27 +01:00
displayName: ccache
Try to re-enable Azure Pipelines for PRs
2020-03-14 20:50:17 +01:00
Properly setup Azure Pipelines using current system Also sets up Azure artifacts (including for PRs) for AppImages
2020-03-03 03:42:28 +01:00
- bash: |
Bump Linux CI version (#8226) This updates Qt to 5.14.2, Ninja to 1.10.0, SDL2 to 2.0.12
2020-05-15 05:04:24 +02:00
docker pull --quiet rpcs3/rpcs3-travis-xenial:1.4
Properly setup Azure Pipelines using current system Also sets up Azure artifacts (including for PRs) for AppImages
2020-03-03 03:42:28 +01:00
docker run \
-v $(pwd):/rpcs3 \
CI: Maintenance - Rename .travis dir to .ci, since it isn't just for Travis - Convert Linux build scripts to posix sh - Clean up some scripts per shellcheck
2020-04-07 04:53:23 +02:00
--env-file .ci/travis.env \
Properly setup Azure Pipelines using current system Also sets up Azure artifacts (including for PRs) for AppImages
2020-03-03 03:42:28 +01:00
-v $CCACHE_DIR:/root/.ccache \
-v $BUILD_ARTIFACTSTAGINGDIRECTORY:/root/artifacts \
Bump Linux CI version (#8226) This updates Qt to 5.14.2, Ninja to 1.10.0, SDL2 to 2.0.12
2020-05-15 05:04:24 +02:00
rpcs3/rpcs3-travis-xenial:1.4 \
CI: Maintenance - Rename .travis dir to .ci, since it isn't just for Travis - Convert Linux build scripts to posix sh - Clean up some scripts per shellcheck
2020-04-07 04:53:23 +02:00
/rpcs3/.ci/build-linux.sh
Properly setup Azure Pipelines using current system Also sets up Azure artifacts (including for PRs) for AppImages
2020-03-03 03:42:28 +01:00
displayName: Docker setup and build
Try to re-enable Azure Pipelines for PRs
2020-03-14 20:50:17 +01:00
Properly setup Azure Pipelines using current system Also sets up Azure artifacts (including for PRs) for AppImages
2020-03-03 03:42:28 +01:00
- publish: $(Build.ArtifactStagingDirectory)
Unify Azure artifacts names and produce them only on successful build.
2020-06-08 03:31:12 +02:00
condition: and(succeeded(), eq(variables['COMPILER'], 'gcc'))
artifact: RPCS3 for Linux
CI: Port Windows build to Azure Pipelines (#7757) * CI: Port Windows build to Azure Pipelines from Appveyor * CI: Split Windows build into scripts * CI: Remove Appveyor * CI: Add GitHub Release deployment to Azure Windows Build * VCS: Add full branch name function to rpcs3_version The STRINGIZE macro was a little awkward, and difficult to control at configure time. Since other version information is already included, the full branch name is now added as a function. It's runtime instead of compile-time checking, but it seems worth it. * CI: Overhaul Windows setup script Previously, there was no way of forcing a re-download of cached dependencies when they were replaced by new ones. In addition, there was really no verification of downloads or cache. Now, changing a few lines at the top of the file will automagically force a cache update.
2020-03-27 14:37:27 +01:00
- job: Windows_Build
variables:
COMPILER: msvc
Update Azure config to fix Windows Azure build (#8399) Co-authored-by: Eladash <elad3356p@gmail.com>
2020-06-11 05:14:09 +02:00
QT_VER: '5.14.2'
QT_DATE: '202003291224'
CI: Port Windows build to Azure Pipelines (#7757) * CI: Port Windows build to Azure Pipelines from Appveyor * CI: Split Windows build into scripts * CI: Remove Appveyor * CI: Add GitHub Release deployment to Azure Windows Build * VCS: Add full branch name function to rpcs3_version The STRINGIZE macro was a little awkward, and difficult to control at configure time. Since other version information is already included, the full branch name is now added as a function. It's runtime instead of compile-time checking, but it seems worth it. * CI: Overhaul Windows setup script Previously, there was no way of forcing a re-download of cached dependencies when they were replaced by new ones. In addition, there was really no verification of downloads or cache. Now, changing a few lines at the top of the file will automagically force a cache update.
2020-03-27 14:37:27 +01:00
QTDIR: C:\Qt\$(QT_VER)\msvc2017_64
[CI] Update VulkanSDK to 1.2.135.0
2020-05-07 15:33:43 +02:00
VULKAN_VER: '1.2.135.0'
VULKAN_SDK_SHA: '181b3353612c8b0fc5e1857b652d62140191ae42b98f2f0d532cf349cebfd8c6'
CI: Port Windows build to Azure Pipelines (#7757) * CI: Port Windows build to Azure Pipelines from Appveyor * CI: Split Windows build into scripts * CI: Remove Appveyor * CI: Add GitHub Release deployment to Azure Windows Build * VCS: Add full branch name function to rpcs3_version The STRINGIZE macro was a little awkward, and difficult to control at configure time. Since other version information is already included, the full branch name is now added as a function. It's runtime instead of compile-time checking, but it seems worth it. * CI: Overhaul Windows setup script Previously, there was no way of forcing a re-download of cached dependencies when they were replaced by new ones. In addition, there was really no verification of downloads or cache. Now, changing a few lines at the top of the file will automagically force a cache update.
2020-03-27 14:37:27 +01:00
VULKAN_SDK: C:\VulkanSDK\$(VULKAN_VER)
CACHE_DIR: ./cache
pool:
vmImage: "windows-latest"
steps:
[CI, Cache] Add proper cache versioning (#8285)
2020-05-26 01:33:59 +02:00
- bash: .ci/get_keys-windows.sh
displayName: Get Cache Keys
CI: Update Azure cache task to newer version
2020-03-28 21:13:55 +01:00
- task: Cache@2
CI: Port Windows build to Azure Pipelines (#7757) * CI: Port Windows build to Azure Pipelines from Appveyor * CI: Split Windows build into scripts * CI: Remove Appveyor * CI: Add GitHub Release deployment to Azure Windows Build * VCS: Add full branch name function to rpcs3_version The STRINGIZE macro was a little awkward, and difficult to control at configure time. Since other version information is already included, the full branch name is now added as a function. It's runtime instead of compile-time checking, but it seems worth it. * CI: Overhaul Windows setup script Previously, there was no way of forcing a re-download of cached dependencies when they were replaced by new ones. In addition, there was really no verification of downloads or cache. Now, changing a few lines at the top of the file will automagically force a cache update.
2020-03-27 14:37:27 +01:00
inputs:
[CI, Cache] Add proper cache versioning (#8285)
2020-05-26 01:33:59 +02:00
key: $(Agent.OS) | $(COMPILER) | "$(QT_VER)" | $(VULKAN_SDK_SHA) | llvm.lock | glslang.lock
CI: Port Windows build to Azure Pipelines (#7757) * CI: Port Windows build to Azure Pipelines from Appveyor * CI: Split Windows build into scripts * CI: Remove Appveyor * CI: Add GitHub Release deployment to Azure Windows Build * VCS: Add full branch name function to rpcs3_version The STRINGIZE macro was a little awkward, and difficult to control at configure time. Since other version information is already included, the full branch name is now added as a function. It's runtime instead of compile-time checking, but it seems worth it. * CI: Overhaul Windows setup script Previously, there was no way of forcing a re-download of cached dependencies when they were replaced by new ones. In addition, there was really no verification of downloads or cache. Now, changing a few lines at the top of the file will automagically force a cache update.
2020-03-27 14:37:27 +01:00
path: $(CACHE_DIR)
[CI, Cache] Add proper cache versioning (#8285)
2020-05-26 01:33:59 +02:00
restoreKeys: |
$(Agent.OS) | $(COMPILER)
CI: Port Windows build to Azure Pipelines (#7757) * CI: Port Windows build to Azure Pipelines from Appveyor * CI: Split Windows build into scripts * CI: Remove Appveyor * CI: Add GitHub Release deployment to Azure Windows Build * VCS: Add full branch name function to rpcs3_version The STRINGIZE macro was a little awkward, and difficult to control at configure time. Since other version information is already included, the full branch name is now added as a function. It's runtime instead of compile-time checking, but it seems worth it. * CI: Overhaul Windows setup script Previously, there was no way of forcing a re-download of cached dependencies when they were replaced by new ones. In addition, there was really no verification of downloads or cache. Now, changing a few lines at the top of the file will automagically force a cache update.
2020-03-27 14:37:27 +01:00
displayName: Cache
CI: Maintenance - Rename .travis dir to .ci, since it isn't just for Travis - Convert Linux build scripts to posix sh - Clean up some scripts per shellcheck
2020-04-07 04:53:23 +02:00
- bash: .ci/setup-windows.sh
CI: Port Windows build to Azure Pipelines (#7757) * CI: Port Windows build to Azure Pipelines from Appveyor * CI: Split Windows build into scripts * CI: Remove Appveyor * CI: Add GitHub Release deployment to Azure Windows Build * VCS: Add full branch name function to rpcs3_version The STRINGIZE macro was a little awkward, and difficult to control at configure time. Since other version information is already included, the full branch name is now added as a function. It's runtime instead of compile-time checking, but it seems worth it. * CI: Overhaul Windows setup script Previously, there was no way of forcing a re-download of cached dependencies when they were replaced by new ones. In addition, there was really no verification of downloads or cache. Now, changing a few lines at the top of the file will automagically force a cache update.
2020-03-27 14:37:27 +01:00
displayName: Download and unpack dependencies
CI: Maintenance - Rename .travis dir to .ci, since it isn't just for Travis - Convert Linux build scripts to posix sh - Clean up some scripts per shellcheck
2020-04-07 04:53:23 +02:00
- bash: .ci/export-azure-vars.sh
CI: Add workaround for exporting variables in Azure Using '-x' to echo commands in the shell causes the Azure process commands to be processed twice
2020-03-28 01:19:44 +01:00
displayName: Export Variables
[CI, Windows] build SPIRV-Tools separately
2020-05-23 02:04:58 +02:00
- task: MSBuild@1
inputs:
solution: './Vulkan/spirv-tools-build/spirv-tools-build.vcxproj'
maximumCpuCount: true
platform: x64
configuration: 'Release'
displayName: Compile SPIRV-Tools
CI: Port Windows build to Azure Pipelines (#7757) * CI: Port Windows build to Azure Pipelines from Appveyor * CI: Split Windows build into scripts * CI: Remove Appveyor * CI: Add GitHub Release deployment to Azure Windows Build * VCS: Add full branch name function to rpcs3_version The STRINGIZE macro was a little awkward, and difficult to control at configure time. Since other version information is already included, the full branch name is now added as a function. It's runtime instead of compile-time checking, but it seems worth it. * CI: Overhaul Windows setup script Previously, there was no way of forcing a re-download of cached dependencies when they were replaced by new ones. In addition, there was really no verification of downloads or cache. Now, changing a few lines at the top of the file will automagically force a cache update.
2020-03-27 14:37:27 +01:00
- task: VSBuild@1
inputs:
solution: 'rpcs3.sln'
[CI, Windows] build SPIRV-Tools separately
2020-05-23 02:04:58 +02:00
maximumCpuCount: true
CI: Port Windows build to Azure Pipelines (#7757) * CI: Port Windows build to Azure Pipelines from Appveyor * CI: Split Windows build into scripts * CI: Remove Appveyor * CI: Add GitHub Release deployment to Azure Windows Build * VCS: Add full branch name function to rpcs3_version The STRINGIZE macro was a little awkward, and difficult to control at configure time. Since other version information is already included, the full branch name is now added as a function. It's runtime instead of compile-time checking, but it seems worth it. * CI: Overhaul Windows setup script Previously, there was no way of forcing a re-download of cached dependencies when they were replaced by new ones. In addition, there was really no verification of downloads or cache. Now, changing a few lines at the top of the file will automagically force a cache update.
2020-03-27 14:37:27 +01:00
platform: x64
configuration: 'Release - LLVM'
displayName: Compile RPCS3
CI: Maintenance - Rename .travis dir to .ci, since it isn't just for Travis - Convert Linux build scripts to posix sh - Clean up some scripts per shellcheck
2020-04-07 04:53:23 +02:00
- bash: .ci/deploy-windows.sh
CI: Port Windows build to Azure Pipelines (#7757) * CI: Port Windows build to Azure Pipelines from Appveyor * CI: Split Windows build into scripts * CI: Remove Appveyor * CI: Add GitHub Release deployment to Azure Windows Build * VCS: Add full branch name function to rpcs3_version The STRINGIZE macro was a little awkward, and difficult to control at configure time. Since other version information is already included, the full branch name is now added as a function. It's runtime instead of compile-time checking, but it seems worth it. * CI: Overhaul Windows setup script Previously, there was no way of forcing a re-download of cached dependencies when they were replaced by new ones. In addition, there was really no verification of downloads or cache. Now, changing a few lines at the top of the file will automagically force a cache update.
2020-03-27 14:37:27 +01:00
displayName: Pack up build artifacts
- publish: $(Build.ArtifactStagingDirectory)
Unify Azure artifacts names and produce them only on successful build.
2020-06-08 03:31:12 +02:00
condition: succeeded()
artifact: RPCS3 for Windows
CI: Port Windows build to Azure Pipelines (#7757) * CI: Port Windows build to Azure Pipelines from Appveyor * CI: Split Windows build into scripts * CI: Remove Appveyor * CI: Add GitHub Release deployment to Azure Windows Build * VCS: Add full branch name function to rpcs3_version The STRINGIZE macro was a little awkward, and difficult to control at configure time. Since other version information is already included, the full branch name is now added as a function. It's runtime instead of compile-time checking, but it seems worth it. * CI: Overhaul Windows setup script Previously, there was no way of forcing a re-download of cached dependencies when they were replaced by new ones. In addition, there was really no verification of downloads or cache. Now, changing a few lines at the top of the file will automagically force a cache update.
2020-03-27 14:37:27 +01:00
Manually upload Windows Github Release using curl. Actually fixes #7938 (#8715) For some reason Azure would evaluate the GitHub release instantly and complain about missing/invalid GitHub Release deployment and fail to even start the build, this fixes the issue by just manually uploading it via the GitHub API and curl.
2020-08-15 21:46:53 +02:00
- bash: .ci/github-upload-windows.sh
CI: Avoid trying to publish builds on forks
2020-07-27 18:16:15 +02:00
condition: and(ne(variables['Build.Reason'], 'PullRequest'), eq(variables['Build.Repository.Name'], 'RPCS3/rpcs3'))
CI: Port Windows build to Azure Pipelines (#7757) * CI: Port Windows build to Azure Pipelines from Appveyor * CI: Split Windows build into scripts * CI: Remove Appveyor * CI: Add GitHub Release deployment to Azure Windows Build * VCS: Add full branch name function to rpcs3_version The STRINGIZE macro was a little awkward, and difficult to control at configure time. Since other version information is already included, the full branch name is now added as a function. It's runtime instead of compile-time checking, but it seems worth it. * CI: Overhaul Windows setup script Previously, there was no way of forcing a re-download of cached dependencies when they were replaced by new ones. In addition, there was really no verification of downloads or cache. Now, changing a few lines at the top of the file will automagically force a cache update.
2020-03-27 14:37:27 +01:00
displayName: Push build to GitHub
Manually upload Windows Github Release using curl. Actually fixes #7938 (#8715) For some reason Azure would evaluate the GitHub release instantly and complain about missing/invalid GitHub Release deployment and fail to even start the build, this fixes the issue by just manually uploading it via the GitHub API and curl.
2020-08-15 21:46:53 +02:00
env:
RPCS3_TOKEN: $(RPCS3-Token)
Reference in New Issue Copy Permalink