scm commadline - load (empty) workspace and accept of a baseline does not work
we are in the process of importing a lot of source code into RTC.
We are also having to set up a lot of builds.
This is RTC 3.0.1 and Build Forge, with custom adaptors etc.
The way things work best for us is to create the streams and build workspaces which are empty (set to Initial baseline).
Then we import source code and create a baseline.
When we run the initial build, the (empty) ws needs to be loaded and accept that initial baseline and that is where we have an issue.
I did reproduce what the adaptor is trying to do in a Linux shell
scm load MyBuild_wksp -r rtc_prod -d $HOME/MyBuild_wksp/myComp myComp
Nothing to load. Filesystem unmodified
scm accept -d $HOME/MyBuild_wksp/myComp -C myComp
Could not initialize data area:
Directory is not shared: $HOME/MyBuild_wksp/myComp
$HOME/MyBuild_wksp/myComp was created and has a .metadata directory
So the big question is: what do I need to change to make this work - Linux shell commands or scm commands.
it all works fine if the wksp has some content before the load, but making that happen is a lot of work we don't want to do as part of the import.
We are also having to set up a lot of builds.
This is RTC 3.0.1 and Build Forge, with custom adaptors etc.
The way things work best for us is to create the streams and build workspaces which are empty (set to Initial baseline).
Then we import source code and create a baseline.
When we run the initial build, the (empty) ws needs to be loaded and accept that initial baseline and that is where we have an issue.
I did reproduce what the adaptor is trying to do in a Linux shell
scm load MyBuild_wksp -r rtc_prod -d $HOME/MyBuild_wksp/myComp myComp
Nothing to load. Filesystem unmodified
scm accept -d $HOME/MyBuild_wksp/myComp -C myComp
Could not initialize data area:
Directory is not shared: $HOME/MyBuild_wksp/myComp
$HOME/MyBuild_wksp/myComp was created and has a .metadata directory
So the big question is: what do I need to change to make this work - Linux shell commands or scm commands.
it all works fine if the wksp has some content before the load, but making that happen is a lot of work we don't want to do as part of the import.
One answer
ok, I figured it out myself
running
scm accept -r rtc_prod -t MyBuild_wksp -C myComp
first and then the load gets around this.
I still think the original sequence should work though.
running
scm accept -r rtc_prod -t MyBuild_wksp -C myComp
first and then the load gets around this.
I still think the original sequence should work though.
Comments
Martina, there is a work item tracking this limitation. See SCM CLI: Cannot work with empty repository workspace... (158036) and its dup item.
The workaround you discovered is the recommended one.