Note that there are some explanatory texts on larger screens.

plurals
  1. PObuildbot vs hudson/jenkins for C++ continuous integration
    primarykey
    data
    text
    <p>I'm currently using jenkins/hudson for continuous integration a large mostly C++ project. We have separate projects for trunk and every branch. Also, there are some related projects for the Java code, but the setup for those are fairly basic right now (we may do more later though). The C++ projects do the following:</p> <ul> <li>Builds everything with options for whether to reconfigure, do a clean build, or use a fresh checkout</li> <li>Optionally builds and runs all tests</li> <li>Optionally runs all tests using Valgrind's memcheck</li> <li>Runs cppcheck</li> <li>Generates doxygen documentation</li> <li>Publishes reports: unit tests, valgrind, cppcheck, compiler warnings, SLOC, open tasks, and code coverage (using gcov, gcovr, and the cobertura plugin)</li> <li>Deploys code nightly or on demand to a test environment and a package repository</li> </ul> <p>Everything is configurable for automatic builds and optional for on demand builds. Underneath, there's a bash script that controls much of this, which farther depends on our build system, which uses automake and autoconf along with custom bash scripts.</p> <p>We started using Hudson (at the time) because that's what the Java guys were using and we just wanted nightly builds. Since then, we've added a lot more and continue to add more. In some ways Hudson is great, but certainly isn't ideal.</p> <p>I've looked at other solutions and the only one that looks like it could be a replacement is buildbot. Would buildbot be better for this situation? Is the investment worth it since we're already using Hudson? Why?</p> <p><strong>EDIT</strong>: Someone asked why I haven't found Hudson/Jenkins to be ideal. The short answer is that everything can be improved. I'm simply wondering if Jenkins is the best current solution for my use case or whether there is something better (buildbot?) that would be easier to maintain in the long run even as new requirements come up.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload