dharillo

We upgraded the server and the issue was solved. I think that the 3rd version number (which indicates server-client compatibility) should have been updated when the client stopped being fully compatible with the server. The server may be compatible with older versions of the client when the 3rd version number matches. The other way is not always true. Some features that come in newer versions of the client require that the server is updated to match the client version sometimes.

Ok, no problem! For those who wish to downgrade the linux version on Ubuntu, you should execute the following command: $ sudo apt install plasticscm-client-complete=10.0.16.6307 plasticscm-client-core=10.0.16.6307 plasticscm-client-gtk=10.0.16.6307 plasticscm-theme=10.0.16.6307

Version: 10.0.16.6339 Operating system: Ubuntu 20.04.1 Steps to reproduce: 1. Open a terminal 2. Try to launch the application from /opt/plasticscm5/client/linplasticx Actual behavior: Unhandled exception. System.NullReferenceException: Object reference not set to an instance of an object. at PlasticAvalonia.MainMenu.BuildAppMenu() at PlasticAvalonia.MainMenu.BuildComponents() at PlasticAvalonia.MainMenu..ctor(IMainMenuOperations mainMenuOperations) at PlasticAvalonia.WindowHandler..ctor(GuiHelpEvents guiHelpEvents, NewVersionNotificationControl newVersionNotificationControl, PlasticWebRestApi restApi, IClassicDesktopStyleApplicationLifetime applicationLifetime) at PlasticAvalonia.App.<>c__DisplayClass1_0.<OnFrameworkInitializationCompleted>b__10() at PlasticAvalonia.Diagnostics.TraceTimer.Span.Add(String actionName, Action action) at PlasticAvalonia.App.OnFrameworkInitializationCompleted() at Avalonia.Controls.AppBuilderBase`1.Setup() at Avalonia.Controls.AppBuilderBase`1.SetupWithLifetime(IApplicationLifetime lifetime) at Avalonia.ClassicDesktopStyleApplicationLifetimeExtensions.StartWithClassicDesktopLifetime[T](T builder, String[] args, ShutdownMode shutdownMode) at PlasticAvalonia.Program.Main(String[] args) Aborted (core dumped) Expected result: The application should start with the new UI

Hi @ollieblanks, Yes, we have an on-premise server. The problem is happening to three different people and has happened in more than one review. I think it is easily reproducible. I have already asked our IT team to check if they can update the server version to the latest version and they are going to check it. Also, they are going to contact you at your support e-mail, linking this post if you need more detailed information that I can not share in a public forum (like screenshots where our code may be visible).

Lately, we are experimenting some issues with the code reviews. We make the code reviews for entire branches and when there are multiple change requests we try to fix each one in a single check-in. This one a review with 3 change requests will have three different changesets after the one where the review was done. We've been working this way for months, and all worked fine. But, in recent versions of the client, after the first check-in closing a change request, double-clicking on the next pending change only opens the file where the comment was done. Double-clicking again navigates to the zone where the comment was done but the circle indicating the line where the comment was done does not appear and the right pane does not show the full review comment either. Clicking on the "Revision with comments", "Last in branch" or "Diff with head" does not seem to fix it either. We have tested this in the following client versions: 10.0.16.5642 10.0.16.5459 9.0.16.5242 Our server version is: 9.0.16.4507

Hi, I had Java 11. I just tried downgrading to Java 8 and it works fine. Will you deliver a new plugin version compatible with Java 11? Regards!

Greetings! We are trying to use the Teamcity plugin with the "checkout on agent" configuration. This configuration works fine on Windows, but for a Linux agent the checkout does not work. The build fails event before the first build step: Looking at the teamcity-agent.log the next exception trace appears: [2019-10-01 17:54:40,649] ERROR - pl.patch.ProjectSourcesOnAgent - Problem while checkout on agent java.lang.NoClassDefFoundError: Could not initialize class org.apache.commons.lang.SystemUtils at com.codicesoftware.plugins.teamcity.PathUtils.isFileInSymlinkContained(PathUtils.java:34) at com.codicesoftware.plugins.teamcity.PathUtils.getCanonicalPath(PathUtils.java:16) at com.codicesoftware.plugins.teamcity.WorkspaceManager.ensureWorkspaceExists(WorkspaceManager.java:21) at com.codicesoftware.plugins.teamcity.PlasticAgentVcsSupport.updateSources(PlasticAgentVcsSupport.java:67) at jetbrains.buildServer.agent.impl.vcs.AgentVcsManagerExImpl$CheckoutSupportImpl.updateSources(AgentVcsManagerExImpl.java:108) at jetbrains.buildServer.agent.impl.patch.ProjectSourcesOnAgent$1.run(ProjectSourcesOnAgent.java:186) at java.base/java.lang.Thread.run(Thread.java:834) [2019-10-01 17:54:40,651] WARN - l.patch.AbstractSourcesUpdater - Error while checkout on agent: Problem while checkout on agent: java.lang.NoClassDefFoundError: Could not initialize class org.apache.commons.lang.SystemUtils jetbrains.buildServer.vcs.VcsException: Problem while checkout on agent: java.lang.NoClassDefFoundError: Could not initialize class org.apache.commons.lang.SystemUtils at jetbrains.buildServer.agent.impl.patch.ProjectSourcesOnAgent$1.run(ProjectSourcesOnAgent.java:192) at java.base/java.lang.Thread.run(Thread.java:834) Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.apache.commons.lang.SystemUtils at com.codicesoftware.plugins.teamcity.PathUtils.isFileInSymlinkContained(PathUtils.java:34) at com.codicesoftware.plugins.teamcity.PathUtils.getCanonicalPath(PathUtils.java:16) at com.codicesoftware.plugins.teamcity.WorkspaceManager.ensureWorkspaceExists(WorkspaceManager.java:21) at com.codicesoftware.plugins.teamcity.PlasticAgentVcsSupport.updateSources(PlasticAgentVcsSupport.java:67) at jetbrains.buildServer.agent.impl.vcs.AgentVcsManagerExImpl$CheckoutSupportImpl.updateSources(AgentVcsManagerExImpl.java:108) at jetbrains.buildServer.agent.impl.patch.ProjectSourcesOnAgent$1.run(ProjectSourcesOnAgent.java:186) ... 1 more Plugin version: Do you know why may this be happening? I have looked at the plugin folder in the agent and the commons-lang.jar is there. Regards!