Skip to content

Latest commit

 

History

History
84 lines (57 loc) · 4.18 KB

pullrequest-builds.md

File metadata and controls

84 lines (57 loc) · 4.18 KB

Pull Request Builds

As part of our Pull Requests we have some validation builds where we build the product and run tests on different Operating Systems and Build Configurations.

Build Matrix

Build Framework Builds Tests Runs Tests
Windows x86_Release netcoreapp X X
Windows x64_Debug netcoreapp X X
Windows NETFX_x86_Release netfx X X
Linux x64_Release netcoreapp X X
Linux arm64_Release netcoreapp X X
Linux arm_Release netcoreapp X
Linux musl_x64_Debug netcoreapp X
MacOS x64_Debug netcoreapp X X
Packaging All Configurations x64_Debug all X X

Our build definitions are defined by some .yml files with the following structure:

  • Entrypoint .azure-pipelines.yml
  • Shared build steps eng/pipelines/corefx-base.yml
  • Helix step eng/pipelines/helix.yml
  • Windows Matrix eng/pipelines/windows.yml
  • Linux Matrix eng/pipelines/linux.yml
  • MacOS Matrix eng/pipelines/macos.yml

Available builds

  • corefx-ci (Runs by default on every commit)
  • corefx-outerloop-linux
  • corefx-outerloop-osx
  • corefx-outerloop-windows

Azure pipelines commands

/azp help (displays help message)
/azp run (runs all builds listed above)
/azp run <build name> (/azp run corefx-outerloop-linux)

/azp is a shortcut for /AzurePipelines which can be used as well.

In order to use comment triggers, at the moment you need to be a Collaborator or Member of the repo.

How to look at a build failure

First, you need to click in the details button on the right hand side of the build you're interested in looking at. That will redirect you to the Checks tab within that PR, which will have a summary of that build.

To get to the actual build, you will need an extra step here. You have two options:

  1. Click on View more details on Azure Pipelines:
  2. Click on errors / warnings summary hyperlink.

Once in the build UI you can look at a specific job, or step log, by clicking on them directly.

How to look at a test failure

Use the Azure DevOps Test Explorer which lists all tests grouped by the different build configurations. You can filter and navigate through the results and look at stack traces, and detailed logs.

How to rerun builds

In order to rerun a build, it can be done through comments, the checks tab through the rerun button, or in the build UI on the right top corner, under the ... submenu you will find a retry button.

Unfortunately, rerun button on checks tab and retry button in build's UI are only available for contributors that are part of the Microsoft organization.

Access a build binlog

We publish binlogs as part of our PR builds to make weird build errors easier to diagnose. In order to find these, you can find them via the build UI:

  1. If the build is still running, you can click on the ... submenu and there will be an Artifacts entry.
  2. If the build is done, on the top right corner, there will be a big blue button called Artifacts.

Once you click under the Artifacts section, a popup will show, with multiple directories, one for each build leg. Under this directory, you will find every binlog produced as part of the build.

Known Issues

  1. Multiline comments are not supported, so if you want to trigger multiple builds, you have to do it on separate comments. Also, everything after /azp run is considered the build name, so a comment trigger can't have anything after it. See a real example.
  2. Feature request: trigger multiple builds with one /azp call. I.e /azp run corefx-ci, corefx-outerloop-osx.
  3. Feature request: /azp help doesn't list available builds for the repo.
  4. Only an entire pipeline can be triggered through comments, triggering a single leg is not supported yet. /azp run corefx-ci (macOS x64_Debug) wouldn't work.
  5. Rerunning a single leg while others are still running is not yet supported, you have to wait for all legs to finish before retrying an individual leg.

All of this issues have been raised to Azure DevOps teams, expect @safern, to update the docs through PR to widely communicate new features coming.