Undeliverable Change-set

Hi Dave,

Does your workspace have a flow target? To find out, open the Pending Changes view and look for grey text beside the name of your workspace. It should look something like:

My workspace <-> Name of some stream

The flow target defines where your changes get delivered to and and where you accept from. Without a flow target, the only thing you can do with a change-set is to complete it.

Add a flow target by right-clicking on the workspace and selecting 'Change Flow Target...'. That will provide you with a streams to collaborate with. You can also pop open the workspace editor and edit flow targets from there.


Hope that helps,
e

davidward@us.ibm.com wrote:

Hi

New to Jazz.

Following the Jazz Tutorial, the I've loaded some existing source into
my Repository Workspace and now I'm working on "Delivering Your Changes
to the Team".

Done the "Associate Work Item .." and thought I was ready to Deliver.

Right-clicking on the Change Set shows a menu with both Accept and
Deliver grayed out.

I'm running 0.6M3a on our Linux server and 0.6M3a TeamConcert client.

It's probably something simple that I've missed :-)

Dave

What menu items *can* you see?

Is there a chance your change-set is not checked in? Do you have the
auto check-in turned off in Window/Preferences/Team/Jazz Source Control?
-Paul

Hi Evan

Yes, I did have Flow Target. I'm just a little confused but I now see
what the problem was.

I was trying to checkin/deliver a complete source tree (for the first
time) to form my Initial Baseline. The source tree ' project' was in my
Eclipse workspace but the source itself was elsewhere (i.e. the Eclipse
project option to use a 'non-default' location was checked). The result
is that Eclipse only has project metadata in its workspace, not the actual
source (the source tree does appear in Eclipse navigator even though its
physically located elsewhere on the disk).

It seems that when I tried to place this project under Jazz Source
Control, Jazz only took 1 file from the top-level directory of the Eclipse
project (i.e. the .project file). The rest of source tree was ignored by
Jazz. I didn't notice that at the time. It should have taken 20 minutes
or so to complete this operation since there's quite a lot of source
(about 25000 files). It actually took 3 secs !!!

So, the change set was undeliverable because, as far as Jazz was
concerned, it had already been delivered !!! (remember, I am new to all
this).

I'm guessing, but shouldn't RTC have correctly picked up all the source in
the Eclipse project, even in the non-default-location case ?

Thanks for getting back






Hi Dave,

Does your workspace have a flow target? To find out, open the
Pending Changes view and look for grey text beside the name of your
workspace. It should look something like:

My workspace <-> Name of some stream

The flow target defines where your changes get delivered to and and
where you accept from. Without a flow target, the only thing you can
do with a change-set is to complete it.

Add a flow target by right-clicking on the workspace and selecting
'Change Flow Target...'. That will provide you with a streams to
collaborate with. You can also pop open the workspace editor and edit
flow targets from there.


Hope that helps,
e

Hi Paul See my other post about this

Hey, at least the performance was good!

But seriously, it sounds like something that should be addressed, so I
suggest you file a work item against this "feature".
-Paul
davidward@us.ibm.com wrote:

Hi Evan

Yes, I did have Flow Target. I'm just a little confused but I now see
what the problem was.

I was trying to checkin/deliver a complete source tree (for the first
time) to form my Initial Baseline. The source tree ' project' was in
my Eclipse workspace but the source itself was elsewhere (i.e. the
Eclipse project option to use a 'non-default' location was checked).
The result is that Eclipse only has project metadata in its workspace,
not the actual source (the source tree does appear in Eclipse navigator
even though its physically located elsewhere on the disk).

It seems that when I tried to place this project under Jazz Source
Control, Jazz only took 1 file from the top-level directory of the
Eclipse project (i.e. the .project file). The rest of source tree was
ignored by Jazz. I didn't notice that at the time. It should have
taken 20 minutes or so to complete this operation since there's quite a
lot of source (about 25000 files). It actually took 3 secs !!!

So, the change set was undeliverable because, as far as Jazz was
concerned, it had already been delivered !!! (remember, I am new to all
this).

I'm guessing, but shouldn't RTC have correctly picked up all the source
in the Eclipse project, even in the non-default-location case ?

Thanks for getting back






Hi Dave,

Does your workspace have a flow target? To find out, open the
Pending Changes view and look for grey text beside the name of your
workspace. It should look something like:

My workspace <-> Name of some stream

The flow target defines where your changes get delivered to and and
where you accept from. Without a flow target, the only thing you can
do with a change-set is to complete it.

Add a flow target by right-clicking on the workspace and selecting
'Change Flow Target...'. That will provide you with a streams to
collaborate with. You can also pop open the workspace editor and edit
flow targets from there.


Hope that helps,
e

Dave said:
> ...
> I'm guessing, but shouldn't RTC have correctly picked up
> all the source in the Eclipse project, even in the
> non-default-location case ?

It should have. I believe this bug has been filed: https://jazz.net/jazz/web/projects/Jazz%20Project#action=com.ibm.team.workitem.viewWorkItem&id=25133

I suggest leaving a note in the bug. It's always worth chiming in on a bug you want to see fixed.

Good idea. Took a look and it does seem to match my symptoms.

I'll add a comment to that bug now.

Thanks


Dave said:

...
I'm guessing, but shouldn't RTC have correctly picked up
all the source in the Eclipse project, even in the
non-default-location case ?

It should have. I believe this bug has been filed:
https://jazz.net/jazz/web/projects/Jazz%20Project#action=com.ibm.team.workitem.viewWorkItem&id=25133


I suggest leaving a note in the bug. It's always worth chiming in on a
bug you want to see fixed.