Use mbed-tools deploy

The latest `mbed-tools deploy` automatically uses the shallowest clone
possible. It has the advantage of fetching the version in mbed-os.lib,
compared to a hardcoded `git clone` in `.travis.yml` which fetches the
latest `master` branch of Mbed OS.

Author: LDong-Arm

.circleci/config.yml

@@ -22,7 +22,7 @@ jobs:
           apt-get update -y
           apt-get install -y cmake srecord ninja-build # TF-M dependencies
           cd mbed-os-tf-m-regression-tests
-          git clone --depth=1 --single-branch https://github.com/ARMmbed/mbed-os.git
+          mbed-tools deploy
       - compile:
           target: "ARM_MUSCA_S1"
       - compile:

.travis.yml

@@ -72,10 +72,9 @@ matrix:
         - sudo ln -s $(which ccache) bin/arm-none-eabi-gcc
         - sudo ln -s $(which ccache) bin/arm-none-eabi-g++
         - export PATH="$(pwd)/bin:$PATH"
-        # Fetch mbed-os: We use manual clone, with depth=1 and --single-branch to save time.
-        - git clone --depth=1 --single-branch https://github.com/ARMmbed/mbed-os.git
         # Install Mbed CLI and dependencies
         - pip install --upgrade mbed-tools
+        - mbed-tools deploy
         - pip install -r mbed-os/requirements.txt
       script:
         # Build TF-M and all tests