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

Continuous Delivery/integration #21

Open
bryanhuntesl-lowpriv opened this issue Oct 6, 2017 · 2 comments
Open

Continuous Delivery/integration #21

bryanhuntesl-lowpriv opened this issue Oct 6, 2017 · 2 comments

Comments

@bryanhuntesl-lowpriv
Copy link

bryanhuntesl-lowpriv commented Oct 6, 2017

I want to get travis, circleci, codeship or anything else (within reason) up and running and generating Riak rpm/debs.

I don't have write access to any basho repositories to put the appropriate .travis.yml , .codeship.yml, .circleci.yml or whatever into the root of each repository.

In the meantime I've forked everything to the postbasho organisation. Thoughts anyone?

@pjaclark
Copy link
Contributor

pjaclark commented Oct 6, 2017

Decisions from 2017-10-06:

  • no negative comments on Travis CI
  • raise at Riak roadmap meeting next week

@Licenser
Copy link
Contributor

Licenser commented Oct 7, 2017

gitlabci has some features that can be rather helpful, not sure if they work w/o gitlab however (so it might be a no-go). But it'd allow us to set up an EQC capable host and/or custom OS's I've not see that with travis or circleci.

Travis (for OSS) can have some problems with larger tests suites their runners are incredibly slow and throttle you on even medium load anything beyond trivial unit tests might just time out.

Disclaimer: I have a love/hate relationship w/ gitlab

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

No branches or pull requests

3 participants