thomas.weltenbauer.

Yes I think we could schedule a meeting. As I said, we can workaround this right now, but maybe we can find the error in the setup.

Oh I'm sorry, this is Teamcity, not Bamboo. Teamcity Version is 2022.10 (build 116751). I tested "Exclude default branch changes from other branches". It does not change anything regarding this error. The build already is a manual build. We don't have any triggers in this test case. It's just starting a new build with the given branch with the "run" button in Teamcity. But to make sure I increased the maximum polling time to prevent polling to interfere, which does not change anything. The "collect changes" is part of the build pre steps in teamcity which we have no direct control of (as far as I know, except for the settings regarding included branches, etc.). Maybe no one is starting builds from main branch? We hat this requirement multiple times in our project, but as this is working with sub branches from the given changesets it is just a matter of some more steps before building. But for automated builds like nightlies it would be create to build from the main branch as well.

Maybe because there was never a build from this branch before? Looks like all changesets are evaluated for pending changes that would be contained in this build. Which means starting from current changeset and going backward all changesets contained in the branch? The error happens in the "Collecting changes" part before the build config itself is even started. With the given settings below and starting the build with the parameter "branch" set to /main the error occurs. It does not matter what is happening after this, so this even happens with an empty build config for the main branch. All other branches (which have changesets with parents) are working without problems. Only changeset 0 seems to be the problem. -------------------------------------

Hi @calbzam Thank you for your answer. No, this is not the case. It is just a build from the main branch (initial branch), which is there since the beginning of the repository and contains changeset 0, which Plastic is diffing based on the error message in teamcity: Error getting diff info of 0: Can't diff cset cs:0@rep:RepSpecs because it doesn't have a parent. Note: I removed the repository specs because it contains repository and server URL. It is possible to prevent the plugin to check for changes on changeset 0? Recreating the VCS root does not change this behaviour.

Same error with version SNAPSHOT-202210120016 of the plugin.

We have the same issue when building from /main branch. It is not possible to build from this branch because of this error and it always happens when you try to build from it. Only workaround is to create a child branch from the CS you want to build. The Changeset 0 by default has now parent. We are currently using Plastic Teamcity Plugin version SNAPSHOT-202108051447 . But I will try to update and see if this is fixed.

The bug is indeed fixed for us in version 11.0.16.7504 which was released yesterday. Thanks!

As blue said, it will be fixed in the next upcomming release, so it is not fixed in the current version, right. Based on the last releases I would guess the next version is released this week. So.. fingers crossed

In version 11.0.16.7411 (Released: 19-Sep-2022) this issue is still present.

What would be an older version? I think we are using the 10.0.16.5622 .net core version. Yes, it is a little older but we had no time to switch to the .net core version with installer yet. Server incompatibility would be a pretty bad thing. This would break the "as long as the third number (16) stays the same it is compatible to the server" rule. As I said: The legacy client is working for me (looks like others have different experiences). So at least the logic there is kind of compatible.

The new version (11.0.16.7388) has the same error.

This also happens when we view incomming changes / newer changesets.

Hello! I'm not sure if this is the right place to post this. Also a search gave me no result about this error, so I'm not sure if it is known already. With the current PlasticX Version (11.0.16.7359) I get this dialog e.G. when merging from one branch into another: "The method GetChangesetsInfoByNumber is not supported." The legacy client is working without problems. Also everything is working with older verison of PlasticX. There are no log entries at the given time (relevant and debug).

Hi, also for developers it would be a good feature to turn the diff of or exclude file types from diff. Our team is not using the diff most of the time. When PlasticX is used for operations (checkin, undo), most of the time the diff view is it's just time consuming. E.g. when selecting multiple files you have to make sure the last one is a file that can be checked very fast to have a good workflow. Otherwise, if you select e.g. a scene or a bigger prefab (when working with a Unity project) you have to wait until the diff is finished, even when the diff itself is not relevant. This makes the PlasticX client slower in comparison to the "old" Plastic client and because of this, most of our team members do not try the PlasticX client.

Hi, I think this behaviour started after one of the last client updates. I'm not sure because we don't have the same version of the client installed on every machine and I'm the first one how noticed this problem. But I know some colleagues have this probleme, too. My client version is 9.0.16.4361. We want to move to the new .net core Version of the plastic server in a few days anyway. Do you think this could be related to the server version? If so, I think the best way is to check, if this happens after the update. Thank you for you help! I come back to you after the update and let you know if this happens again.

I already checked this. I can see the changes in the diff. Here some screenshots: Pending changes in plastic client Output of checkcontent + onlychanged and checkcontent only (As you can see I will get all or nothing ) One of the changes in AddressableAssetSettings (this is the file with the changes): Physics.asset has no changes Undo unchanged changes in Plastic ("Check the content to determine file as changes, not just timestamp" is enabled) Pending changes after undoing unchanged setting So this means, the plastic client can find changes in the AddressableAssetSettings.asset file and does not find changes in Physics.asset. But I can't reproduce this behaviour with the command line tool. I get both as changed or both as unchanged. I hope this helps Thanks again!

Thank you for your answer. I already tried the --onlychanged parameter. But this gives me no return for both items (the one with changes and the one without changes which is just checked out). But if undo unchanged changes in Plastic client, the one without changes is undone. The background of this operation is, that we only want to make an automated process when there really are changes on specific files. So it's not only about the undo operation. I hope this clarifies, why we want this. The undo operation is not needed, but it is a nice side effect, if we could remove these items from pending changes.

Hello, we used the following command to find unchanged change in specific files/directories: cm fc --checkcontent -R %filepath% I know this command is deprecated, but I found no other possibility to do the same per command line. So today I found a problem: I have two binary files in my pending changes. One has changes the other one does not have changes (it's just a checkout). When check the files with the command above, both files have changes according to the output. When I undo unchanged changes in Plastic client, the file without changes is removed from pending changes. Because of this our automated process isn't working any more. I also tried this with a simple checkout of an object wich also gives me the path of the object as if there were changes. Do you have any idea what could be wrong? Thanks! Plastic Client Version: 9.0.16.4361

Ok maybe this is the problem. I was confused because psantosl talked about "marked as checkout" in this thread: https://forum.plasticscm.com/topic/20437-update-workspace-with-pending-changes/ With changed items it is possible to switch branches/changeset, but checkout files are not. Thank you for your help!

The ignore.conf file was just an example. This was the first file I could find and I simply only checked it out in Plastic without any changes. This is the same for every other file. The behaviour changed in a long running project where this worked all the time, so the cloaked items can't be the problem. (Additional information: We don't use a cloaked.conf file in any project so there are no cloaked files) The "Run fast update" is not available in my plastic client. Looks like you removed it (see https://www.plasticscm.com/download/releasenotes/8.0.16.3651#8.0.16.3651-new-7). It's possible this setting is activated but since it is hidden, can't be changed. I could test it if you can tell me which entry I have to change in the config file.

Hello! I was used to switch between changesets and branches with pending changes in Plastic. But this is no longer possible, no matter what I do. Basic infos: Plastic Client Version: 8.0.16.3899 "Allow when trying to switch / update workspace with changed items" is set to "Allow" in the settings Pending changes are checked-out My workspace is set to a branch and I'm trying to switch to another branch (not changeset as described in the thread Update workspace with pending changes) But I'm pretty sure I switch between changesets as well some time ago. The message is the same (no matter if I switch from branch to branch, from branch to changeset or from changeset to changeset): "Cannot perform the switch to branch/label/changeset/shelve since there are pending changes. Please review the pending changes and retry the operation again." Update of the workspace works (if there is a newer changeset on the branch) I also double checked that "PendingChangesOnSwitchAction" is set to "None" in my client.conf. I also made a short test in a small project with the same result. This is where I made this screenshots: Pending Changes View in Branch Explorer (tried to switch from main branch to /main/TestBranch) Workspace Settings And the message I can't say since which version of the client this isn't working but I didn't changed my behaviour and wondered, why this isn't working. Do you have a idea what could be the problem ore any recommendation what I could test? Thanks in advance! Thomas

Hi, we are using groups to specify users that can only work on specific branches. Therefore we removed permissions for this group in the repository permissions (except read and view) and overwrite the permissions for the branches. This works well for everything except the "changecomment" permission. If the user wants to change a comment on one of the defined branches, he gets the message "You don't have permissions for operation changecomment". Is it possible that this is a bug? As all other features (like commiting, merging, etc.) are working well with this method. In the attachments you can see the settings for the repository (ReproSettings) and one of the branches (BranchSettings) for the group. Thanks in advance! Thomas BranchSettings ReproSettings

Hi, so I copied all data from E:\ to E:\jet and changed the jet.conf file. No Plastic starts without problems. So it seems like only Drive Letter as path is not working with newer Plastic versions. Can an admin mark this thread as solved, please? Thanks for your help! Thomas

Hi, thank you for your fast answer. Yes, we are paying customers, but at this point the issue is not urgent, because our current setup is running. Our jet.config contains this: basepath=E:\ prefix= suffix= maxcachedtrees=50 datafilesize=4 I thought about the "short" path with only the driveletter could be the problem, but wanted to wait for you answer. I will try to move the repository files. Regards Thomas

We are using Plastic SCM Server 7.0.16.2877 at the moment but we want to upgrade to a newer version. But after every version that we install (tried 7.0.16.2888 and multiple 8.0.X releases, the last one I tried was 8.0.16.3088) the plastic server service can't be started. The plastic.debu.log.txt says: 2019-07-12 17:32:55,536 Main-1 INFO Daemon - Initialize Datalayer 2019-07-12 17:32:55,552 Main-1 INFO DatalayerFs.FsConfParser - JET SETTINGS: 2019-07-12 17:32:55,552 Main-1 INFO DatalayerFs.FsConfParser - basepath=E:\ 2019-07-12 17:32:55,552 Main-1 INFO DatalayerFs.FsConfParser - prefix= 2019-07-12 17:32:55,552 Main-1 INFO DatalayerFs.FsConfParser - suffix= 2019-07-12 17:32:55,552 Main-1 INFO DatalayerFs.FsConfParser - maxcachedtrees=50 2019-07-12 17:32:55,552 Main-1 INFO DatalayerFs.FsConfParser - datafilesize=4294967296 2019-07-12 17:32:55,552 Main-1 INFO DatalayerFs.FsConfParser - highperf=True 2019-07-12 17:32:55,552 Main-1 INFO DatalayerFs.FsConfParser - cleaningtemppath=C:\WINDOWS\TEMP\ 2019-07-12 17:32:55,552 Main-1 FATAL Daemon - Value cannot be null. Parameter name: path1 2019-07-12 17:32:55,552 Main-1 DEBUG Daemon - Value cannot be null. Parameter name: path1 at System.IO.Path.Combine(String path1, String path2) at Codice.CM.Server.ShareFolder.BuildFromJetPath(String jetPath, String prefix, String suffix) at DatalayerFs.FsDatalayer.Build(FsConf config) at Codice.CM.Data.Datalayer.Initialize() at akn.a(aas A_0) at akn.a(String[] A_0) I'm not really sure what's the problem here. As you can see the basepath is set (and all these settings are working with version 7.0.16.2877). Do you have any idea how to solve this? Thanks in advance! Thomas