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

Integrate with travis-ci #33

Closed
gamedevsam opened this issue Feb 11, 2014 · 7 comments
Closed

Integrate with travis-ci #33

gamedevsam opened this issue Feb 11, 2014 · 7 comments

Comments

@gamedevsam
Copy link
Contributor

Travis provides continuous build support (including pull requests). This would let us know if a pull request would cause a compiler error.

https://travis-ci.org/

@caitp
Copy link

caitp commented Feb 11, 2014

+1for CI

@reduz
Copy link
Member

reduz commented Feb 11, 2014

I'm not quite sure I understand what travis-ci is, I kind of understand that it's a platform for continuous integration, but I'm not sure which tagrets can compile. Right now I'm using jenkins at my office server to make the builds at night, and having it configured so it does builds for android, html5 bb10, etc is quite a lot of work. Maybe it could be used for the 32 bits linux binary :P

@gamedevsam
Copy link
Contributor Author

Travis uses virtualized linux boxes to do the integrations, so I think compiling the 32 bit linux binary is about as far as we could get. I still think that would be useful though.

@caitp
Copy link

caitp commented Feb 11, 2014

I recall they were adding VMs for other platforms in the soon-ish future, although these are probably not available free of charge. But open source projects can take advantage of linux containers at no cost, so that's nice.

An alternative solution could be Jenkins CI alongside Leeroy for github integration, which would allow more flexibility in the target systems

@bdero
Copy link
Contributor

bdero commented Jan 19, 2015

@reduz I was about to suggest the use of Travis for per-commit builds, but if you're using Jenkins, that's great, too.

An uprising practice is to run full build and test suite jobs against every commit on every pull request for automated integration into the code review process.

Notice how edX does it: https://github.com/edx/edx-platform/pull/6609
Next to each commit, there's an icon indicating the build status:
Build status

Clicking it takes the user to the build report to pinpoint test/build failures:
Build report

Of course, building Godot for all platforms on every push might be intense on compute time. The bright side is that, since Godot has surprisingly few dependencies, build configuration is probably quite a bit simpler than it could be.

@erbridge
Copy link
Contributor

Looks like Travis is already set up to do the Linux build. There's a .travis.yml file which looks like it's set up correctly to me. It only needs to be turned on.

@leonkrause
Copy link
Contributor

The discussion about continuous integration is continued in #1553.

@akien-mga akien-mga removed this from the Later milestone Nov 20, 2015
hungrymonkey referenced this issue in hungrymonkey/godot Sep 30, 2017
…eration_for_enums

Fix bindings generation for enums
lawnjelly added a commit to lawnjelly/godot that referenced this issue Apr 25, 2023
…unds

Hierarchical 2D culling - use interpolated bound
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants