Jump to content

Search the Community

Showing results for tags 'windows'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Plastic SCM
    • General
    • Installation and configuration
    • Unity 3D
    • 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

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 8 results

  1. 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
  2. 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
  3. I've installed Plastic v6.0.16.1395 on a Windows 10 VM running on Mac - Accepted the default settings (including to use Jet back-end) and installation all went fine. I've started up the Plastic client, gone to create first repo, and I get an error which - strangely - references the Firebird backend: "...server wasn't able to open a connection to the database ... Error: The type initializer for 'FirebirdSql.Data.Common.Charset" threw an exception." I had an old installer on another machine for v6.0.16.1307 which I've installed successfully on another Windows 10 machine - so I uninstalled 1395, then installed 1307, but with the same result. Any ideas? Thanks, Steve. Additional info: I'm guessing this issue may be related to running Windows in a VM - if I change the server name from the suggested "Ghost.local:8087" to "localhost:8087", the repo is created successfully. But I still cannot progress any further without hitting the same database error.
  4. Hello guys, I have a Unity project and meet with an issue that you probably will be interested. 1) I had a class with name Leftpanel.cs and checked in it to the changeset 2) Later I changed my mind and changed class name to LeftPanel in Unity3D I had to rename the filename too so I renamed it to LeftPanel.cs 3) Plastic client did not recognize it and saved changes again to Leftpanel.cs 4) After downloading of change set contents I received file Leftpanel.cs and therefore my project became broken. How to fix. 1) Remove file from project, copy file to some other location. 2) checkin 3) Copy file back 4) checkin I use server: PlasticSCM-5.4.16.712-linux-client-binaries Client: PlasticSCM-5.4.16.749
  5. TLDR: How might we migrate from our OSX team server and all of it's repositories, branches, etc to a new windows machine? I can't find any cross platform migration tips. The PlasticSCM Server for OSX, in a word, Sucks. While the client has gotten MUCH better in the last year, the server is a total PITA when something goes wrong. There are essentially no docs or guides specific to very mundane and regular CLI admin issues such as: replacing the token (running through server config and specifying a new token doesn't do it, yay), there is no GUI client for admin, etc. etc. After wasting days on several occasions for support to get back to us, or trying to piece things together from the forums, and then verify that they apply to the newer versions of plastic, we're considering migration of our repos to a windows server so we can actually USE the docs, and gui admin client etc. I'll start speccing a new server machine while I wait for I don't know how long for support to answer my last ticket about our license issue. One more day of labor wasted by a new employee because he can't pull our project down Andrew
  6. I have been using Plastic as a client for some time now and like it a lot. Last year I set up a server on an OSX machine and, after a few hiccups with connections across multiple versions of the software, there was no problem setting up a server. However, I've tried to set up a server on two Windows machines now, a Windows 7 machine and an 8.1 machine, and both machines are causing me problems that I can't seem to solve with a simple Google search (or twelve). After configuring the server with the desired settings, I try to check plasticd status, and get "Cannot start service from the command line or a debugger. A Windows Service must first be installed (using installutil.exe) and then started with the ServerExplorer, Windows Services Administratice tool of the NET START command." Command line reads a whole lot of "log4net : ERROR [FileAppender] Unable to acquire lock on file *.log.txt. Access to the path is denied." so I'm not getting any log info either. I tried using installutil but that won't work either. As I write this it occurs to me that this feels reminiscent of issues I've experienced with installing stuff in Program Files... but if that's the problem, I don't believe I changed the default install directory, and it chose to put itself in Program Files. I'll attempt to install the whole shebang in root C: later but until then, acting under the assumption that this alone won't be the solution, maybe someone has some insight? Thanks!
  7. LoganBarnettASU

    Cross-platform Client-side triggers

    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
  8. I would like to ask if it would be possible to add a feature for when I right click on a workspace in PlasticSCM, I'd like to see an option to "Open workspace folder in Windows Explorer". Is this something that could be included? Low priority, but would be a nice feature.
×