Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SPIKE] [CI] Azure Pipelines #1752

Closed
10 tasks
virkt25 opened this issue Sep 24, 2018 · 4 comments
Closed
10 tasks

[SPIKE] [CI] Azure Pipelines #1752

virkt25 opened this issue Sep 24, 2018 · 4 comments
Labels
Internal Tooling Issues related to our tooling and monorepo infrastructore spike stale

Comments

@virkt25
Copy link
Contributor

virkt25 commented Sep 24, 2018

Description / Steps to reproduce / Feature proposal

See https://github.com/marketplace/azure-pipelines

Azure Pipelines offers 10 parallel builds for Open Source Projects and offers the capability of being the one-stop shop for testing on Linux, macOS, Windows (vs. the current setup of Travis + AppVeyor (so slow ... ugh)).

The purpose of this spike is to investigate the feasibility of testing the feasibility of switching to Azure Pipelines. I would propose the plan be to add the integration but not make it a required check. This will allow these builds to run alongside the current setup and we can see if it's faster / slower / other issues etc. Let this run against the repo for 30-days and then have a spike results meeting to discuss with the team what they noticed with Azure vs. the current setup (speed, reliability, etc). Make a decision to proceed with keeping it or not. If keeping it / switching to it as the default -- make it a required check, remove Travis, AppVeyor.

Spike Criteria

  • Add Azure Pipelines to this repository (must be done by the org owner)
  • Configure it to run out Linting (on Linux) + Tests (on all 3 platforms + Node 8, 10)
  • Ensure pipeline is hooked into GitHub PR Status API but is not a required check.
  • Let it run for 30 days for monitoring while the team observes speed, reliability, etc.
  • Have a spike meeting to discuss team observations and to decide if this should be adopted in place of the current CI pipelines we have
  • Document outcome (adopted / rejected) on this ticket as results of the spike for the community to know our reason for the switch

IF ADOPTED

  • Make the check required on GitHub PRs
  • Remove Travis + AppVeyor
  • Blog

IF REJECTED

  • Remove Azure Pipelines optional check from the repo
@kaylangan
Copy link

I'm a Program Manager for Azure Pipelines. Let me know if you have any questions or suggestions. I'm happy to help!

@bajtos
Copy link
Member

bajtos commented Oct 3, 2018

The TypeScript project seem to have a reasonably complex pipeline configuration including "nightly publish", it may be a good source of inspiration for our setup.

https://typescript.visualstudio.com/TypeScript/_build

@dhmlau dhmlau added spike Internal Tooling Issues related to our tooling and monorepo infrastructore labels Jun 14, 2019
@stale
Copy link

stale bot commented Jun 9, 2020

This issue has been marked stale because it has not seen activity within six months. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository. This issue will be closed within 30 days of being stale.

@stale stale bot added the stale label Jun 9, 2020
@stale
Copy link

stale bot commented Jul 11, 2020

This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository.

@stale stale bot closed this as completed Jul 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Internal Tooling Issues related to our tooling and monorepo infrastructore spike stale
Projects
None yet
Development

No branches or pull requests

4 participants