path: root/.azure-pipelines.yml
AgeCommit message (Collapse)AuthorFilesLines
2020-03-09Azure/Travis: Re-sync jobs and clarify exclusionsTom Rini1-3/+3
We keep both of these jobs in sync as much as possible even when the primary motivation is to keep Travis from exceeding the build time limit there. With that in mind: - Use "rk" not "rockchip" to get all Rockchip SoC platforms in one job, rather than just all Rockchip vendor platforms. - The NXP LX216* SoCs have their own job, exclude them from the AArch64 generic job. - SoCFPGA SoCs have their own job, exclude them from the AArch64 generic job. Signed-off-by: Tom Rini <>
2020-02-25azure: build HTML documentationHeinrich Schuchardt1-0/+10
Several patches delivered incorrect restructured text as documentation. We should be able to discover this in Azure CI. Provide a build step for 'make htmldocs'. Signed-off-by: Heinrich Schuchardt <> Reviewed-by: Bin Meng <>
2020-02-24Azure / GitLab: Update Docker imageTom Rini1-1/+1
Bring in a newer Docker image to build on that has everything required for running 'make htmldocs'. Signed-off-by: Tom Rini <>
2020-02-13travis/gitlab/azure: Ensure we use python3 alwaysTom Rini1-1/+1
When running our tests there are some cases where as part of the Python 2.7 to Python 3.6 migration we didn't force Python 3.6 to be used as everything wasn't yet migrated. Now that everything is, make sure to tell virtualenv to use python3. In the case of Travis this is best done by making the tools test happen after the main tests so that it will already have been run in all cases, TEST_PY_TOOLS is a subset of TEST_PY_BD. Signed-off-by: Tom Rini <>
2020-02-07azure/gitlab: Update to Docker to have SDL2 availableTom Rini1-1/+1
Update to a newer Docker image that contains SDL2 libraries as required by recent Sandbox changes. Signed-off-by: Tom Rini <>
2020-02-07azure: Use our own GRUB binariesTom Rini1-5/+4
Use the same logic from 24df1b14f3ab to use our own GRUB binaries in Azure pipelines as well. Signed-off-by: Tom Rini <>
2020-02-04azure: Move to vs2017-win2016 platform build hostTom Rini1-1/+1
Azure is moving to remove the vs2015-win2012r2 platform build host. The two suggested new platforms to use are vs2017-win2016 and windows-2019. For now, move up to vs2017-win2016. Cc: Bin Meng <> Signed-off-by: Tom Rini <> Reviewed-by: Bin Meng <> Tested-by: Bin Meng <>
2020-01-20gitlab/azure: Update to latest container tagTom Rini1-1/+1
- Based on bionic-20200112 tag from Ubuntu - Add graphviz (Heinrich) Signed-off-by: Tom Rini <>
2020-01-10gitlab/azure: Update to latest containerTom Rini1-1/+1
- Updated base snapshot - QEMU v4.2.0 Signed-off-by: Tom Rini <>
2019-11-23travis: rework NXP layerscape jobsHeiko Schocher1-13/+13
remove from NXP arm32 all layerscape boards and build them instead in already existing layerscape jobs (which now not only build aarch64 boards) Signed-off-by: Heiko Schocher <>
2019-11-06gitlab/azure: Enable LLVM testsTom Rini1-0/+5
Now that we have again fixed the problems that building with clang exposes, enable these tests on Azure and GitLab-CI as well. Signed-off-by: Tom Rini <>
2019-11-01azure: Update the script to prepend PATH not override PATHTom Rini1-1/+1
Similar to 90d3d78a1c68 ("gitlab-ci: Prepend to PATH rather than replace it") we need to prepend the PATH with our additional binaries and not replace the value fully as doing so breaks virtualenv. Signed-off-by: Tom Rini <>
2019-10-31azure: Update for python3 and current pytestTom Rini1-6/+4
Similar to the rework for GitLab-CI and Travis-CI, rework the Azure Pipeline to use python3 and requirements.txt to install the necessary modules. Signed-off-by: Tom Rini <>
2019-10-29Bring all testings in gitlab and travis CI to Azure PipelinesBin Meng1-0/+382
This expands current Azure Pipelines Windows host tools build testing to cover all the CI testing in gitlab and travis CI. Note for some unknown reason, the 'container' cannot be used for any jobs that have buildman, for buildman does not exit properly and hangs the job forever. As a workaround, we manually call docker to run the image to perform the CI tasks. A complete run on Azure Pipelines takes about 2 hours and 10 minutes. Signed-off-by: Bin Meng <>
2019-10-28Add Microsoft Azure Pipelines configurationBin Meng1-0/+38
Microsoft Azure Pipelines [1] provides unlimited CI/CD minutes and 10 parallel jobs to every open source project for free. This adds a configuration file for Azure Pipelines to utilize the free Windows VM hosted by Microsoft to ensure no build broken in building U-Boot host tools for Windows. [1] Signed-off-by: Bin Meng <>