Implement Windows release builds in Azure Pipelines #14065
Conversation
|
Side question. I've tried to search using google and azure pipelines documentation site embedded searcher but found nothing |
|
@asvetlov It's totally customizable. We have multiple build definitions configured for this repo - one using If you use |
|
You should be able to see all the builds at https://dev.azure.com/python/cpython/_build I also have a few manually created ones for building the OpenSSL and libffi bits that we use. |
|
Thanks @zooba for the PR 🌮🎉.. I'm working now to backport this PR to: 3.8. |
|
Sorry @zooba, I had trouble checking out the |
|
GH-14085 is a backport of this pull request to the 3.8 branch. |
|
@zooba thanks. |
Includes backported fixes from GH-14091
| $(PySourcePath)PC\crtlicense.txt; | ||
| $(bz2Dir)LICENSE; | ||
| $(opensslOutDir)LICENSE; | ||
| $(tcltkDir)tcllicense.terms; |
There was a problem hiding this comment.
@zooba This change breaks building with --no-tkinter. Which breaks the Windows arm32 buildbot
This automates most of the Windows Release build in a single (multi-stage) Azure Pipelines job.
You can see a sample run at https://dev.azure.com/python/cpython/_build/results?buildId=45280&view=results
It still requires my custom build machine to be running, but only when
SigningCertificateis set. Without this, and withoutUsePGO, it should all run on hosted machines.The final publish steps are currently not implemented, as they weren't previously anyway (other than Nuget). I expect to leave them unimplemented for now, and just won't use them, but eventually may come around to automating it the whole way through.
Once you get past the .yml files, there are actual changes to the build files. I found it convenient to generate more files at build (e.g.
LICENSE.txt) rather than doing it as part of setup. There shouldn't be anything dramatic in here, and it obviously all works with the release build process or I wouldn't be posting yet :)