All geek questions in one place

Linux Continuous Build

We have a small C ++ Linux project that accompanies our large C ++ / MFC Windows project. Currently, the Windows project uses CruiseControl.net and Visual Build Pro to manage continuous building and integration. We would like to implement something to launch our Linux project in the same way.

My question is: should I learn to use a separate build tool for Linux or try to get Visual Build Pro to work using my automation and just calling make script on our Linux Build machine to actually compile the project?

Also, due to the size of the Linux project, will it be easier for the script to all include snapshots etc.?

+4
source share
2 answers

You can use jenkins or hudson to build on a Linux box. These tools have integration with Source Control (svn, perforce, ...), cppunit ...

+2
source

As long as I don’t know the complexity of the “integration” step in your project, the “build” step in my experience is best resolved by a trivial shell script:

BUILDDIR=`mktemp -d` svn checkout MY_REPOSITORY/trunk $BUILDDIR cd $BUILDDIR ./configure make all check

I solved part of the integration test with Dejagnu in my current project, it works like a charm with another sh line calling it.

Then paste this shell script into the daily runtime program (for example, adding it to crontab special CI user on a Linux machine) and forward all the mail that the CI user receives from the person responsible for monitoring the CI.

+3
source

Source: https://habr.com/ru/post/1381161/

More articles:


All Articles