Gerald O Posted January 9, 2018 Report Share Posted January 9, 2018 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) Link to comment Share on other sites More sharing options...
calbzam Posted January 10, 2018 Report Share Posted January 10, 2018 Hello Gerald, We haven't been reported this issue before. Let me prepare a test scenario and I will let you know if the issue is reproducible or if we need more information. Regards, Carlos. Link to comment Share on other sites More sharing options...
calbzam Posted January 12, 2018 Report Share Posted January 12, 2018 Hi again, I was not able to reproduce any issue with: Plastic 7.0.16.1912 Bamboo: 6.3.0 (running on Ubuntu 14.04) plugin: 5.10.1 - If you create a new build configuration, is it easy to reproduce the problem when entering a custom "subdirectory" value? - Could you send us the build log and a snapshot of your configuration? You can reach as at support@codicesoftware.com. Regards, Carlos. Link to comment Share on other sites More sharing options...
Gerald O Posted January 25, 2018 Author Report Share Posted January 25, 2018 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. Link to comment Share on other sites More sharing options...
calbzam Posted February 2, 2018 Report Share Posted February 2, 2018 We are debugging the issue via support thread. I will update this post with the results. Regards, Carlos. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.