summaryrefslogtreecommitdiffstats
path: root/.travis.yml
Commit message (Collapse)AuthorAgeFilesLines
* Drop release v2.6.0+no-stlportJean-Michel Trivi2015-07-151-2/+1
| | | | | | | Bug 246391 Change-Id: I662b7b0f90c97cb169978e1b64ad1fe32c440cf5 Signed-off-by: Jean-Michel Trivi <jmtrivi@google.com>
* travis: don't send email notificationsDavid Wagner2015-04-241-2/+0
| | | | | | | I never received any email from travis and actually don't want to. Thus, I'm removing my email address from the notification list. Signed-off-by: David Wagner <david.wagner@intel.com>
* travis: Use the docker infrastructureDavid Wagner2015-04-241-36/+32
| | | | | | | | | | | | | | | | | As advertise by travis news: http://blog.travis-ci.com/2014-12-17-faster-builds-with-container-based-infrastructure/ using the new docker infra is faster and more reliable. This comes with the cost of not being able to use "sudo", though. Installing packages is still possible by specifying them in an "addons.apt" section in .travis.yml. We have to remove "sudo make install" but we aren't using the installed libs and binaries anyway. I had some syntax issues with the "addons" and "env" sections and had to remove the coverity subsection which wasn't configure for the 01org repository anyway. Signed-off-by: David Wagner <david.wagner@intel.com>
* Revert "Revert "Merge pull request #88 from krocard/improve_travis_debug_build""Kevin Rocard2015-04-241-8/+7
| | | | | | | | | The pull request #88 was reverted as it broke travis build. In fact it only reveled a bug that was introduced in #80 (1b071fadd). The previous commit 0c0cc95 fixes the problem (cmake variable shadow). Revert the revert (d17b931a3dcc70cf9e) to restore the pull request #88.
* Revert "Merge pull request #88 from krocard/improve_travis_debug_build"David Wagner2015-04-241-7/+8
| | | | | This reverts commit 339779ac82acb755f6e992bf7ee54e3b791a9ca6, reversing changes made to 1b071faddaf8c5e835ea38d6c8d2d5db88011251.
* [Travis] No longer install debug buildKevin Rocard2015-04-241-8/+7
| | | | | | | | | | | | | | | | | | | Debug build used to be installed as it was required for make test. As make test is now stand alone, do not install debug builds. This has several advantages: - slightly faster builds. - make test without install is actually tested by travis. Debug binaries used to overwrite release ones that were installed presciently. As it is no longer the case, and to avoid tests to use installed binaries instead of the local ones, test the debug build *before* the release one. As the debug build is now build (first) in it's own folder, debug and release build can not interfere. Signed-off-by: Kevin Rocard <kevin.rocard@intel.com>
* [Travis] Use gcov long optionsKevin Rocard2015-04-241-1/+1
| | | | Long option are more readable.
* [Travis] Only run gcov through coverallsKevin Rocard2015-04-241-1/+1
| | | | | | | | | | Gcov was run twice, first by the target ExperimentalCoverage and then by coveralls. As coveralls give a better coverage report and cdash is not used, remove ExperimentalCoverage. Signed-off-by: Kevin Rocard <kevin.rocard@intel.com>
* coveralls: send coverage report to coveralls.ioDavid Wagner2015-04-241-0/+13
| | | | | | | | | | | | | | | coveralls.io is a service that uses information from gcov (generated during "make test") to provide a coverage report online: https://coveralls.io/r/01org/parameter-framework Some files must be ignored, specifically: generated files (python bindings and files generated by CMake), tests (because they would inflate the coverage rate) and samples (for now, only the skeleton subsystem). A "badge" is also added to the readme showing the coverage rate. Signed-off-by: David Wagner <david.wagner@intel.com>
* travis: run 'ldconfig' after 'sudo make install'David Wagner2015-04-241-4/+7
| | | | | | | | | | | | In 327b1a48e2fe539c0ca5414ce9c98b2405536a09 we changed the installation prefix to /usr because we witnessed errors during unit tests using the python bindings. We initially thought that /usr/local/lib wasn't in the loader's default paths but it turns out it is. In fact, it only is the loader's cache that was outdated and needed to be regenerated. That's what ldconfig does. Signed-off-by: David Wagner <david.wagner@intel.com>
* C pfw bindingsKevin Rocard2015-04-241-0/+2
| | | | | | | | | The pfw can not currently be used from c code. Add an c api. It does not target a perfect one/one mapping with the c++ one, but rather aim ease of use and type safety (as far as possible in c). Signed-off-by: Kevin Rocard <kevin.rocard@intel.com>
* travis: set the installation prefix to /usrDavid Wagner2015-04-241-3/+3
| | | | | | | | | | | | CMake defaults to /usr/local which results in libraries being installed in /usr/local/lib. Unfortunately, this path isn't in the loader's default locations. The canonical installation path is /usr. /usr/local is recommended for stuff not handled by the package manager but in the context of the CI, this isn't relevant. Signed-off-by: David Wagner <david.wagner@intel.com>
* Modularise build using cmake optionsKevin Rocard2015-04-241-1/+1
| | | | | | | | | | | | | | | | | The parameter framework can build lots of components including but not limited to core c++ lib, c api, python api, bash completion... All those modules are not always wanted, especially if they have external dependencies as it force the builder to install them. Conditionally define non core build modules. The builder can disable feature by providing -D <FEATURE>=OFF to deactivate them. The following options are available: - PYTHON_BINDINGS: Break swig dependencies - BASH_COMPLETION: If the target does not have bash - COVERAGE: Default to off, set to on to build c/c++ with coverage flags. Signed-off-by: Kevin Rocard <kevin.rocard@intel.com>
* Use ctest for testingKevin Rocard2015-04-241-5/+11
| | | | | | | | | | | | | Test were enabled with the enable_testing command. Nevertheless this method is very basic. Include CTest, as this cmake utility enables automatic build + test + coverage generation + memchek test (valgrind) + sending report in one command: ```make Experimental``` There are far more features added by this utility, see: http://www.cmake.org/Wiki/CMake/Testing_With_CTest#Dashboards Signed-off-by: Kevin Rocard <kevin.rocard@intel.com>
* Reformat .travis.yml test commandsKevin Rocard2015-04-241-4/+8
| | | | | | | | Do not execute tests if the build fails. Indent the commands for readability. Signed-off-by: Kevin Rocard <kevin.rocard@intel.com>
* Print test output if the test failsKevin Rocard2015-04-241-1/+1
| | | | | | | | ctest by default put all logs in a file and never display it even if a test fails. Add the relevant option to output on failure. Signed-off-by: Kevin Rocard <kevin.rocard@intel.com>
* Install a recent gcc, gcov, cmake and ctest versionKevin Rocard2015-04-241-2/+10
| | | | | | | | | | | | | | The c pfw interface (following patch) needs a recent gcc to compile. Gcc and gcov version need to be align, thus gcov is updated too. Ctest analyse the gcov output, as a result it must be align with it (gcov 2.7 changed it's report format). Ctest, and cmake are packaged together. Conclusion: update cmake and gcc packages. Unfortunatly ubuntu backport does not provide a recent enough version, that is why ppa were used instead. Signed-off-by: Kevin Rocard <kevin.rocard@intel.com>
* Travis-CI: also build the skeleton pluginDavid Wagner2015-02-131-1/+5
| | | | | | | The skeleton plugin is an example and as such needs to work out-of-the-box. Make travis build it to ensure we don't break anything. Signed-off-by: David Wagner <david.wagner@intel.com>
* Add a configuration file for Travis-CIDavid Wagner2015-02-131-0/+34
Travis will build each new commit and each pull request and publish the results here: https://travis-ci.org/01org/parameter-framework and on the #parameter-framework channel on FreeNode. This commit also adds a build status icon in the Readme. Signed-off-by: David Wagner <david.wagner@intel.com>