Author steve.dower
Recipients Alex.Willmer, barry, steve.dower, zach.ware
Date 2019-01-08.04:19:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1546921151.97.0.533946172892.issue35683@roundup.psfhosted.org>
In-reply-to
Content
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?
History
Date User Action Args
2019-01-08 04:19:15steve.dowersetrecipients: + steve.dower, barry, zach.ware, Alex.Willmer
2019-01-08 04:19:11steve.dowersetmessageid: <1546921151.97.0.533946172892.issue35683@roundup.psfhosted.org>
2019-01-08 04:19:11steve.dowerlinkissue35683 messages
2019-01-08 04:19:11steve.dowercreate