[PATCH 01/13] ci: also run linux-gcc pipeline with python-3.7 environment

From: Yang Zhao <yang.zhao@skyboxlabs.com>
Date: Dec 7, 2019, 00:33 UTC
Message-ID: <20191207003333.3228-2-yang.zhao@skyboxlabs.com>
In-Reply-To: <20191207003333.3228-1-yang.zhao@skyboxlabs.com>

git-p4.py includes support for python-3, but this was not previously validated in CI. Lets actually do that.

There is no tangible benefit to repeating python-3 tests for all environments, so only limit it to linux-gcc for now.

Signed-off-by: Yang Zhao <yang.zhao@skyboxlabs.com>
---

I assert that we don't need to run python3 tests on more platforms, but is this actually reasonable?

 azure-pipelines.yml | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/azure-pipelines.yml b/azure-pipelines.yml
index 37ed7e06c6..d5f9413248 100644
--- a/azure-pipelines.yml
+++ b/azure-pipelines.yml
@@ -331,7 +331,18 @@ jobs:
   displayName: linux-gcc
   condition: succeeded()
   pool: Hosted Ubuntu 1604
+  strategy:
+    matrix:
+      python27:
+        python.version: '2.7'
+      python37:
+        python.version: '3.7'
   steps:
+  - task: UsePythonVersion@0
+    inputs:
+      versionSpec: '$(python.version)'
+  - bash: |
+      echo "##vso[task.setvariable variable=python_path]$(which python)"
   - bash: |
        test "$GITFILESHAREPWD" = '$(gitfileshare.pwd)' || ci/mount-fileshare.sh //gitfileshare.file.core.windows.net/test-cache gitfileshare "$GITFILESHAREPWD" "$HOME/test-cache" || exit 1

-- 
2.21.0.windows.1