How to deliver code to the repository

Hi Daniel,

I'll give it a try.

You have streams and components in these streams. Each component can contain one or more eclipse projects.

Jazz SCM has Streams that are used for sharing code between several people. Jazz SCM has Repository workspaces used to contain code for one workspace e.g. of one person.

Getting code shared with a team is two stages. A repository workspace is synced with an Eclipse worspace via check-in which can be automated (preferences). To expose your changes to the team you deliver the outgoing changes (your changed code) from your repository workspace to the stream that is the current flow target of your repository workspace. All repository workspaces with that stream as current flow target will see the changes delivered.

Changes delivered to the stream not in a repository workspace are showed as incoming and can be accepted to be brought in when appropriate.

Changes form one stream are brought to another by changing the current flow target of a repository workspace containing the changes to another stream.

Thats about it. There are several articels around and some help in the tool also. See also
http://jazz.net/library/video/100
http://jazz.net/library/article/115
http://jazz.net/library/article/40

Ralph

Hi,

I'm new so bear with me if this has an obvious answer.

I've created 3 components shared in 2 streams. Each of the components represent a project, and the streams represent development and certification. By changing the target, I can check code in from my workspace to development and then certification.

What I'm not sure of is how the code eventually makes it to the repository? My thought was each stream was like a branch and the repository is the main-line, but I can't figure out how to deliver code to the main-line.

Am I on the wrong path?

Thanks,
Deege

You are close.
But there is no special "main line" ... the main line is just a stream
that you have selected as acting as the main line for your project.

Note that terminologically, you "check in" changes to a repository
workspace, and you "deliver" changes from a repository workspace to a
stream.

Both check-ins and delivers make change to the "repository".


deege wrote:

Hi,

I'm new so bear with me if this has an obvious answer.

I've created 3 components shared in 2 streams. Each of the components
represent a project, and the streams represent development and
certification. By changing the target, I can check code in from my
workspace to development and then certification.

What I'm not sure of is how the code eventually makes it to the
repository? My thought was each stream was like a branch and the
repository is the main-line, but I can't figure out how to deliver
code to the main-line.

Am I on the wrong path?

Thanks,
Deege

You are close.
But there is no special "main line" ... the main line is just a stream
that you have selected as acting as the main line for your project.

Note that terminologically, you "check in" changes to a repository
workspace, and you "deliver" changes from a repository workspace to a
stream.

Both check-ins and delivers make change to the "repository".

Thanks. So this means I need to create a third "main-line" stream then?

Yes.

Cheers,
Geoff

deege wrote:

gmclemmwrote:
You are close.
But there is no special "main line" ... the main line is
just a stream
that you have selected as acting as the main line for your project.

Note that terminologically, you "check in" changes to a
repository
workspace, and you "deliver" changes from a repository
workspace to a
stream.

Both check-ins and delivers make change to the
"repository".

Thanks. So this means I need to create a third "main-line"
stream then?