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

Travis-CI: Request for help #289

Closed
4 tasks
rw opened this issue Oct 8, 2015 · 5 comments
Closed
4 tasks

Travis-CI: Request for help #289

rw opened this issue Oct 8, 2015 · 5 comments

Comments

@rw
Copy link
Collaborator

rw commented Oct 8, 2015

We use Travis CI to test code at check-in. However, right now it only tests the FlatBuffers C++ code.

I'd like help configuring our .travis.yml file to test the following ports:

  • Java
  • C#
  • Go
  • Python

As a bonus, testing each port on 32bit and 64bit machines, and different OS'es, would be useful.

@ghost
Copy link

ghost commented Oct 9, 2015

Great idea, this is long overdue.
What software does this all need that Travis doesn't come with by default?
Can we start with a test_all.sh that combines the existing tests?

@Thomasdezeeuw
Copy link

This could be travis file for Go:

sudo: false
language: go
go:
  - 1.3
  - 1.4
  - 1.5
  - tip

I should note that I haven't tested flatbuffers with older versions of Go.

@xplicit
Copy link

xplicit commented Oct 22, 2015

For CS you can look at the travis configuration for ms bond serializer. It uses various languages (cs, c++, etc) https://github.com/Microsoft/bond/blob/master/.travis.yml

If you don't want to use "csharp" language definition in travis.yml file, you can use any other language and install mono prerequisites manually.

Here the sample how It can be done for OSX:
https://github.com/xplicit/bond/blob/travis2/.travis.yml

Here the sample how it can be done for Linux:
https://github.com/xplicit/HyperFastCgi/blob/2f92e4d1a0a87927c1c022176e9b4be45a0eb1ec/.travis.yml

@rw
Copy link
Collaborator Author

rw commented Oct 30, 2015

I also wrote about this in an existing Travis issue: travis-ci/travis-ci#4090 (comment)

@ghost
Copy link

ghost commented Aug 14, 2017

These languages are now all tested by our AppVeyor CI. And since they're not as platform-sensitive as C++, testing them also in Travis would be nice to have but not strictly necessary.

@ghost ghost closed this as completed Aug 14, 2017
This issue was closed.
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