Skip to content
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.

Move CI to Azure Pipelines #1740

Merged
merged 73 commits into from
Nov 11, 2018
Merged

Move CI to Azure Pipelines #1740

merged 73 commits into from
Nov 11, 2018

Conversation

daviwil
Copy link
Contributor

@daviwil daviwil commented Oct 10, 2018

Description of the Change

Trying out Azure DevOps Pipelines for the GitHub package!

Remaining

  • Run tests on Linux, macOS, and Windows
  • Publish test results
  • Fail the check when the test step fails, but still publish test results
  • Lint in an independent job
  • Test snapshot in an independent job
  • Fix the Windows build failures
  • Implement a build matrix of Atom versions within each platform
  • Refactor common elements out of builds
  • Determine whether or not this addresses "WorkerManager when the manager process is destroyed destroys all the renderer processes..." #1688
  • Move to our own, independent Azure DevOps account, so we don't clobber the queue for Electron and Atom (and vice versa)
  • Set up the GitHub app on this repository for Checks goodness
  • Replace build badges in the README with an Azure Pipelines badge
  • Remove other build YAML configuration and scripts
  • Restore Coveralls integration
  • Deactivate other build integrations

@coveralls
Copy link

coveralls commented Oct 10, 2018

Coverage Status

Coverage increased (+0.6%) to 85.528% when pulling 2bc7531 on try-vsts-ci into 26c39ee on master.

@smashwilson smashwilson changed the title Create .vsts.yml Move CI to Azure Pipelines Nov 10, 2018
@smashwilson
Copy link
Contributor

🚋 choo choo

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants