When cvs update fails, the sonar operation is still started even though nothing was build at all

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Minor
    • Component/s: sonar-plugin
    • None
    • Environment:
      Hudson 1.377, Linux SUSE SLE 11, Tomcat 6.0.26, jdk 1.6u21, Sonar 2.2

      Due to an error in the cvs update procedure(*see below), the whole build of the project didn't work (in fact it didn't even start), however the Sonar process that runs after the build is still started and processes the old version of the build.
      I would prefer the Sonar process not to start at all if the build before couldn't be started, but I think this this happens since the build doesn't fail, the cvs update does.

      • I should mention that the cvs update failed due to an accented character in a file name, turned out to be a locale issue

            Assignee:
            godin
            Reporter:
            Alex Lehmann
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: