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

Team Concert plugin cannot resolve Jenkins path and Build Definition Jazz Source Control path

XMLWordPrintable

      When the Jenkins Job's working directory is set and the RTC Build Definition under 'Jazz Source Control', you need to set the Load Directory.
      If an absolute path is used, the Team Concert plugin combines the Jenkins Job workspace (even custom one) and the RTC Build Definition load directory.

      Jenkins Job log:
      ================
      Started by user Beerens, Danny
      [EnvInject] - Loading node environment variables.
      Building in workspace C:\Jenkins\Workspace
      RTC : checkout...
      FATAL: RTC : checkout failure: Load directory C:\Jenkins\Workspace\C:\Data\IBM\RTC is invalid : The filename, directory name, or volume label syntax is incorrect
      ERROR: RTC : checkout failure: Load directory C:\Jenkins\Workspace\C:\Data\IBM\RTC is invalid : The filename, directory name, or volume label syntax is incorrect
      Finished: FAILURE

      Workaround:
      ===========
      Set-up Jazz Source control load directory to have a relative path, e.g. "EPNav"
      Result:
      -------
      Building in workspace C:\Jenkins\Workspace\
      RTC : checkout...
      RTC Checkout : Source control setup
      RTC Checkout : Accepting changes into workspace "sys24_Test_Rumba_EPNavigator_Team Workspace" ...
      RTC Checkout : Fetching files to fetch destination "C:\Jenkins\Workspace\EPNav" ...

          [JENKINS-18292] Team Concert plugin cannot resolve Jenkins path and Build Definition Jazz Source Control path

          Scott Cowan added a comment -

          Hi Danny,

          We'll investigate this one. Perhaps we can detect if a qualified path is specified and just use it, otherwise we'd concatenate it on to the jenkins workspace path.

          In the meantime, you should be unblocked by using a relative path.

          Scott

          Scott Cowan added a comment - Hi Danny, We'll investigate this one. Perhaps we can detect if a qualified path is specified and just use it, otherwise we'd concatenate it on to the jenkins workspace path. In the meantime, you should be unblocked by using a relative path. Scott

          Scott Cowan added a comment -

          I've adjusted the priority using the Jenkins guidelines,

          Blocker
          Blocks development and/or testing work, production could not run.
          Critical
          Crashes, loss of data, severe memory leak.
          Major
          Major loss of function.
          Minor
          Minor loss of function, or other problem where easy workaround is present.
          Trivial
          Cosmetic problem like misspelled words or misaligned text

          Scott Cowan added a comment - I've adjusted the priority using the Jenkins guidelines, Blocker Blocks development and/or testing work, production could not run. Critical Crashes, loss of data, severe memory leak. Major Major loss of function. Minor Minor loss of function, or other problem where easy workaround is present. Trivial Cosmetic problem like misspelled words or misaligned text

          Nick Edgar added a comment -

          I had made a similar suggestion by email:

          • This is a defect which we'll investigate (it's supposed to use the full path if given, and only append to Jenkins workspace path if relative).
          • For now, please specify a relative path in the build definition, or use "." if you want to use the Jenkins workspace directory directly.

          Danny responded with:
          >> We’ve already switched to a relative path setting in the 'Load Directory'-setting of the 'Jazz Source Control'-tab in the Build Definition. Good suggestion to use the “.” here, thanks.

          Nick Edgar added a comment - I had made a similar suggestion by email: This is a defect which we'll investigate (it's supposed to use the full path if given, and only append to Jenkins workspace path if relative). For now, please specify a relative path in the build definition, or use "." if you want to use the Jenkins workspace directory directly. Danny responded with: >> We’ve already switched to a relative path setting in the 'Load Directory'-setting of the 'Jazz Source Control'-tab in the Build Definition. Good suggestion to use the “.” here, thanks.

          Heather Fraser-Dube added a comment -

          Created a work item in jazz.net corresponding to this issue. 274151: Absolute path in build definition is treated as a relative path by Jenkins plugin

          Heather Fraser-Dube added a comment - Created a work item in jazz.net corresponding to this issue. 274151: Absolute path in build definition is treated as a relative path by Jenkins plugin

          Scott Cowan added a comment -

          On Linux, a build definition with a load directory starting with "/" (i.e. "/any/folder") used to be interpreted as a relative path, but is now correctly interpreted as an absolute path. So, any build definition relying on the previous behavior need only prefix the load directory with a "." (i.e. "./any/folder").

          Scott Cowan added a comment - On Linux, a build definition with a load directory starting with "/" (i.e. "/any/folder") used to be interpreted as a relative path, but is now correctly interpreted as an absolute path. So, any build definition relying on the previous behavior need only prefix the load directory with a "." (i.e. "./any/folder").

            Unassigned Unassigned
            dbeerens Danny Beerens
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: