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

Switch from AppVeyor and Wercker to CirrusCI #1718

Closed
jen20 opened this issue Sep 1, 2018 · 2 comments
Closed

Switch from AppVeyor and Wercker to CirrusCI #1718

jen20 opened this issue Sep 1, 2018 · 2 comments
Assignees
Labels
area/build Issues relating to the build system detectability/easy Negative impact will be easily detected impact/low Low prospect of negative impact kind/enhancement Issues which are a new feature

Comments

@jen20
Copy link
Contributor

jen20 commented Sep 1, 2018

Neither AppVeyor or Wercker are doing what we need right now (although Wercker is closer). We intend to move to Cirrus CI, which is a managed service which allows both Windows and Linux containers, and to transition our Linux builds to a distribution with the oldest version of glibc that we care about - CentOS 7.

This will take some effort to get working, so right now, _there is no CI system hooked up for either master or for pull requests.

We are working on the new-project-format branch to get everything going again, and will close out this thread when things are good.

This is related work for #1716, but has wider benefits too.

Until this is complete, no other pull requests are being merged to master unless they are part of an SLA-backed commercial request, where other testing will be carried out.

@jen20 jen20 added kind/enhancement Issues which are a new feature tracking/In Progress impact/low Low prospect of negative impact detectability/easy Negative impact will be easily detected area/build Issues relating to the build system labels Sep 1, 2018
@jageall
Copy link
Contributor

jageall commented Dec 10, 2018

@jen20 is this issue still valid as we are on pipelines for all platforms now?

@shaan1337
Copy link
Member

@jageall thank you, we can close it. This was merged through #1710.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/build Issues relating to the build system detectability/easy Negative impact will be easily detected impact/low Low prospect of negative impact kind/enhancement Issues which are a new feature
Projects
None yet
Development

No branches or pull requests

3 participants