Skip to content

Set up CI with Azure Pipelines#2

Merged
Edilmo merged 8 commits intomasterfrom
ms/ado
Feb 25, 2020
Merged

Set up CI with Azure Pipelines#2
Edilmo merged 8 commits intomasterfrom
ms/ado

Conversation

@Edilmo
Copy link

@Edilmo Edilmo commented Jan 27, 2020

This PR contains the minimal CI required to work with this repo in Azure DevOps.
The main idea behind this initial step is the following: let's start with a CI as closer as possible to the CI in upstream, and improve or adapt on top of that taking advantage of all the features that Azure Pipelines offer.

Several task has been deferred:

  • Public PR to move to Bazel 2.0: the two files that are modified out of the folder ci/azure-pipelines, are related to the support of Bazel 2.0, which is the version used by the CI added by this PR.
  • Streaming related tests are not integrated yet.
  • Bazel Remote Cache.
  • Parallelization of jobs: currently there is one very long job that concentrates all the integration and performance tests of RLlib, Tune and others. This could be easily split in the near future.
  • Performance considerations in Microsoft-hosted machines: there is a small change in a threshold that was necessary because a random sampling implementation was performing a little bit poor in Microsoft-hosted Ubuntu.
  • Tune related tests are disabled: there is incompatibility issue with PyTorch.
  • Large memory tests are disabled: the current pool has not enough memory.
  • And more...

The missing parts mention above and others will be added in incremental fashion.

@Edilmo Edilmo force-pushed the ms/ado branch 14 times, most recently from 999eb2a to 6e5492c Compare January 30, 2020 08:41
Specifically, we are setting a
travis like ADO pipeline following
what is already present in the .travis.yml
file in the root of the repo.
@Edilmo Edilmo force-pushed the ms/ado branch 15 times, most recently from 4814cf8 to 329d826 Compare February 3, 2020 04:35
@Edilmo Edilmo force-pushed the ms/ado branch 9 times, most recently from ea4c8a8 to e0c5c4e Compare February 8, 2020 00:33
@Edilmo Edilmo force-pushed the ms/ado branch 8 times, most recently from 35e274c to c60ac40 Compare February 19, 2020 16:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants