CI: Remove extraneous toolchain job from Azure CI

This was useful when building both i686 and x86_64 SerenityOS targets as we could use a single toolchain build for both targets. But now all this extra job does is create the opportunity for the toolchain to need to be built twice (i.e. if the pipelines are backed up and the toolchain cache is busted between these jobs while the x86_64 step is waiting for a VM).
cubiclove · Dec 28, 2022 · 0a7d036 · 0a7d036
1 parent 598fcfc
commit 0a7d036
Show file tree

Hide file tree

Showing 3 changed files with 2 additions and 42 deletions.
diff --git a/Meta/Azure/Serenity.yml b/Meta/Azure/Serenity.yml
@@ -33,7 +33,7 @@ jobs:
  serenity_ccache_path: '$(SERENITY_CCACHE_DIR)'
 
  - script: ./Toolchain/BuildClang.sh --ci
- displayName: Extract Toolchain
+ displayName: Build Toolchain
  env:
  TRY_USE_LOCAL_TOOLCHAIN: 'y'
 

diff --git a/Meta/Azure/Toolchain.yml b/Meta/Azure/Toolchain.yml
diff --git a/azure-pipelines.yml b/azure-pipelines.yml
@@ -23,14 +23,8 @@ stages:
  parameters:
  os: 'macOS'
 
- - stage: Toolchain
- dependsOn: []
-
- jobs:
- - template: Meta/Azure/Toolchain.yml
-
  - stage: SerenityOS
- dependsOn: Toolchain
+ dependsOn: []
 
  jobs:
  - template: Meta/Azure/Serenity.yml