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.