after the build (changeset) what is the delivery process?
after a team has completed a sprint, and we have the final approved changeset, and the builds are complete.. what is the process for packaging the deliverable and making it available to the customer? Same discussion for defect (or collection of defects)..
our company has a completely automated process that takes the packaged items and moves them thru the distribution process. Are there RTC addons that will allow me to select the workitems/changesets and drive those processes? (take the installanywhere build script, execute it, make the distro file for each OS, windows, linux, aix, solaris, ..., then load them into our distribution system).. products go into one hopper and fixes go into another. can I make new process UI panels to add to the release/defect to support this? Sam |
One answer
Geoffrey Clemm (30.1k●3●30●35)
| answered Jul 15 '11, 12:20 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
The selection of which work items and change sets go into a particular
configuration (in RTC, a "stream") is done through the Pending Changes view (if you are using the Eclipse client). Once you have a desired configuration of the source in a stream, the process of building, packaging, and distributing is done through a "build" request (which is where you would define all of your various build/package/distribute scripts). Cheers, Geoff On 7/15/2011 10:23 AM, sdetweil wrote: after a team has completed a sprint, and we have the final approved |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.