-
Notifications
You must be signed in to change notification settings - Fork 362
update CI to build vcpkg dependencies in separate stage #821
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: latestw_all
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR refactors the CI pipeline to build vcpkg dependencies in a separate stage before the main build, addressing timeout issues when CodeQL is enabled.
Key Changes
- Introduces a new
BuildDependenciesstage that installs vcpkg dependencies for both x64 and x86 architectures in parallel - Uploads vcpkg dependencies as pipeline artifacts for reuse in the build stage
- Modifies the build jobs to download pre-built dependencies instead of building them during compilation
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
.azdo/templates/install-vcpkg-dependencies.yml |
New template that verifies LibreSSL versions, installs and bootstraps vcpkg, builds dependencies for a specified triplet, and uploads them as artifacts |
.azdo/templates/build-win32-openssh-job.yml |
Updated to accept a dependenciesArtifactName parameter and download pre-built dependencies instead of building them inline |
.azdo/ci.yml |
Added BuildDependencies stage with jobs for x64 and x86, and configured the Build stage to depend on it |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
PR Summary
PR Context