Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-20016

Build in Jenkins fails when gcc finds errors


    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Major Major
    • core
    • S.O.: Ubuntu Server 11.04; GCC version: 4; Compiler Warning Plugin: version 4.35; Jenkins version: 1.480.3

      Hello people

      I'm trying to build a C project using Jenkins. This project has many source files (over 500), so I'm doing this step by step.

      What I'm trying to achieve is to get all the errors and warnings into a file, this file is useful, because after that I need these results for Jenkins "Compiler Warning Plugin".

      To get all the information I need I'm running the following command as a "Build Step":

      gcc -Wall path/to/my/source/files.c 2>report.xml

      After that, I have other configurations and build steps, but when I execute the build, it fails because of the error messages triggered by gcc. And the rest of the steps an other configurations are never executed.

      The thing is, if I execute the same gcc command, to the same files, but outside Jenkins, I mean in a typically Linux terminal, I don't receive any message about failure. The xml file with warnings and errors output is generated and the Linux terminal finish the task without complaint

      How can I achieve the same behavior in Jenkins and not receive a build failure message? Thanks!

            Unassigned Unassigned
            acordinz Angelo Cordova
            0 Vote for this issue
            2 Start watching this issue