It's all about the answers!

Ask a question

RTC 3.0.1 - Package and Deploy cycle


Donald Poulin (2249119107) | asked Jun 20 '11, 9:31 a.m.
If we create a 200 member package and a deployment based on that package and set the deployment to "Complete package" then when we deploy we copy 200 members to a destination. If we then just recompile 10 members and execute the package again and do the deploy again - do all 200 members get copied to the destination or just the 10 that actually changed? Trying to determine if the deploy function at "copy" time examines the list to see if all or only some need to be copied.

2 answers



permanent link
Hung Lam (2911915) | answered Jun 20 '11, 1:31 p.m.
JAZZ DEVELOPER
Currently in RTC 3.0.1, packaging can only package what's in the supplied shiplist.xml or work items. All members being packaged are recorded in a manifest file for each package. Deployment looks at this manifest file to deploy the members. If you want to package and deploy only the changes from last completed build, then you could:

1. Provided the work items that contains only the changes in the last build.
2. Create a shiplist.xml that contains only those members.

We already have a work item "create a package from a build result (167997)" to address your scenario.


If we create a 200 member package and a deployment based on that package and set the deployment to "Complete package" then when we deploy we copy 200 members to a destination. If we then just recompile 10 members and execute the package again and do the deploy again - do all 200 members get copied to the destination or just the 10 that actually changed? Trying to determine if the deploy function at "copy" time examines the list to see if all or only some need to be copied.

permanent link
Donald Poulin (2249119107) | answered Jun 21 '11, 5:46 a.m.
Thanks
Currently in RTC 3.0.1, packaging can only package what's in the supplied shiplist.xml or work items. All members being packaged are recorded in a manifest file for each package. Deployment looks at this manifest file to deploy the members. If you want to package and deploy only the changes from last completed build, then you could:

1. Provided the work items that contains only the changes in the last build.
2. Create a shiplist.xml that contains only those members.

We already have a work item "create a package from a build result (167997)" to address your scenario.


If we create a 200 member package and a deployment based on that package and set the deployment to "Complete package" then when we deploy we copy 200 members to a destination. If we then just recompile 10 members and execute the package again and do the deploy again - do all 200 members get copied to the destination or just the 10 that actually changed? Trying to determine if the deploy function at "copy" time examines the list to see if all or only some need to be copied.

Your answer


Register or to post your answer.