Hi

We would like to have a structure as we have in SVN
but it is not like in SVN.

RTC is not SVN. It uses a different (albeit more flexible paradigm) for changeset based SCM. Coming from SVN it is probably best for you to read the RTC-SVN comparison in the library.

We also like to give the version number to the build engine in order to get a release according to the given component version? s there a way to pass the component version to the build?

Read through the RTC FAQ for builds first.
A build engine is just a demon listening for a build request. A build request is derived from a build definition. In a build definition, you can reference a workspace / stream. This object holds the configuration (e.g. component baselines) determining what goes into the build. Load rules in the build definition can furthermore determine if only certain components / component parts will be loaded for a particular build.

Good success,
Arne

WRT the structure, how you map it into RTC depends on what you are using
that structure for. Minimally, you are likely to want a stream for each
of your releases, i.e. streams ProjectA-1.0, ProjectA-1.1, ProjectA-1.2.

WRT passing a "version number" as Arne responded, you would store that
information in the build definition. In particular, in the build
definition for the ProjectA-1.0 stream would tell the build engine what
configuration to build by selecting the ProjectA-1.0 stream.

Cheers,
Geoff

On 7/12/2011 4:38 AM, canberk wrote:

Hi,

We would like to have a structure as we have in SVN:
-Stream-FT
*ProjectA
+Releases
-1.0
-1.1
-1.2

But we can't find a way to do it? We are always creating some baseline
and new versions but it is not like in SVN.

We also like to give the version number to the build engine in order
to get a release according to the given component version? s there
a way to pass the component version to the build?