You could use IFileSystemView.compareAsWorkspaces to compare your
workspace to the stream. That can get you a list of different baselines.
Then you could compare baselines to get the changesets within the
baselines.

This should be effective for your general case where your workspace and
streams are similar; however, you could potentially hit performance issues
if you are comparing two vastly different targets.

Also, just a small technical correction. When there are multiple baselines
outgoing on the same component, and you do a 'deliver all', under the hood
you are not delivering 'multiple' baselines to the target. You are
delivering the top-most baseline that builds ontop of the ones below it.

On Thu, 16 Jul 2009 06:53:03 -0400, askankur
<ankshar4> wrote:

Hi all

Currently if there is some precondition written for a 'change set' (eg
there must be a workitem attached to it), it only applies when we
deliver the change set. But before delivering the change set to the
stream if I make a baseline of the component and include this change
set in the baseline and deliver the baseline, then the precondition
doesn't work i.e. the change set will be delivered as a child of
baseline without any workitem attached to it.
So I want to write the precondition for delivering the baselines, so
that all the change sets in the baselines have workitem attached to
them. My doubt is if one delivers more than one baseline for same
component in a single deliver operation, how to find all the change
sets under all those baselines which are being delivered in single
deliver operation ? Since API only provides the method to get a
single baseline per component.

Thanks
-Ankur

On Thu, 16 Jul 2009 10:53:03 +0000, askankur wrote:

Currently if there is some precondition written for a 'change set' (eg
there must be a workitem attached to it), it only applies when we
deliver the change set. But before delivering the change set to the
stream if I make a baseline of the component and include this change set
in the baseline and deliver the baseline, then the precondition doesn't
work i.e. the change set will be delivered as a child of baseline
without any workitem attached to it.

This is a known limitation, tracked here:

53173: When delivering baseline process rules are different than for individual change sets
https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/53173


--
Jared Burns
Jazz Process Team

Note that one workaround is to disallow the delivery of baselines, and
only allow the delivery of change sets.

Cheers,
Geoff

Jared Burns wrote:

On Thu, 16 Jul 2009 10:53:03 +0000, askankur wrote:
Currently if there is some precondition written for a 'change set' (eg
there must be a workitem attached to it), it only applies when we
deliver the change set. But before delivering the change set to the
stream if I make a baseline of the component and include this change set
in the baseline and deliver the baseline, then the precondition doesn't
work i.e. the change set will be delivered as a child of baseline
without any workitem attached to it.

This is a known limitation, tracked here:

53173: When delivering baseline process rules are different than for individual change sets
https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/53173

You can write a pre-condition which is run when you deliver a baseline.
What we've been discussing is how you would have such a pre-condition
validate something about all change-sets that are effectively being
delivered by delivering that baseline.

Logically, any rules that you have in place for validating delivery of
change sets should be applied to the delivery of baselines, since
logically a baseline is just a way of collecting a set of change sets,
and delivering them as a group. It would be prohibitively expensive
(and unnecessary) to run the check on every change set in the baseline,
since only the "new change-sets" in that baseline need to be checked
(i.e. change sets that aren't already in the stream you are delivering
to). But computing the list of new change-sets and applying change-set
rules to all of them can still be expensive, which is one of the issues
discussed in work item 53173 (and probably why that feature hasn't yet
been implemented).

So you could try to do that computation yourself, but that will be hard
for you to make acceptably efficient. So I believe that what is really
needed here is for the system to apply change-set deliver rules to
change sets delivered via baselines (i.e. work item 53173).

Cheers,
Geoff

askankur wrote:

Does that mean I can't write any precondition which checks while
delivering a baseline ? Basically 2nd half of my initial query is
still not answered. i.e. I want to write the precondition for
delivering the baselines, so that all the change sets in the
baselines have workitem attached to them. My doubt is if one delivers
more than one baseline for same component in a single deliver
operation, how to find all the change sets under all those baselines
which are being delivered in single deliver operation ? Since API
only provides the method to get a single baseline per component.