Assuming that the build step is a shell script, then the defaults when started are /bin/sh -xe which causes it to return at the first error.
You can alter this following the answers in https://groups.google.com/d/topic/jenkinsci-users/dyS1y4y32tc/discussion Chris. On Friday, November 16, 2012 10:32:45 AM UTC, Miguel Algaba Borrego wrote: > > Hi all, > > I am working in a C++ project and use Jenkins for CI. Our slave machine > runs Ubuntu Server 12.04 and we are using several plug-ins to detect and > report C++ compiling warnings, but we are wondering if it would be possible > to report C++ compiling errors as well. We noticed that Jenkins > automatically stops the job execution after a compiling error. We have also > tried to compile our targets using the "make -k" option to let the compiler > continue in case of failing targets. This way, he finally get non-failing > targets compiled, but Jenkins keeps stopping the job. Is there a way to let > Jenkins continue executing the job and report the failing targets and > detected compiling errors (in a similar way to detected warnings)? > > Thanks a lot and best regards! > Miguel Algaba. >
