Jump to content

Search the Community

Showing results for tags 'windows'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Plastic SCM
    • General
    • Installation and configuration
    • Unity 3D
    • Unreal Engine
    • Plastic SCM on Mac
    • Plastic SCM on Linux
    • Gluon
    • Git interop
    • Integrations
    • Community Edition
    • Branching and merging
    • Announcements
  • Plastic SCM 4.0 Beta (Closed)
  • Plastic Cloud
    • General
    • Configuration
  • SemanticMerge
    • General
    • License
    • SCM's configuration
    • Share your experience!
    • External Parsers
  • GitJungle
  • Method History for Subversion
  • PlasticX Early Adopter Program's General Feedback
  • PlasticX Early Adopter Program's Issue Reporting
  • PlasticX Early Adopter Program's Feature Requests
  • PlasticX Early Adopter Program's Announcements

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 5 results

  1. My build system consists of two Linux servers and one Windows server. One of the Linux servers runs the Atlassian Bamboo service (master). The other two machines (one Linux and one Windows) run Bamboo Remote Agents. Bamboo ist set up to run PlasticSCM operations (Check out, Branch handling) and works fine on the two Linux machines. When I run a build plan on the Windows remote agent then I get an error: simple 09-Nov-2017 10:40:07 Remote agent on host DESKTOP-B0AIIQS simple 09-Nov-2017 10:40:07 Build working directory is C:\bamboo-agent-home\xml-data\build-dir\OGS-CTP-JOB1 simple 09-Nov-2017 10:40:07 Executing build Ognerisk - ConfigToolPrototype - Default Job #45 (OGS-CTP-JOB1-45) simple 09-Nov-2017 10:40:07 Starting task 'Checkout Default Repository' of type 'com.atlassian.bamboo.plugins.vcs:task.vcs.checkout' simple 09-Nov-2017 10:40:07 Updating source code to revision: 208 simple 09-Nov-2017 10:40:07 Updating source code to revision: 208 simple 09-Nov-2017 10:40:08 Updating source code to revision: 208 error 09-Nov-2017 10:40:08 Error occurred while running Task 'Checkout Default Repository(1)' of type com.atlassian.bamboo.plugins.vcs:task.vcs.checkout. error 09-Nov-2017 10:40:08 java.lang.RuntimeException: com.atlassian.bamboo.repository.RepositoryException: Error creating workspace name OGS-CTP-JOB1_67868698-0adc-40a9-b0c2-a070644d4697 at C:\bamboo-agent-home\xml-data\build-dir\OGS-CTP-JOB1: There was a problem between the IDE and Plastic SCM communication through the console. Cannot run program "cm": CreateProcess error=2, Das System kann die angegebene Datei nicht finden error 09-Nov-2017 10:40:08 at com.atlassian.bamboo.executor.RetryingTaskExecutor.rerun(RetryingTaskExecutor.java:144) error 09-Nov-2017 10:40:08 at com.atlassian.bamboo.executor.RetryingTaskExecutor.runTask(RetryingTaskExecutor.java:88) error 09-Nov-2017 10:40:08 at com.atlassian.bamboo.executor.RetryingTaskExecutor.retry(RetryingTaskExecutor.java:203) error 09-Nov-2017 10:40:08 at com.atlassian.bamboo.executor.RetryingTaskExecutor.retry(RetryingTaskExecutor.java:188) error 09-Nov-2017 10:40:08 at com.atlassian.bamboo.plugins.vcs.task.VcsCheckoutTask.execute(VcsCheckoutTask.java:127) error 09-Nov-2017 10:40:08 at com.atlassian.bamboo.task.TaskExecutorImpl.lambda$executeTasks$3(TaskExecutorImpl.java:317) error 09-Nov-2017 10:40:08 at com.atlassian.bamboo.task.TaskExecutorImpl.executeTaskWithPrePostActions(TaskExecutorImpl.java:246) error 09-Nov-2017 10:40:08 at com.atlassian.bamboo.task.TaskExecutorImpl.executeTasks(TaskExecutorImpl.java:317) error 09-Nov-2017 10:40:08 at com.atlassian.bamboo.task.TaskExecutorImpl.executePreparationTasks(TaskExecutorImpl.java:93) error 09-Nov-2017 10:40:08 at com.atlassian.bamboo.build.pipeline.tasks.PrepareBuildTask.call(PrepareBuildTask.java:77) error 09-Nov-2017 10:40:08 at com.atlassian.bamboo.v2.build.agent.DefaultBuildAgent.build(DefaultBuildAgent.java:216) error 09-Nov-2017 10:40:08 at com.atlassian.bamboo.v2.build.agent.BuildAgentControllerImpl$1.call(BuildAgentControllerImpl.java:139) error 09-Nov-2017 10:40:08 at com.atlassian.bamboo.v2.build.agent.BuildAgentControllerImpl$1.call(BuildAgentControllerImpl.java:130) error 09-Nov-2017 10:40:08 at com.atlassian.bamboo.variable.CustomVariableContextImpl.withVariableSubstitutor(CustomVariableContextImpl.java:221) error 09-Nov-2017 10:40:08 at com.atlassian.bamboo.v2.build.agent.BuildAgentControllerImpl.waitAndPerformBuild(BuildAgentControllerImpl.java:129) error 09-Nov-2017 10:40:08 at com.atlassian.bamboo.v2.build.agent.DefaultBuildAgent$1.run(DefaultBuildAgent.java:138) error 09-Nov-2017 10:40:08 at com.atlassian.bamboo.utils.BambooRunnables$1.run(BambooRunnables.java:51) error 09-Nov-2017 10:40:08 at com.atlassian.bamboo.security.ImpersonationHelper.runWith(ImpersonationHelper.java:31) error 09-Nov-2017 10:40:08 at com.atlassian.bamboo.security.ImpersonationHelper.runWithSystemAuthority(ImpersonationHelper.java:20) error 09-Nov-2017 10:40:08 at com.atlassian.bamboo.security.ImpersonationHelper$1.run(ImpersonationHelper.java:52) error 09-Nov-2017 10:40:08 at java.lang.Thread.run(Unknown Source) error 09-Nov-2017 10:40:08 Caused by: com.atlassian.bamboo.repository.RepositoryException: Error creating workspace name OGS-CTP-JOB1_67868698-0adc-40a9-b0c2-a070644d4697 at C:\bamboo-agent-home\xml-data\build-dir\OGS-CTP-JOB1: There was a problem between the IDE and Plastic SCM communication through the console. Cannot run program "cm": CreateProcess error=2, Das System kann die angegebene Datei nicht finden error 09-Nov-2017 10:40:08 at com.codicesoftware.plugins.bamboo40.changesproviders.WorkspaceManager.doCreateWorkspace(WorkspaceManager.java:90) error 09-Nov-2017 10:40:08 at com.codicesoftware.plugins.bamboo40.changesproviders.WorkspaceManager.createWorkspace(WorkspaceManager.java:65) error 09-Nov-2017 10:40:08 at com.codicesoftware.plugins.bamboo40.changesproviders.PlasticContinuousIntegrationMode$1.call(PlasticContinuousIntegrationMode.java:94) error 09-Nov-2017 10:40:08 at com.codicesoftware.plugins.bamboo40.changesproviders.PlasticContinuousIntegrationMode$1.call(PlasticContinuousIntegrationMode.java:91) error 09-Nov-2017 10:40:08 at com.atlassian.util.concurrent.ManagedLocks$ManagedLockImpl.withLock(ManagedLocks.java:312) error 09-Nov-2017 10:40:08 at com.codicesoftware.plugins.bamboo40.changesproviders.PlasticContinuousIntegrationMode.updateWorkspace(PlasticContinuousIntegrationMode.java:90) error 09-Nov-2017 10:40:08 at com.codicesoftware.plugins.bamboo40.PlasticRepository.retrieveSourceCode(PlasticRepository.java:131) error 09-Nov-2017 10:40:08 at com.codicesoftware.plugins.bamboo40.PlasticRepository.retrieveSourceCode(PlasticRepository.java:114) error 09-Nov-2017 10:40:08 at com.atlassian.bamboo.vcs.configuration.legacy.LegacyWorkingCopyManager.retrieveSourceCode(LegacyWorkingCopyManager.java:137) error 09-Nov-2017 10:40:08 at com.atlassian.bamboo.plugins.vcs.task.VcsCheckoutTask.fillWorkingDirFromVcs(VcsCheckoutTask.java:228) error 09-Nov-2017 10:40:08 at com.atlassian.bamboo.plugins.vcs.task.VcsCheckoutTask.access$000(VcsCheckoutTask.java:53) error 09-Nov-2017 10:40:08 at com.atlassian.bamboo.plugins.vcs.task.VcsCheckoutTask$1.call(VcsCheckoutTask.java:132) error 09-Nov-2017 10:40:08 at com.atlassian.bamboo.plugins.vcs.task.VcsCheckoutTask$1.call(VcsCheckoutTask.java:128) error 09-Nov-2017 10:40:08 at com.atlassian.bamboo.executor.RetryingTaskExecutor.rerun(RetryingTaskExecutor.java:108) error 09-Nov-2017 10:40:08 ... 20 more error 09-Nov-2017 10:40:08 Failed to prepare the build 'Ognerisk - ConfigToolPrototype - Default Job #45 (OGS-CTP-JOB1-45)' simple 09-Nov-2017 10:46:05 Running on server: post build plugin 'NCover Results Collector' simple 09-Nov-2017 10:46:05 Running on server: post build plugin 'Build Hanging Detection Configuration' simple 09-Nov-2017 10:46:05 Running on server: post build plugin 'Clover Delta Calculator' simple 09-Nov-2017 10:46:05 Running on server: post build plugin 'Maven Dependencies Postprocessor' simple 09-Nov-2017 10:46:05 All post build plugins have finished simple 09-Nov-2017 10:46:05 Generating build results summary... simple 09-Nov-2017 10:46:05 Saving build results to disk... simple 09-Nov-2017 10:46:05 Logging substituted variables... simple 09-Nov-2017 10:46:05 Indexing build results... simple 09-Nov-2017 10:46:05 Finished building OGS-CTP-JOB1-45. I tried several suolution attempts regarding the path to the cm.exe (full path a.s.o.). cm.exe and the program folder are accessible by local system (bamboo agent service runs as local system). EDIT: Bamboo Version 5.15.3; PlastiscSCM: 5.4.16-802; Plugin 5.10.1
  2. I have the client installed in a docker for windows container. Everything seems to work except that the result of cm update is a workspace with ONLY directories and zero files. The same MSI ( on a VM hosting the container works correctly. This also happens within the container if the workspace is located on a mounted volume (i.e. NOT "in" the container). Is there something "extra special" that I am missing to run cm.exe inside a docker container (Windows)? info: PlasticSCM https://s3.eu-west-2.amazonaws.com/plastic-releases/releases/ Windows Server 2019 Datacenter 10.0.17763.0 mcr.microsoft.com/windows/servercore:ltsc2019
  3. Hello, My team is working in a mixed OS X and Windows environment. We want the triggers we make to work on both systems, but I suspect our problem is that the paths we're using aren't valid for both operating systems. $ cm listtriggers 2 Update art on update ruby /Users/atlantisremixed/.arx-plastic/update_art.rb LoganBarnett after-update The Ruby script we're running works great for both OS X and Windows when running standalone, but that path won't work for WIndows in the trigger so it doesn't even get to the Ruby script. What can I do to make my trigger platform agnostic? All of the examples in the PDF seem to prefer one platform or another, but never something universal. It would be nice if I could just do ~ for a home directory but I don't think that expands correctly. Perhaps I was doing that wrong? Thanks in advance! -Logan
  4. Hello everybody, I suddently have a problem with one of my Plastic SCM client on Windows. Everything worked well, but since last week I can't connect to my Plastic server anymore. Nothing changes in server config nor in my client config, but now I've got this message "The remote certificate is not valid according to the validation procedure" (see attached picture). The server has an attached domain with a valid, not expirated, certificate. But, as my client is on the same network as the server and as my box can't do loopback (domain name pointing to itself) I have an entry in my client host file to redirect domain name to local server IP address. This worked for more than 3 years without problem. The only thing that happened last week is that I used my PC out of office, so I removed the redirect line in my client host file in order to do my commit through "real" internet. This also worked properly. But a few hours later when I restarted Plastic from my office again (with local host redirection), it began to display the error message. Server and clients were in version, I updated my Windows client to but the problem did not disappear. Two other clients (on Mac) don't suffer from the problem and continu to reach the server without problem, locally or through internet. So my question is : is there a kind of certificate cache on Windows client ? ... Perhaps wrong data was cached when I came back to my office. I tried to clear windows ssl state in "internet options" but it had no effect. Any idea ?
  5. We have recently set up a project where a directory within that project is an xlink to another project. The files within this xlink are meant to never be edited, so we have the xlink on read-only. Whilst this is fine to prevent any changes to the files on source control, we need to enforce that our users cannot modify the files locally at all. Ideally this would be with a windows file lock applied recursively to the directory. Is there a convention for doing this within plastic? The closest idea I have is to use client-side triggers to file lock the directory, but I cant see a way of applying the trigger to a single repository? It feels like I am probably missing an element of Plastic SCM to solve this problem? Any help much appreciated! Thanks
  • Create New...