Chemi wrote:

Hi, I am playing around with following scenario: I have different
development streams for different teams, each one using its own SCM
component. And I have an integration single stream for all of them with
all SCM components.

As nightly and continuous build I would like to refresh automatically
integration stream's components with the content of same components in
each development stream. The way I found to do it, is manually point all
repositories workspace to integration stream and deliver change sets.
Another manual way to do it is open integration stream and replace each
component with current baseline of each development stream.

But I would like an automatically way to do it from the build script.
BTW, all development streams flow to the integration stream in its
definition but nothing happens (it seems it is a descriptive filed
instead a functional one).

Amy help or suggestion?

Thanks in advance,

Chemi.

Further investigation shows me this article:
http://jazz.net/library/article/195

What I need is "Recipe 2: Promoting Changes to Another Stream When a
Build Succeeds" but I am wondering if I can deliver directly from stream
A to stream B without passing the change sets through a temporal
repository workspace. Is it possible?

Thanks,

Chemi.

rschoon wrote:

Hi Chemi,

as far as I know you can't. The flow target in a stream is for
documentation. You always use a repository workspace load that from
one stream, switch to the other stream, integrate the changes, test
and deliver there.


Ralph

I follow those steps when doing manually. But I thought via SCM CLI
could be more direct (although internally SCM CLI could be doing such
steps). But I don't see how... so it seems I need to follow those steps
also when doing from SCM CLI.

Thanks,

Chemi.

Chemi wrote:

rschoon wrote:
Hi Chemi,

as far as I know you can't. The flow target in a stream is for
documentation. You always use a repository workspace load that from
one stream, switch to the other stream, integrate the changes, test
and deliver there.


Ralph

I follow those steps when doing manually. But I thought via SCM CLI
could be more direct (although internally SCM CLI could be doing such
steps). But I don't see how... so it seems I need to follow those steps
also when doing from SCM CLI.

Thanks,

Chemi.

Nope! I was wrong... "scm deliver" supports delivers between streams
without passing through a temporal repository workspace:
http://publib.boulder.ibm.com/infocenter/rtc/v2r0m0/index.jsp?topic=/com.ibm.team.scm.doc/topics/r_scm_cli_deliver.html

I have tested successfully.

Regards,

Chemi.

On 11/11/2009 6:17 PM, Chemi wrote:

Chemi wrote:
Nope! I was wrong... "scm deliver" supports delivers between streams
without passing through a temporal repository workspace:
http://publib.boulder.ibm.com/infocenter/rtc/v2r0m0/index.jsp?topic=/com.ibm.team.scm.doc/topics/r_scm_cli_deliver.html


I have tested successfully.

Regards,

Chemi.

Interesting, this worked fine with RTC 2.0.0.1

Right now, I am trying to do the same with RTC 2.0.0.2 iFix2 and I get
following error:

Delivering changes from "Java EE Development" into "Global
Development"
No baselines to flow.
Problem running 'deliver':
Cannot flow components via command line interface.
Result: 19

Any idea? Could it be a regression problem? Or it shouldn't work and in
2.0.0.1 was an unexpected behavior?

Thanks in advance,

Chemi.

Still doing tests with no success.

The piece of code that worked in 2.0.0.1 was (stream to stream) and it
is failing now in 2.0.0.2 iFix2:

<exec>
<arg>
<arg>
<arg>
<arg>
<arg>
<arg>
<arg>
<arg>
<arg>
<arg>
<arg>
<arg>
</exec>

And I received:

Delivering changes from "Java EE Development" into "Global
Development"
No baselines to flow.
Problem running 'deliver':
Cannot flow components via command line interface.
Result: 19

Then, I have changed the code to deliver from the build repository
workspace like this:

<exec>
<arg>
<arg>
<arg>
<arg>
<arg>
<arg>
<arg>
<arg>
<arg>
<arg>
<arg>
<arg>
<arg>
<arg>
</exec>

And I receive:

Delivering changes from "Java EE Build Workspace" into "Global
Development"
Baselines to flow:
Component "Web Interface App" baseline 26 -
"nightly.demoweb.build_20100618-0846"
Comment: Snapshot created by automated build
Problem running 'deliver':
Cannot flow components via command line interface.
Result: 19

Why is it trying to deliver a component??? The component specified in -C
argument already exists in the target stream. As I understand the SCM
CLI command, it should deliver the changes of the specified component.
Not deliver a component itself. Right?

I am going to try upgrading to 2.0.0.2 iFix3 but meanwhile... any help
on this?

Thanks in advance,

Chemi.

Still doing tests with no success.

The piece of code that worked in 2.0.0.1 was (stream to stream) and it
is failing now in 2.0.0.2 iFix2:

_exec executable="${scm.home}/scm.exe">
_arg value="deliver" />
_arg value="-r" />
_arg value="${jazz.url}" />
_arg value="-u" />
_arg value="${userId}" />
_arg value="-P" />
_arg value="build" />
_arg value="-v" />
_arg value="-s" />
_arg value="${source.stream}" />
_arg value="-t" />
_arg value="${target.stream}" />
_/exec>

And I received:

Delivering changes from "Java EE Development" into "Global
Development"
No baselines to flow.
Problem running 'deliver':
Cannot flow components via command line interface.
Result: 19

Then, I have changed the code to deliver from the build repository
workspace like this:

_exec executable="${scm.home}/scm.exe">
_arg value="deliver" />
_arg value="-r" />
_arg value="${jazz.url}" />
_arg value="-u" />
_arg value="${userId}" />
_arg value="-P" />
_arg value="build" />
_arg value="-v" />
_arg value="-s" />
_arg value="${source.workspace}" />
_arg value="-t" />
_arg value="${target.stream}" />
_rg value="-C" />
_arg value="Web Interface App" />
_/exec>

And I receive:

Delivering changes from "Java EE Build Workspace" into "Global
Development"
Baselines to flow:
Component "Web Interface App" baseline 26 -
"nightly.demoweb.build_20100618-0846"
Comment: Snapshot created by automated build
Problem running 'deliver':
Cannot flow components via command line interface.
Result: 19

Why is it trying to deliver a component??? The component specified in -C
argument already exists in the target stream. As I understand the SCM
CLI command, it should deliver the changes of the specified component.
Not deliver a component itself. Right?

I am going to try upgrading to 2.0.0.2 iFix3 but meanwhile... any help
on this?

Thanks in advance,

Chemi.

After upgrading to iFix3 some problem, I decided to open a WI at
Jazz.net: Defect 118427

Regards,

Chemi.

On 6/18/2010 11:45 AM, Chemi wrote:

After upgrading to iFix3 some problem, I decided to open a WI at
Jazz.net: Defect 118427

Regards,

Chemi.

Fixed. It was a permission problem. I left the WI opened because I
understand the real problem is the error message then:

"Build user has no permission to deliver to target stream" instead of
"Cannot flow components via command line interface".

Regards,

Chemi.