New submission from Steve Dower <steve.do...@python.org>:
Azure Pipelines can now support container jobs: https://docs.microsoft.com/en-us/azure/devops/pipelines/process/container-phases?view=vsts&tabs=yaml I experimented with enabling a manylinux1 build a while back, which should now be able to use identical steps to the POSIX build. With the new syntax, we can enable CI (and perhaps PR?) builds using the snippet below: - job: ManyLinux1_CI_Tests displayName: ManyLinux1 CI Tests dependsOn: Prebuild condition: | and( and( succeeded(), eq(variables['manylinux'], 'true') ), eq(dependencies.Prebuild.outputs['tests.run'], 'true') ) resources: containers: - container: manylinux1 image: dockcross:manylinux-x64 pool: vmImage: ubuntu-16.04 container: manylinux1 variables: testRunTitle: '$(build.sourceBranchName)-manylinux1' testRunPlatform: manylinux1 steps: - template: ./posix-steps.yml I don't have time right now to test this change, but someone else might. It's certainly going to be easier for someone to test it by adding this to the PR build first (or set up a build on your own Pipelines instance). Maybe there are other more relevant containers we should be testing in? ---------- components: Cross-Build messages: 333209 nosy: Alex.Willmer, barry, steve.dower, zach.ware priority: normal severity: normal status: open title: Enable manylinux1 builds on Pipelines versions: Python 3.7, Python 3.8 _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue35683> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
