-
Notifications
You must be signed in to change notification settings - Fork 28
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 for install script #15
Conversation
Preliminary merge
Signed-off-by: Ruben Smits <[email protected]>
Signed-off-by: Ruben Smits <[email protected]>
Signed-off-by: Ruben Smits <[email protected]>
Signed-off-by: Ruben Smits <[email protected]>
Signed-off-by: Ruben Smits <[email protected]>
Signed-off-by: Ruben Smits <[email protected]>
707f3c7
to
be98b08
Compare
Signed-off-by: Ruben Smits <[email protected]>
Signed-off-by: Ruben Smits <[email protected]>
.travis.yml
Outdated
- if [[ "$TRAVIS_OS_NAME" == "osx" ]]; then brew link --force gnu-getopt ; fi | ||
|
||
script: | ||
- ./install.sh --verbose --prefix $HOME/install --enable-tests --enable-corba --enable-mqueue |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't actually run the tests, so why build them? Or should we add another line that runs the tests after installation? Or would you expect that --enable-tests
not only builds but also runs the tests?
Signed-off-by: Ruben Smits <[email protected]>
Unit tests will be built and run for individual projects, but not for this meta repository. The purpose of this job is mainly to test the installation script.
Looks good to merge now. Note that containerized builds still cause some trouble for unit testing, like in orocos-toolchain/rtt#195, but as a pure installation script test case it should be fine. I disabled tests in 71d9b01, but they were only built and not executed until now. |
No description provided.