Jump to content

Gerald O

Members
  • Posts

    7
  • Joined

  • Last visited

Recent Profile Visitors

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

Gerald O's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. With this syntax I get an error that the config file is broken or corrupt. When I use [submodules] ignore.xLinkRepository -> configToolPrototype the error still occurs
  2. Carlos, thanks for your suggestion. I tried with this gitsync.conf [submodules] ignore.xLinkRepository -> configToolPrototype@plasticserver:8087 ignore.submoduleUrl -> https://my.gitserver/scm/mo/server_configtool.git https://my.gitserver/scm/mo/server_configtool.git -> configtoolPrototype@plasticserver:8087 writable:false relativeserver:false I also tried with writable:true and/or relativeserver:true But the error persists.
  3. Hi, i have a repo A that used a xlink to repo B in the past. When I try to gitSync to a git repo then the sync aborts with an error that says that a changeset <guid>@<repo B>@server:8087 does not exist. I also run a plastc gitserver and when I try to clone the repo then I get only the commits until the broken changeset and any newer changeset is omitted. I searched and found the changeset in repo A and when I try to "open" the changeset I get the same error: The specified changeset <guid>@<repo B>@server:8087 does not exist. since this changeset is pretty old and I don't need that anymore I tried to delete the changeset. But it is not possible. Is there a possibility to sync just the changes since a specific date? Or can I fix the broken xLink (any way to change the linked changeset guid)? Or is there a way to delete the changeset?
  4. My config: Bamboo 6.3.0 on Ubuntu 14.04 (tested with Ubuntu 16.04 as well but makes no difference) Plastic 6.0.16.1765 plugin 5.10.1 Here is my Task config in bamboo The working directory looks like as follows: the directories 'ognix', 'intercom_server', and 'embedded_server' are empty. Instead all files (from the last repo of the three, which is "embedded_server") are placed in the working directory root. I had a look at the working directory during the checkout process. When ognix (first) has been checked out, then all Sources of this repo wre in the working directory root. Same with intercom_server (ognix sources are deleted), and at the end emebedded_server files were checked out (intercom_server files removed) So easy steps to reproduce: define two or three repo on plastic with different content each On Bamboo create a plan with one job and one source code checkout task (plastic scm) In the task define 2 or 3 checkouts where every repo is checked out to a different directory run the plan check working directory. subdirs are created but empty. sources of the last repo remain in the working directory root Log 25-Jan-2018 15:01:13 Build Ognerisk - ARM Build - Build Embedded Stuff #1 (OGS-AB-BES-1) started building on agent Default Agent 25-Jan-2018 15:01:13 25-Jan-2018 15:01:13 Build working directory is /opt/bamboo-home/xml-data/build-dir/OGS-AB-BES 25-Jan-2018 15:01:13 Executing build Ognerisk - ARM Build - Build Embedded Stuff #1 (OGS-AB-BES-1) 25-Jan-2018 15:01:13 Starting task 'Checkout Default Repository' of type 'com.atlassian.bamboo.plugins.vcs:task.vcs.checkout' 25-Jan-2018 15:01:13 Checking out into /opt/bamboo-home/xml-data/build-dir/OGS-AB-BES/ognix 25-Jan-2018 15:01:13 Updating source code to revision: 2544 25-Jan-2018 15:04:46 Updated source code to revision: 2544 25-Jan-2018 15:04:46 Checking out into /opt/bamboo-home/xml-data/build-dir/OGS-AB-BES/intercom_server 25-Jan-2018 15:04:46 Updating source code to revision: 911 25-Jan-2018 15:06:31 Updated source code to revision: 911 25-Jan-2018 15:06:31 Checking out into /opt/bamboo-home/xml-data/build-dir/OGS-AB-BES/embedded_server 25-Jan-2018 15:06:31 Updating source code to revision: 61 25-Jan-2018 15:08:02 Updated source code to revision: 61 25-Jan-2018 15:08:02 Finished task 'Checkout Default Repository' with result: Success 25-Jan-2018 15:08:02 Running pre-build action: VCS Version Collector 25-Jan-2018 15:08:02 Running post build plugin 'NCover Results Collector' 25-Jan-2018 15:08:03 Running post build plugin 'Artifact Copier' 25-Jan-2018 15:08:03 Running post build plugin 'npm Cache Cleanup' 25-Jan-2018 15:08:03 Running post build plugin 'Clover Results Collector' 25-Jan-2018 15:08:03 Running post build plugin 'Docker Container Cleanup' 25-Jan-2018 15:08:03 Finalising the build... 25-Jan-2018 15:08:03 Stopping timer. 25-Jan-2018 15:08:03 Build OGS-AB-BES-1 completed. 25-Jan-2018 15:08:03 Running on server: post build plugin 'NCover Results Collector' 25-Jan-2018 15:08:03 Running on server: post build plugin 'Build Hanging Detection Configuration' 25-Jan-2018 15:08:03 Running on server: post build plugin 'Clover Delta Calculator' 25-Jan-2018 15:08:03 Running on server: post build plugin 'Maven Dependencies Postprocessor' 25-Jan-2018 15:08:04 All post build plugins have finished 25-Jan-2018 15:08:04 Generating build results summary... 25-Jan-2018 15:08:04 Saving build results to disk... 25-Jan-2018 15:08:04 Logging substituted variables... 25-Jan-2018 15:08:04 Indexing build results... 25-Jan-2018 15:08:04 Finished building OGS-AB-BES-1.
  5. I use Atlassian Bamboo as CI service together with PlasticSCM (tested plugin 5.6.2 and 5.10.1) When I configure a source code checkout task to checkout to a sub directory the directory is created but the source code remains in the working directory. When I use another source ode repo (like git) the option works well. Therefore I think there is a bug in the bamboo-plasticscm-plugin plastic version: 6.0.16.884 Bamboo: 6.3.0 (running on Ubuntu) plugin: 5.10.1 (tested with 5.6.2 as well)
  6. Thanks for the reply. PATH contains C:\Program Files\PlasticSCM5\client (system wide) I tied to run the service as a different user I copied the client.conf from the user space to the Program Files. Still same error.
  7. 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
×
×
  • Create New...