• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • integrity-plugin
    • None
    • Jenkins 2.32.1, PTC Integrity CM - Jenkins Plugin 2.0.2, Windows 7

      Hello All,

      I am using the 2.0.2 version of this plugin. I'd like to check-in at the end of the build process.

      My workspace looks like this:

      -folder1
      -folder2
      --fileA
      -file1
      -file2

      The build output is folder2, and I'd like to check-in into that folder of the project. Currently if I set the:

      • Build output folder to: folder2
      • Includes filter: fileA

      Then after the checkin process finishes, the fileA appears in the root of the project, not under the folder2.
      Is there any way with the current implementation to check in into a subfolder of the project?

      Can you help me with this?

      BR,
      Peter

          [JENKINS-41019] Check in into subfolder of current project

          Peter Simon added a comment -

          Added the log file of the original problem: PTCIntegrityLog1.txt
          The problem is basically that it cannot lock the file: fileA
          Because there is no fileA in the project, but folder2/fileA. So this is understandable.

          BUT

          I modified the checking in step, to the following:

          • Build output folder: . (dot)
          • Includes filter: folder2/fileA

          Still error given to the lock command. (Log attached as Log2.txt)
          Although now I don't know why. It tries to lock "folder2\fileA", which I am ABLE to do in a simple command line:
          si lock --project=..project.pj folder2\fileA

          Can you help me with this?

          Peter Simon added a comment - Added the log file of the original problem: PTCIntegrityLog1.txt The problem is basically that it cannot lock the file: fileA Because there is no fileA in the project, but folder2/fileA. So this is understandable. BUT I modified the checking in step, to the following: Build output folder: . (dot) Includes filter: folder2/fileA Still error given to the lock command. (Log attached as Log2.txt) Although now I don't know why. It tries to lock "folder2\fileA", which I am ABLE to do in a simple command line: si lock --project=..project.pj folder2\fileA Can you help me with this?

          PTC ALM added a comment -

          Trying to reproduce the problem.

          PTC ALM added a comment - Trying to reproduce the problem.

          Peter Simon added a comment -

          Thank you. I don't know if that matters, but the 'project.pj' is actually a subproject.

          Peter Simon added a comment - Thank you. I don't know if that matters, but the 'project.pj' is actually a subproject.

          Peter Simon added a comment -

          Hi,

          Did you perhaps manage to recreate the problem?

          Péter

          Peter Simon added a comment - Hi, Did you perhaps manage to recreate the problem? Péter

          Alex Ruff added a comment -

          It looks like we have a very similar Problem with Version 2.1 of the PTC Plugin . The rootcause seems to be the failing lock on a member of the subproject.

          The annoying thing is that because of the failed lock the member (fileA) gets added in a Subdirectory with the same name as the Subproject (folder2). So in the local sandbox folder its unclear which member is finally used.

          Alex Ruff added a comment - It looks like we have a very similar Problem with Version 2.1 of the PTC Plugin . The rootcause seems to be the failing lock on a member of the subproject. The annoying thing is that because of the failed lock the member (fileA) gets added in a Subdirectory with the same name as the Subproject (folder2). So in the local sandbox folder its unclear which member is finally used.

            integrity_jenkins_plugin PTC ALM
            speter Peter Simon
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: