Can't deliver a changeset using scmtools deliver

I continue to explore the RTC's commandline interface using scmtools under Eclipse client and got stuck with another issue while tryig to deliver a changeset:

Deliver the changset 1023 to stream:
C:\scmtools_workspace\Operational Infrastructure Team Default Component\Jazz>lsm deliver 1023
Delivering changes from "scmtools_workspace" into "Operational Infrastructure Tam Stream"
No baselines to flow.
Process Reports:
Name: Deliver
Unable to find extension matching precondition id: com.ibm.team.process.delver.requireWorkItem. This typically means that a plugin is missing. In order for
this operation to run without this precondition, the team must configure it as"optional".
Operation failed because the above client side advisors are not yet compatible with the command line client. To fix this problem, edit the process specification and make each of them optional.
Problem running 'deliver':Delivery was blocked by process.

I don't see an option in scm Deliver for me to specify the work team id.

So I understand this is due to the fact that the CLI has not yet been able to hanlde deliver requiring work item.

Will this be solved in 3.0?


You first need to associate a workitem to a changeset and to do that run 'lscm changeset associate <changeset> <workitem>'. After that your deliver command should succeed.

I am not sure about the client side advisor not compatible with the command line client error.

WRT the error message:

There is server-side process and client-side process.
Apparently, the command line tool is not able to run client-side
process. So this means:
- You cannot enforce any client-side checks when using the command line
tool.
- You need to declare all client-side process for an operation to be
"optional" in order to perform that operation from the command line.

Because of this, most SCM process can now be declared as server-side
checks (how much depends on which version of the RTC server you are
running). So if you want to do the work item check, open up the process
editor, and see if your version of the RTC server lets this check be
done server-side, in which case you should enable the server-side check
and disable the client-side check.

Cheers,
Geoff


On 9/8/2010 12:22 AM, spadur wrote:

ghuwrote:
I continue to explore the RTC's commandline interface using scmtools
under Eclipse client and got stuck with another issue while tryig to
deliver a changeset:

Deliver the changset 1023 to stream:
C:\scmtools_workspace\Operational Infrastructure Team Default
Component\Jazz>lsm deliver 1023
Delivering changes from "scmtools_workspace" into
"Operational Infrastructure Tam Stream"
No baselines to flow.
Process Reports:
Name: Deliver
Unable to find extension matching precondition id:
com.ibm.team.process.delver.requireWorkItem. This typically means
that a plugin is missing. In order for
this operation to run without this precondition, the team must
configure it as"optional".
Operation failed because the above client side advisors are not yet
compatible with the command line client. To fix this problem, edit
the process specification and make each of them optional.
Problem running 'deliver':Delivery was blocked by process.



I don't see an option in scm Deliver for me to specify the work team
id.

So I understand this is due to the fact that the CLI has not yet been
able to hanlde deliver requiring work item.

Will this be solved in 3.0?

You first need to associate a workitem to a changeset and to do that
run 'lscm changeset associate<changeset> <workitem>'.
After that your deliver command should succeed.

I am not sure about the client side advisor not compatible with the
command line client error.

You first need to associate a workitem to a changeset and to do that run 'lscm changeset associate <changeset> <workitem>'. After that your deliver command should succeed.

I am not sure about the client side advisor not compatible with the command line client error.

Associate the changeset with work item doesn't work:
C:\scmtools_workspace\Operational Infrastructure Team Default Component\Jazz>lscm changeset associate 1023 45820
Link created.

C:\scmtools_workspace\Operational Infrastructure Team Default Component\Jazz>lsc
m deliver 1023
Delivering changes from "scmtools_workspace" into "Operational Infrastructure Team Stream"
No baselines to flow.
Process Reports:
Name: Deliver
Unable to find extension matching precondition id: com.ibm.team.process.deli
ver.requireWorkItem. This typically means that a plugin is missing. In order for this operation to run without this precondition, the team must configure it as "optional".
Operation failed because the above client side advisors are not yet compatible with the command line client. To fix this problem, edit the process specification and make each of them optional.
Problem running 'deliver':
Delivery was blocked by process.

WRT the error message:

There is server-side process and client-side process.
Apparently, the command line tool is not able to run client-side
process. So this means:
- You cannot enforce any client-side checks when using the command line
tool.
- You need to declare all client-side process for an operation to be
"optional" in order to perform that operation from the command line.

Because of this, most SCM process can now be declared as server-side
checks (how much depends on which version of the RTC server you are
running). So if you want to do the work item check, open up the process
editor, and see if your version of the RTC server lets this check be
done server-side, in which case you should enable the server-side check
and disable the client-side check.

Cheers,
Geoff

Hi, Geoff,
You are right. I see both server and client deliver under Source Control Operation Behavior in Team Configuration and the clien-side Deliver is checked with pre-condition of Descriptive Change set.

If we disable the client-side Deliver, enable the server-side one, I assume this won't cause any change/process block for deliver via Eclipse Client?

That is correct ... the client-side process has been kept for backward
compatibility for processes that were defined before the server-side
form is available. Whenever possible, use the server-side form of a
process check, so that it is run by all clients.

Cheers,
Geoff

On 9/8/2010 7:53 AM, ghu wrote:

gmclemmwrote:
WRT the error message:

There is server-side process and client-side process.
Apparently, the command line tool is not able to run client-side
process. So this means:
- You cannot enforce any client-side checks when using the command
line
tool.
- You need to declare all client-side process for an operation to be

"optional" in order to perform that operation from the
command line.

Because of this, most SCM process can now be declared as server-side

checks (how much depends on which version of the RTC server you are

running). So if you want to do the work item check, open up the
process
editor, and see if your version of the RTC server lets this check be

done server-side, in which case you should enable the server-side
check
and disable the client-side check.

Cheers,
Geoff




Hi, Geoff,
You are right. I see both server and client deliver under Source
Control Operation Behavior in Team Configuration and the clien-side
Deliver is checked with pre-condition of Descriptive Change set.

If we disable the client-side Deliver, enable the server-side one, I
assume this won't cause any change/process block for deliver via
Eclipse Client?

That is correct ... the client-side process has been kept for backward
compatibility for processes that were defined before the server-side
form is available. Whenever possible, use the server-side form of a
process check, so that it is run by all clients.

Cheers,
Geoff

Thanks, Geoff,
I modified the process cnfiguration and it is working now.