Confused about SCM root folder creation in automated build

Hi, I am running an automated build that fetches code from SCM and builds using a custom bash script. Basically I am confused why my SCM root folder is not getting created in the team.scm.fetchDestination. Let me explain my setup.

I have a stream called 'DevOps' with one component (also called 'DevOps'). It contains two Eclipse projects:

- com.ibm.devops.site
- com.ibm.tivoli.ops

I have a build definition that generates a web site from the contents of the first project (com.ibm.devops.site). It uses a custom repository workspace and a single load rule:

RootFolderName=/com.ibm.devops.site

The build definition's load directory is set to:

/home/jazz/jbe/working/devops.site

When I run the build, the load directory ends up with the contents of the com.ibm.devops.site project, but not the project folder itself. This is not causing any problems, but it will when I start to add additional folders.

Could you please explain what's happening here and if there's a way that the load directory will end up with the com.ibm.devops.site project folder rather than just its contents?

Hi, I am running an automated build that fetches code from SCM and builds using a custom bash script. Basically I am confused why my SCM root folder is not getting created in the team.scm.fetchDestination. Let me explain my setup.

I have a stream called 'DevOps' with one component (also called 'DevOps'). It contains two Eclipse projects:

- com.ibm.devops.site
- com.ibm.tivoli.ops

I have a build definition that generates a web site from the contents of the first project (com.ibm.devops.site). It uses a custom repository workspace and a single load rule:

RootFolderName=/com.ibm.devops.site

The build definition's load directory is set to:

/home/jazz/jbe/working/devops.site

When I run the build, the load directory ends up with the contents of the com.ibm.devops.site project, but not the project folder itself. This is not causing any problems, but it will when I start to add additional folders.

Could you please explain what's happening here and if there's a way that the load directory will end up with the com.ibm.devops.site project folder rather than just its contents?