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

Decide on a continuous integration (CI) system. #3

Open
deanberris opened this issue Jan 11, 2019 · 10 comments
Open

Decide on a continuous integration (CI) system. #3

deanberris opened this issue Jan 11, 2019 · 10 comments
Labels
help wanted Extra attention is needed

Comments

@deanberris
Copy link
Member

Pick one of:

  • Travis
  • CircleCI
  • Google Cloud Build
  • Something Else

for the CI system.

@deanberris deanberris added the help wanted Extra attention is needed label Jan 11, 2019
@glynos
Copy link
Member

glynos commented Jan 11, 2019

Another candidate might be AppVeyor:

https://www.appveyor.com/

@deanberris
Copy link
Member Author

Thanks -- though I don't see macOS support in the AppVeyor docs, which Travis and CircleCI have, but I don't see Windows in either Travis nor CircleCI. 😕

The worst case scenario here might be that we use one for Linux/macOS build/testing/deployment and one for Windows. Looks like AppVeyor is the only one that supports Windows from this list.

How hard would that be to set-up?

@glynos
Copy link
Member

glynos commented Jan 18, 2019

I used AppVeyor for CI builds with the URL library for Windows, and it was as easy as Travis to set up.

I felt that using a combination of Travis and AppVeyor gave me important feedback and helped me catch cross-platform bugs as soon as I had committed, and I felt that the overhead (admittedly on a small library) was not a lot given the benefit.

@brown2rl
Copy link

Where do you all want to set up the CI server? Looks like between USA, Australia, and Belgium might be somewhere in east Asia like Russia, Philippines, or Japan.

@deanberris
Copy link
Member Author

We use the free CI automation runners that the CI providers allow open source projects to use, if we can help it. These are run on public clouds and don't need to be hosted in a specific region. Was there a specific concern ypu had, @brown2rl on the location of the CI server(s)?

@brown2rl
Copy link

No, thanks. Looks like it's Travis + AppVeyor, if you've had success with that.

@brown2rl
Copy link

I attempted to set up Travis + AppVeyor, however it's a job for the repo owner or organization member. Would I be able to to be added to the organization? Or can we make a new one! Thanks!

@glynos
Copy link
Member

glynos commented Jan 28, 2019

@brown2rl I have configured Travis, AppVeyor and CircleCI for the cpp-netlib/netlib repo.

@deanberris Let me know if I still need to provide access for any of these, if you can't access them.

@brown2rl
Copy link

@glynos great job!

@AngleNet
Copy link

AngleNet commented Jun 6, 2019

Maybe we should integrate tester, linter to CI? If it is not done yet, I can help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

4 participants