Hello Plugin support,

 I have been working with Jenkins and the PTC Plugin for quite some time. And now facing issues at the Check-in stage. I am using Jenkins 2.89.4 and PTC Plug V 2.1.

Our scenario just before PTC Check-in stage:

FolderLevel1 (project.pj)

-FolderLevel2 (project.pj)

-SomefileLevel2.txt

SomefileLevel1.txt

So my intention is to checkin all files into PTC and still maintaining their "Projectstructure". What I am ending up with is that SomefileLevel1.txt gets updated correctly (Rev1.2) but on any file which is on DirectoryLevel2< the Plugin creates a Directory inside the FolderLevel1 and creates a branched version of SomefileLevel2.txt Rev 1.1.1.1. I have attached a screenshot of my sandbox to further clarify the situation.

Am I completely misunderstanding the concept here or is this some kind of bug/feature missing in the Plugin? I am just wondering as many people in forum are successfully using the checkin feature but from my point of view this limits the use of any sub-project structures inside a project.

I have made further analysis of my problem and kind of stuck here:

 In one of my Log analysis sessions I came acros this part of the log. (See attachment)

...

Lock failed: The file DirectoryLevel3\PTCCheckinTest.txt is not a current or destined or pending member or a subproject of /Playground/PlaygroundTest/ArnoTest/DirectoryLevel2/project.pj

...

This error tells me that the plugin tries to lock a member in a directory and obviously fails as the intendet member is inside the project DirectoryLevel3 not the directory.

So later it does the unwanted member add together with a new directory:

...

si projectadd --user=username --port=7001 --hostname=integrity.company.xyz.com --saveTimestamp --nocloseCP --onExistingArchive=sharearchive --project=#/Playground#PlaygroundTest/ArnoTest/DirectoryLevel2 --cpid=:none --sourceFile=remote://D:\BuildServer\jenkins\workspace\PTC_Playground\ArnoTest\DirectoryLevel2\DirectoryLevel3\PTCCheckinTest.txt --description=Build updates from PTC_Playground #23 – DirectoryLevel3\PTCCheckinTest.txt returned exit code 0

...

In contrast on the "root level = #/Playground#PlaygroundTest/ArnoTest/DirectoryLevel2" of the checkin procedure it does the checkin correctly:

...

si lock --user=username --port=7001 --hostname=integrity.company.xyz.com --project=#/Playground#PlaygroundTest/ArnoTest/DirectoryLevel2 --cpid=:none – PTCCheckinTestL2.txt returned exit code 0

Attempting to checkin file: D:\BuildServer\jenkins\workspace\PTC_Playground\ArnoTest\DirectoryLevel2\PTCCheckinTestL2.txt

si projectci --user=username --port=7001 --hostname=integrity.company.xyz.com --saveTimestamp --nocloseCP --nodifferentNames --branchVariant --nocheckinUnchanged --project=#/Playground#PlaygroundTest/ArnoTest/DirectoryLevel2 --cpid=:none --sourceFile=remote://D:\BuildServer\jenkins\workspace\PTC_Playground\ArnoTest\DirectoryLevel2\PTCCheckinTestL2.txt --description=Build updates from PTC_Playground #23 – PTCCheckinTestL2.txt returned exit code 0

It feels like I am missing a setting that forces the PTC plugin to use Sub-Projects instead of Directories for its checkin process.

Best regards 

Alex