How to build change sets from a stream - RTC source control

Question

The workspace in diagram below flows to a stream.

I've added a build definition which builds from this workspace. If I deliver change sets from a different workspace to the stream in diagram should these change sets be built when I perform a build ? Do the change sets need to be first accepted into the workspace from the stream before they are built ?

Currently when I perform a build the change sets(which have been delivered to the stream from a different workspace) are not being delivered to the workspace in diagram and so are not being built.

Answer 1

If I deliver change sets from a different workspace to the stream in diagram should these change sets be built when I perform a build?
Do the change sets need to be first accepted into the workspace from the stream before they are built?

It depends how your build definition is configured:
As this thread mentions:

If you are using a build definition that has 'Jazz Source Control' selected as a pre-build participant, you will see in the bottom section of the 'Jazz Source Control' tab the 'Accept Options section'.
The 'Accept latest changes before loading' checkbox should be checked for you to automatically accept changes.

But with a BuildForge-based Build Definition, as mentioned in "Rational Team Concert 3.0 and Build Forge: An integration scenario":

[...] Once a Server is selected, as first Step, the Build Forge project loads an Adaptor (JazzJBE.xml) to facilitate the integration between Build Forge and RTC.
This adaptor runs the Jazz Build Engine, which is part of the buildtoolkit, to accept and fetch source code based on the properties passed on by the RTC Build Definition
(A more typical continuous integration scenario with RTC would have the Jazz Build Engine running in the background on the build Server, listening for requests. With the JazzJBE adaptor, the Jazz Build Engine is launched on demand).