Add a New Release
Releases are used to group together components that will be implemented at the same time. Components are associated with Releases as well as Assignments, though the relationship between a component and a Release may not be known for some time after an Assignment is created. ReleaseIDs must be defined before components can be associated with Releases.
A R – Add Release
Type A R (A space R) or ADD R on the Container List Command line to add a new Release. Or, if already at the Add/Create New Container screen, overtype the Container Type field from A for Assignment to R for Release.
Add Release
COMMAND ===>
Container Type R (A-Assignment, R-Release)
Description _________________________________________________
Release __________ (Unique Release Identifier)
Release Prefix ____ (Release Prefix )
Release Owner USER003_ (Defaults to user creating container)
Implementation Date __________ (YYYY-MM-DD )
Implementation Time ________ (HH:MM:SS )
Default Application PLAY____ (Owning Application for Release)
Default SubAppl PLAY____ (Sub Application)
Default Stream PLAY____ (Owning Stream for Release)
WORK REQ Ref. No. ________________________ (Optional)
Join Users N (Y-Join Users to Release)
Press ENTER to add/create the new Release, END to terminate
Release names
A release name is a 10-character Container Name and can either be user-specified (perhaps conforming to an organization’s naming standard) or system-generated.
User-specified Name—Enter the name in the Release field and leave the Release Prefix field blank.
System-generated Name—If the Code Pipeline Administrator has defined a Release Prefix, enter this Prefix into the Release Prefix field and leave the Release field blank. The system will generate a name as described in Assignment Names.
Other input fields
The following table describes the other input fields:
Field | Description |
|---|---|
Release Owner | Defaults to the UserID of the person creating the Release |
Implementation Date | Comment field for an implementation target date |
Implementation Time | Also a comment field |
Default Application | Main Application central to the Release |
Default SubApplication | Main SubApplication central to the Release |
Default Stream | Main Stream with which the Application is associated |
WORK REQ Ref. No. | Associates the Release with, for example, a problem ticket or PTF number. |
Join Users | Defaults to No. Use Y to immediately join other users to the new Release. |
Press Enter to create the Release Container.
Adding Tasks to Releases
To add new Tasks to a Release, see A-Add-Task. To add existing Tasks to a Release, see T-Transfer-Task.