-
Notifications
You must be signed in to change notification settings - Fork 8.4k
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
move version to vs2019, the 1903 sdk, and the 14.2 build tools. #1012
Conversation
WELP. Looks like the 2019 hosted pool doesn't have the 1903 SDK yet either... |
I ran this locally on my machine after I saw that it failed the pipeline as the pipeline doesn’t have the v142 tool kit and the build was a success! I downloaded the zip from this Archive and set it up just as mentioned in #489 as #565 only worked the first build then failed afterwards. In this attempt I specifically retargeted the build to the 10.0.18362.0 SDK and checked the toolkit to make sure it was targeted to v142 despite knowing it is now predefined in the code. I let it run and it came back with a few warnings that are all common in the other pipeline builds but not of massive concern as the build did succeed. I certainly do hope to see this solution work for others. Keep up the great work! |
18362 is coming... https://github.com/microsoft/azure-pipelines-image-generation/pull/953 |
If there ever was a pipeline that's in dire need of azure devops build cache save/restore tasks, this one is it. Apparently these things are real, and coming pretty soon. |
Say what now? Can you provide a link to this? @oising |
@miniksa Looks like it's available for testing for internal orgs: microsoft/azure-pipelines-yaml#113 |
@andersosthus, thanks. We're not operating as an internal org right now, so I'll probably wait on this like the rest of everyone in the public. |
I'm going to tee this up again now that all our dependencies have merged. |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
any update on this? What are the next steps to have this merged? |
We're waiting on the 18362 SDK to be deployed to the Azure DevOps tenant from which we're running our CI builds. |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
…osoft#1012) * move version to vs2019, the 1903 sdk, and the 14.2 build tools.
…osoft#1012) * move version to vs2019, the 1903 sdk, and the 14.2 build tools.
Summary of the Pull Request
Moves the solution to VS2019 and the latest SDK/tools
PR Checklist
Detailed Description of the Pull Request / Additional comments
This is sitting here until we figure out what to do with the build agents regarding versioning and signing.