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

cppunit: always use workspace as root

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: other
    • Labels:
      None
    • Environment:
      Platform: All, OS: All
    • Similar Issues:

      Description

      The current cppunit plugin sometimes uses the SCM module, and sometimes uses the
      workspace as the root. Although this is documented, it is unnecessarily
      confusing. It would be far better to maintain consistency both within itself and
      with the JUnit module, and always use the workspace as the root.

      If for some reason this is not possible, provide an option or method to ignore
      the module and use the workspace as root.

      In my case, the SCM checked out module is throwaway, used only to check for
      changes. The actual build is done in a different sub-directory of the workspace.
      Therefore the test results are in a different directory to what CppUnit is
      expecting and this borks the build occasionally.

      (additionally, adding cppunit as a subcomponent of bugzilla would be useful)

        Attachments

          Activity

          Hide
          gbois Gregory Boissinot added a comment -

          OK, It depends on the context.
          I understand your use case.

          According to the plugins ecosystem, the workspace is more used than the module
          root. Nevertheless, with some SCM like Clearcase, the module root is more
          suitable in order to not scan result files in old clearcase view (not deleted in
          the workspace).

          An additional option would be the best solution.

          Are there any other opinions or feedback?

          Show
          gbois Gregory Boissinot added a comment - OK, It depends on the context. I understand your use case. According to the plugins ecosystem, the workspace is more used than the module root. Nevertheless, with some SCM like Clearcase, the module root is more suitable in order to not scan result files in old clearcase view (not deleted in the workspace). An additional option would be the best solution. Are there any other opinions or feedback?
          Hide
          gbois Gregory Boissinot added a comment -

          Fixed with cppunit plugin 1.1

          Show
          gbois Gregory Boissinot added a comment - Fixed with cppunit plugin 1.1

            People

            Assignee:
            gbois Gregory Boissinot
            Reporter:
            brofield brofield
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: