Bug 9593

Summary:	Enable workspace folder to be changed
Product:	[Yocto Project Subprojects] CROPS	Reporter:	Henry Bruce <henry.bruce>
Component:	crops-default	Assignee:	brian avery <brian.avery>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	Medium	CC:	sgw, tim.orling
Version:	2.1
Target Milestone:	2.2
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	Don't know

Description Henry Bruce 2016-05-04 23:35:26 UTC

Expected behavior
-----------------
Check out a project to /path/to/projectA. Configure CROPS to use that workspace. Work with project as expected. Check out a project to /different/path/to/projectB. Configure CROPS to use that workspace. Work with project as expected.

Observed behavior
-----------------
CROPS workspace is preset to $HOMEPATH/crops-workspace. Project must be in that folder before they can be built.

Comment 1 Todor Minchev 2016-06-17 18:26:19 UTC

This doesn't apply to crops-py. The crops installer is obsolete and won't be maintained going forward.

Comment 2 Todor Minchev 2016-06-23 17:57:30 UTC

reopening

Comment 3 Tim Orling 2016-06-23 19:45:58 UTC

The current plan for the eclipse-crops plugin is to spin up a new CROPS toolchain container for each workspace, perhaps even for each build. The host/container mapping would then be setup for each specific instance of running container. Or do we also want a CLI/RESTful API path for this?

Comment 4 brian avery 2016-10-24 22:13:01 UTC

This is fixed by using the samba containers and docker volumes. Bug 10452 is still needing to be done to fully flesh out the options but currently you can solve this by using subdirectories of the volume for different attached containers. within those subirectories, multiple workspaces function.