Jump to content

Amarok

Members
  • Content Count

    76
  • Joined

  • Last visited

  • Days Won

    6

Amarok last won the day on January 10 2014

Amarok had the most liked content!

Community Reputation

10 Good

About Amarok

  • Rank
    Advanced Member
  • Birthday 03/18/1979

Profile Information

  • Gender
    Male
  • Location
    Austria

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi! We are using v7.9.2 of JIRA (self-hosted server edition). Regards, Olaf
  2. Hi Codice! Could it be that the "Display branch task info" feature in the Branch Explorer is broken? We updated Plastic SCM clients (7.0.16.2679) and now the Summary of the associated JIRA task isn't shown anymore on top to branches. The Plastic SCM client logs reveal: 2018-11-05 10:46:59,607 ANTON-PAAR\foo.bar ERROR jiraextensionrest - Could not get the issue MULTIPLE_PROJECTS-main from the JIRA server: The remote server returned an error: (404) Not Found. 2018-11-05 10:46:59,609 ANTON-PAAR\foo.bar DEBUG jiraextensionrest - Stack trace: at System.Net.HttpWebRequest.GetResponse() at Codice.Client.IssueTracker.Jira.JiraRestClient.GetResponse(HttpWebRequest request) at Codice.Client.IssueTracker.Jira.JiraRestClient.GetIssue(String issueKey) 2018-11-05 10:46:59,609 ANTON-PAAR\foo.bar WARN jiraextension - Issue 'MULTIPLE_PROJECTS-main' not found. 2018-11-05 10:46:59,611 ANTON-PAAR\foo.bar ERROR jiraextension - Error loading task main: Object reference not set to an instance of an object. It seems only the "branch task info" feature is affected. The JIRA integration works otherwise, except for the "branch task info". For example, we can create new branches based on JIRA issues, we see issue details in the branch explorer's right-side pane "Atlassian JIRA Extension". Coworkers having older Plastic SCM client versions (7.0.16.2319) installed, still see the "branch task info" on top of branches. Kind regards, Olaf Kober
  3. Our current workspace setup contains a xlink to another repository. The xlinked folder contains build scripts and build tools. Now, when switching between different branches, it is often the case that these branches refer to different versions of the xlinked repository. The current behavior of Plastic SCM client (5.x and 6.x) is that it DOES NOT update the xlinked folder automatically. We have to manually update the workspace once to get the correct files in the xlinked folder. If one forgets to do the update, it sees the up-to-date files of the repository, but non-matching build tools/scripts in the xlinked folder. That behavior is confusing for most users, especially new ones. Is there a configuration option for changing this behavior?
  4. Is there a way (configuration file) to increase the number of recently-used workspaces shown under the workspaces drop-down (this new workspace selector in Plastic 6 client's upper left corner)? I'm asking because I frequently switch between about 20 workspaces and the recent list only holds 7 entries, even though there would be much more space to show more. In this aspect, the new Plastic 6 GUI is a step back. The multiple workspace tabs in the older clients was better suited for my work style. Thus, I'm asking if I can easily increase the number of recent workspaces. That would help much.
  5. Installation of Plastic Proxy doesn't work neither on Win 7 nor on Win 10. That means, installation runs through although it shows an error message (on Win 10 something about FileNotFoundException), but then starting the services fails all the time.
  6. Everything fine!! Using the newest Plugin SNAPSHOT-201509221250 the problem goes away. So, the real problem was that I downloaded the wrong version, however that happened. Thanks Manu and sorry for the trouble!
  7. Now, this is really strange. I downloaded the TeamCity plugin yesterday to be sure that I use the latest version and got the version SNAPSHOT-201504131654. Today I get the correct version, the same you attached. Will try this one...
  8. Opps, I mistyped something. I was downgrading to 5.4.16.668 to workaround that issue.... 668 not 686.
  9. Hi! I tried to upgrade our build infrastructure to the newest versions of TeamCity (9.1.3), Plastic SCM (5.4.16.692) and Plastic SCM plugin for Teamcity (SNAPSHOT-201504131654 which was the latest version I found on the download page today). After upgrading the first builds run fine, but then when I commited a change the next time TeamCity determines the change differences I got following error: Error collecting changes for VCS repository '"DarwinVCS" {instance id=2, parent internal id=1, parent id=Darwin_DarwinVCS, description: "repository "Darwin.Backbone@localhost:8087" path "/" branch "/main" checkout "/main""}' jetbrains.buildServer.vcs.VcsOperationProgressRunner$VcsOperationException: java.lang.StringIndexOutOfBoundsException: String index out of range: -33 with stack trace: jetbrains.buildServer.vcs.VcsOperationProgressRunner$VcsOperationException: java.lang.StringIndexOutOfBoundsException: String index out of range: -33 at jetbrains.buildServer.buildTriggers.vcs.ConnectionStateReporterImpl.reportConnectionFailed(ConnectionStateReporterImpl.java:12) at jetbrains.buildServer.buildTriggers.vcs.ConnectionStateReporterImpl.reportConnectionFailed(ConnectionStateReporterImpl.java:0) at jetbrains.buildServer.buildTriggers.vcs.VcsRootChangesLoader$RunLoadChanges.run(VcsRootChangesLoader.java:68) at jetbrains.buildServer.util.NamedThreadFactory.executeWithNewThreadName(NamedThreadFactory.java:89) at jetbrains.buildServer.buildTriggers.vcs.VcsRootChangesLoader.loadChanges(VcsRootChangesLoader.java:20) at jetbrains.buildServer.vcs.impl.VcsChangesFetcher$LoadChangesForRoot.run(VcsChangesFetcher.java:8) at jetbrains.buildServer.vcs.impl.VcsChangesLoaderImpl$ImmediateFutureExecService$1.call(VcsChangesLoaderImpl.java) at jetbrains.buildServer.serverSide.impl.ImmediateFuture.get(ImmediateFuture.java:59) at jetbrains.buildServer.serverSide.impl.ImmediateFuture.get(ImmediateFuture.java:68) at jetbrains.buildServer.vcs.impl.PeriodicChangesLoader.waitForTaskToComplete(PeriodicChangesLoader.java:13) at jetbrains.buildServer.vcs.impl.PeriodicChangesLoader.loadChanges(PeriodicChangesLoader.java:11) at jetbrains.buildServer.vcs.impl.VcsChangesLoaderImpl.tryLoadChanges(VcsChangesLoaderImpl.java:24) at jetbrains.buildServer.serverSide.impl.VcsModificationChecker$CollectChangesAction$1.run(VcsModificationChecker.java:0) at jetbrains.buildServer.util.NamedThreadFactory.executeWithNewThreadName(NamedThreadFactory.java:89) at jetbrains.buildServer.serverSide.impl.VcsModificationChecker$CollectChangesAction.run(VcsModificationChecker.java:2) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: jetbrains.buildServer.vcs.VcsException: jetbrains.buildServer.vcs.VcsOperationProgressRunner$VcsOperationException: java.lang.StringIndexOutOfBoundsException: String index out of range: -33 at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.collectChangesWithProgress(LoadChanges.java:23) at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.collectChangesForCheckoutRules(LoadChanges.java:49) at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.collectChangesByCombinedRule(LoadChanges.java:11) at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.collectChanges(LoadChanges.java:34) at jetbrains.buildServer.buildTriggers.vcs.VcsRootChangesLoader$RunLoadChanges.run(VcsRootChangesLoader.java:39) ... 17 more Caused by: jetbrains.buildServer.vcs.VcsOperationProgressRunner$VcsOperationException: java.lang.StringIndexOutOfBoundsException: String index out of range: -33 at jetbrains.buildServer.vcs.VcsOperationProgressProviderImpl.runWithProgress(VcsOperationProgressProviderImpl.java:29) at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.collectChangesWithProgress(LoadChanges.java:26) ... 21 more Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: -33 at java.lang.String.substring(String.java:1931) at com.codicesoftware.plugins.teamcity.PlasticVcsSupport$1.collectChanges(PlasticVcsSupport.java:284) at jetbrains.buildServer.vcs.utils.VcsPluginUtil.collectBuildChanges(VcsPluginUtil.java:63) at jetbrains.vcs.api.services.collectChanges.CollectRepositoryChangesPolicyFactory$8.collectChanges(CollectRepositoryChangesPolicyFactory.java:2) at jetbrains.vcs.api.services.collectChanges.SingleVersionCollectChangesCommand.collectChanges(SingleVersionCollectChangesCommand.java:1) at jetbrains.vcs.api.services.collectChanges.CollectChangesServiceProvider$1.collectChanges(CollectChangesServiceProvider.java:4) at jetbrains.buildServer.buildTriggers.vcs.LoadChanges$CollectChangesForCheckoutRules.call(LoadChanges.java:12) at jetbrains.buildServer.buildTriggers.vcs.LoadChanges$CollectChangesForCheckoutRules.call(LoadChanges.java:8) at jetbrains.buildServer.vcs.VcsOperationProgressProviderImpl.runWithProgress(VcsOperationProgressProviderImpl.java:27) ... 22 more jetbrains.buildServer.vcs.VcsException: jetbrains.buildServer.vcs.VcsOperationProgressRunner$VcsOperationException: java.lang.StringIndexOutOfBoundsException: String index out of range: -33 at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.collectChangesWithProgress(LoadChanges.java:23) at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.collectChangesForCheckoutRules(LoadChanges.java:49) at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.collectChangesByCombinedRule(LoadChanges.java:11) at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.collectChanges(LoadChanges.java:34) at jetbrains.buildServer.buildTriggers.vcs.VcsRootChangesLoader$RunLoadChanges.run(VcsRootChangesLoader.java:39) at jetbrains.buildServer.util.NamedThreadFactory.executeWithNewThreadName(NamedThreadFactory.java:89) at jetbrains.buildServer.buildTriggers.vcs.VcsRootChangesLoader.loadChanges(VcsRootChangesLoader.java:20) at jetbrains.buildServer.vcs.impl.VcsChangesFetcher$LoadChangesForRoot.run(VcsChangesFetcher.java:8) at jetbrains.buildServer.vcs.impl.VcsChangesLoaderImpl$ImmediateFutureExecService$1.call(VcsChangesLoaderImpl.java) at jetbrains.buildServer.serverSide.impl.ImmediateFuture.get(ImmediateFuture.java:59) at jetbrains.buildServer.serverSide.impl.ImmediateFuture.get(ImmediateFuture.java:68) at jetbrains.buildServer.vcs.impl.PeriodicChangesLoader.waitForTaskToComplete(PeriodicChangesLoader.java:13) at jetbrains.buildServer.vcs.impl.PeriodicChangesLoader.loadChanges(PeriodicChangesLoader.java:11) at jetbrains.buildServer.vcs.impl.VcsChangesLoaderImpl.tryLoadChanges(VcsChangesLoaderImpl.java:24) at jetbrains.buildServer.serverSide.impl.VcsModificationChecker$CollectChangesAction$1.run(VcsModificationChecker.java:0) at jetbrains.buildServer.util.NamedThreadFactory.executeWithNewThreadName(NamedThreadFactory.java:89) at jetbrains.buildServer.serverSide.impl.VcsModificationChecker$CollectChangesAction.run(VcsModificationChecker.java:2) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: jetbrains.buildServer.vcs.VcsOperationProgressRunner$VcsOperationException: java.lang.StringIndexOutOfBoundsException: String index out of range: -33 at jetbrains.buildServer.vcs.VcsOperationProgressProviderImpl.runWithProgress(VcsOperationProgressProviderImpl.java:29) at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.collectChangesWithProgress(LoadChanges.java:26) ... 21 more Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: -33 at java.lang.String.substring(String.java:1931) at com.codicesoftware.plugins.teamcity.PlasticVcsSupport$1.collectChanges(PlasticVcsSupport.java:284) at jetbrains.buildServer.vcs.utils.VcsPluginUtil.collectBuildChanges(VcsPluginUtil.java:63) at jetbrains.vcs.api.services.collectChanges.CollectRepositoryChangesPolicyFactory$8.collectChanges(CollectRepositoryChangesPolicyFactory.java:2) at jetbrains.vcs.api.services.collectChanges.SingleVersionCollectChangesCommand.collectChanges(SingleVersionCollectChangesCommand.java:1) at jetbrains.vcs.api.services.collectChanges.CollectChangesServiceProvider$1.collectChanges(CollectChangesServiceProvider.java:4) at jetbrains.buildServer.buildTriggers.vcs.LoadChanges$CollectChangesForCheckoutRules.call(LoadChanges.java:12) at jetbrains.buildServer.buildTriggers.vcs.LoadChanges$CollectChangesForCheckoutRules.call(LoadChanges.java:8) at jetbrains.buildServer.vcs.VcsOperationProgressProviderImpl.runWithProgress(VcsOperationProgressProviderImpl.java:27) ... 22 more jetbrains.buildServer.vcs.VcsOperationProgressRunner$VcsOperationException: java.lang.StringIndexOutOfBoundsException: String index out of range: -33 at jetbrains.buildServer.vcs.VcsOperationProgressProviderImpl.runWithProgress(VcsOperationProgressProviderImpl.java:29) at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.collectChangesWithProgress(LoadChanges.java:26) at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.collectChangesForCheckoutRules(LoadChanges.java:49) at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.collectChangesByCombinedRule(LoadChanges.java:11) at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.collectChanges(LoadChanges.java:34) at jetbrains.buildServer.buildTriggers.vcs.VcsRootChangesLoader$RunLoadChanges.run(VcsRootChangesLoader.java:39) at jetbrains.buildServer.util.NamedThreadFactory.executeWithNewThreadName(NamedThreadFactory.java:89) at jetbrains.buildServer.buildTriggers.vcs.VcsRootChangesLoader.loadChanges(VcsRootChangesLoader.java:20) at jetbrains.buildServer.vcs.impl.VcsChangesFetcher$LoadChangesForRoot.run(VcsChangesFetcher.java:8) at jetbrains.buildServer.vcs.impl.VcsChangesLoaderImpl$ImmediateFutureExecService$1.call(VcsChangesLoaderImpl.java) at jetbrains.buildServer.serverSide.impl.ImmediateFuture.get(ImmediateFuture.java:59) at jetbrains.buildServer.serverSide.impl.ImmediateFuture.get(ImmediateFuture.java:68) at jetbrains.buildServer.vcs.impl.PeriodicChangesLoader.waitForTaskToComplete(PeriodicChangesLoader.java:13) at jetbrains.buildServer.vcs.impl.PeriodicChangesLoader.loadChanges(PeriodicChangesLoader.java:11) at jetbrains.buildServer.vcs.impl.VcsChangesLoaderImpl.tryLoadChanges(VcsChangesLoaderImpl.java:24) at jetbrains.buildServer.serverSide.impl.VcsModificationChecker$CollectChangesAction$1.run(VcsModificationChecker.java:0) at jetbrains.buildServer.util.NamedThreadFactory.executeWithNewThreadName(NamedThreadFactory.java:89) at jetbrains.buildServer.serverSide.impl.VcsModificationChecker$CollectChangesAction.run(VcsModificationChecker.java:2) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: -33 at java.lang.String.substring(String.java:1931) at com.codicesoftware.plugins.teamcity.PlasticVcsSupport$1.collectChanges(PlasticVcsSupport.java:284) at jetbrains.buildServer.vcs.utils.VcsPluginUtil.collectBuildChanges(VcsPluginUtil.java:63) at jetbrains.vcs.api.services.collectChanges.CollectRepositoryChangesPolicyFactory$8.collectChanges(CollectRepositoryChangesPolicyFactory.java:2) at jetbrains.vcs.api.services.collectChanges.SingleVersionCollectChangesCommand.collectChanges(SingleVersionCollectChangesCommand.java:1) at jetbrains.vcs.api.services.collectChanges.CollectChangesServiceProvider$1.collectChanges(CollectChangesServiceProvider.java:4) at jetbrains.buildServer.buildTriggers.vcs.LoadChanges$CollectChangesForCheckoutRules.call(LoadChanges.java:12) at jetbrains.buildServer.buildTriggers.vcs.LoadChanges$CollectChangesForCheckoutRules.call(LoadChanges.java:8) at jetbrains.buildServer.vcs.VcsOperationProgressProviderImpl.runWithProgress(VcsOperationProgressProviderImpl.java:27) ... 22 more java.lang.StringIndexOutOfBoundsException: String index out of range: -33 at java.lang.String.substring(String.java:1931) at com.codicesoftware.plugins.teamcity.PlasticVcsSupport$1.collectChanges(PlasticVcsSupport.java:284) at jetbrains.buildServer.vcs.utils.VcsPluginUtil.collectBuildChanges(VcsPluginUtil.java:63) at jetbrains.vcs.api.services.collectChanges.CollectRepositoryChangesPolicyFactory$8.collectChanges(CollectRepositoryChangesPolicyFactory.java:2) at jetbrains.vcs.api.services.collectChanges.SingleVersionCollectChangesCommand.collectChanges(SingleVersionCollectChangesCommand.java:1) at jetbrains.vcs.api.services.collectChanges.CollectChangesServiceProvider$1.collectChanges(CollectChangesServiceProvider.java:4) at jetbrains.buildServer.buildTriggers.vcs.LoadChanges$CollectChangesForCheckoutRules.call(LoadChanges.java:12) at jetbrains.buildServer.buildTriggers.vcs.LoadChanges$CollectChangesForCheckoutRules.call(LoadChanges.java:8) at jetbrains.buildServer.vcs.VcsOperationProgressProviderImpl.runWithProgress(VcsOperationProgressProviderImpl.java:27) at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.collectChangesWithProgress(LoadChanges.java:26) at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.collectChangesForCheckoutRules(LoadChanges.java:49) at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.collectChangesByCombinedRule(LoadChanges.java:11) at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.collectChanges(LoadChanges.java:34) at jetbrains.buildServer.buildTriggers.vcs.VcsRootChangesLoader$RunLoadChanges.run(VcsRootChangesLoader.java:39) at jetbrains.buildServer.util.NamedThreadFactory.executeWithNewThreadName(NamedThreadFactory.java:89) at jetbrains.buildServer.buildTriggers.vcs.VcsRootChangesLoader.loadChanges(VcsRootChangesLoader.java:20) at jetbrains.buildServer.vcs.impl.VcsChangesFetcher$LoadChangesForRoot.run(VcsChangesFetcher.java:8) at jetbrains.buildServer.vcs.impl.VcsChangesLoaderImpl$ImmediateFutureExecService$1.call(VcsChangesLoaderImpl.java) at jetbrains.buildServer.serverSide.impl.ImmediateFuture.get(ImmediateFuture.java:59) at jetbrains.buildServer.serverSide.impl.ImmediateFuture.get(ImmediateFuture.java:68) at jetbrains.buildServer.vcs.impl.PeriodicChangesLoader.waitForTaskToComplete(PeriodicChangesLoader.java:13) at jetbrains.buildServer.vcs.impl.PeriodicChangesLoader.loadChanges(PeriodicChangesLoader.java:11) at jetbrains.buildServer.vcs.impl.VcsChangesLoaderImpl.tryLoadChanges(VcsChangesLoaderImpl.java:24) at jetbrains.buildServer.serverSide.impl.VcsModificationChecker$CollectChangesAction$1.run(VcsModificationChecker.java:0) at jetbrains.buildServer.util.NamedThreadFactory.executeWithNewThreadName(NamedThreadFactory.java:89) at jetbrains.buildServer.serverSide.impl.VcsModificationChecker$CollectChangesAction.run(VcsModificationChecker.java:2) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) I was able to reproduce it by installing a fresh version of the above mentioned software packages creating a new empty plastic scm repository creating a new TeamCity project with a VCS root that uses the newly created plastic repository creating a build configuration that uses the new VCS root run that build configuration -> TC should check for pending changes, do a server-side checkout, run your build now, add a new file to your repository, checkin the change re-run your teamcity build configuration => StringIndexOutOfBoundsException Seems to me like a bug introduced somewhere after 5.4.16.686, because downgrading Plastic SCM to 5.4.16.686 fixed that issue for me. Kind regards, Olaf
  10. User Voice: https://plasticscm.uservoice.com/forums/15467-general/suggestions/9888300-provide-a-setting-to-disable-drag-drop-in-pending
  11. Hello! I'm using the Visual Studio extension of Plastic SCM. In the "Pending changes in workspace" view dragging and dropping changed files is possible, which opens that file directly in Visual Studio. This feature might have been a good idea, but I'm starting to hate it. Every time when I try to select/click on of those files, I move my mouse a few pixels and drag&drop kicks in and opens that file, but my intention was to check/uncheck that file, not opening it. Either there should be an option to disable drag&dop, or the sensitivity of the drag&drop operation should be reduced to prevent such mistakes. Is there such an option? Otherwise I'm going to add a request to user voice. Kind regards, Olaf
  12. Amarok

    Client Version Doesnt Match Visual Studio

    Hello! We had the same problem. This happens when you have VS2012 with 4.1 Visual Studio integration pack and run the NET4 5.0 Plastic Installer without uninstalling 4.1 manually before. Therefore, it is recommended to uninstall 4.1 first. To fix the problem you can use following steps: Uninstall Plastic SCM client Open the Developer Command Prompt for your Visual Studio version Run "vsixinstaller /uninstall:774e58ba-f1b9-40a7-b676-834fa2c220fe" (run from VS2012 developer command prompt) Install Plastic SCM client again; now, the setup should be able to install the new Visual Studio integration package Kind regards, Olaf
  13. Amarok

    Teamcity plugin does some crazy stuff

    Hello! The new plugin works as expected. TeamCity shows plugin version SNAPSHOT-201310221608. Thanks for fixing that! Olaf
  14. Amarok

    Teamcity plugin does some crazy stuff

    Hi! I can confirm that it is not fixed. We still see the same problem with latest 4.1.10.493 and TeamCity 8.0.3 on all builds. Checking for changes [10:28:39]Publishing internal artifacts [10:28:39][Publishing internal artifacts] Sending build.start.properties.gz file [10:28:39]Clearing temporary directory: D:\TEAMCITY\temp\buildTmp [10:28:39]Checkout directory: D:\TEAMCITY\work\d36c7ecd7ed2b398 [10:28:39]Updating sources: server side checkout (51s) [10:28:39][Updating sources] Will perform clean checkout. Reason: The project sources on the agent are newer than requested [10:28:39][Updating sources] Building clean patch for VCS root: Desktop_Platform_main [10:29:03][Updating sources] Repository sources transferred: 73.71 MB total [10:29:03][Updating sources] Average transfer speed: 7.27 MB per second [10:29:03][Updating sources] Removing D:\TEAMCITY\work\d36c7ecd7ed2b398 [10:29:25][Updating sources] Updating D:\TEAMCITY\work\d36c7ecd7ed2b398 +1 Vote for fixing this
×