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 Automated Testing of the Core #4008

Closed
wants to merge 1 commit into from

Conversation

danoli3
Copy link
Member

@danoli3 danoli3 commented Jun 26, 2015

Automated PR / Commit and Merge testing of Core

Original Discussion here from 2012: Continuous integration/testing #1068

  • iOS Empty Example + openFrameworks Core iOS Build Testing
  • OSX Empty Example + openFrameworks Core OSX Build Testing
  • Adds a tick or cross to every PR for fail or success (once configured on Travis-ci website) (You may remember this happening a while ago when travis was added for documentation generation).
  • Removes Documentation Automation - @HalfdanJ had some travis code to generate http://docs.openframeworks.cc automatically on merges.
    This should be done another way, travis is integration testing, even the Github API is designed for this.

- iOS Empty Example + openFrameworks Core iOS Build Testing
- OSX Empty Example + openFrameworks Core OSX Build Testing
@danoli3
Copy link
Member Author

danoli3 commented Jun 26, 2015

Example Branch: https://github.com/danoli3/openFrameworks/tree/Automated/Travis-OSX
Travis Status: https://travis-ci.org/danoli3/openFrameworks/branches

Using the template/emptyExample project for both
Limitations we have with Travis are the time per build (max 1 hour).
So I thought for now the emptyExample is perfect. It validates the core has not been broken by a commit.

Testing this I created another branch from this, one which should soon fail.

https://github.com/danoli3/openFrameworks/tree/Automated/Travis-CoreFail
https://travis-ci.org/danoli3/openFrameworks/builds/68468345

@bilderbuchi
Copy link
Member

This should be done another way, travis is integration testing,

well, to be precise, Travis-CI is Continuous Integration, and artifact generation (and that includes docs) is a part of Continuous Integration. ;-)

@bilderbuchi
Copy link
Member

also, there's no need to rip out the docs generation if we still want that, the builds can run in parallel with a proper travis.yml.

@bilderbuchi
Copy link
Member

also, I think we could run both linux and osx at the same time with the os flag. using the make compilation on osx would make that easier, too, i think.

@danoli3
Copy link
Member Author

danoli3 commented Jun 26, 2015

@bilderbuchi! Nice I'll check out that more detailed matrix style and get everything in one.

@danoli3
Copy link
Member Author

danoli3 commented Jun 26, 2015

Okay I think I've figured it out. I'll keep working on a new PR.

New changes so far just putting into https://github.com/danoli3/openFrameworks/tree/Automated/Travis-OSX for tests.

@danoli3 danoli3 closed this Jun 26, 2015
@danoli3 danoli3 deleted the Automated/Travis branch July 9, 2015 11:41
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

Successfully merging this pull request may close these issues.

2 participants