Container List
Code Pipeline Option P displays the Code Pipeline Container List. The following figure shows the partial Container List associated with the user 'USER001'.
Container List for USER001
Command ===> Scroll ===> CSR
More -->
View: U Closed: N User: USER001_
Appl SubAppl T Container Tag Description
________ ________ _ __________ ____ ______________________________
__ PLAY PLAY A PLAY000004 TEST ASSEMBLER AND PLI
__ PLAY PLAY A PLAY000003 TEST COMPILES
__ PLAY PLAY A PLAY000002 IVP2 - TEST COMPILES
__ PLAY PLAY A PLAY000001 IVP1 - LOAD
__ PLAY PLAY S S000000006
__ PLAY PLAY S S000000005
__ PLAY PLAY S S000000004
__ SITE PLAY A SITE000002 IVP2 – IMPLEMENT
__ SITE PLAY A SITE000001 IVP1 – FIRST ASSIGNMENT
__ SITE PLAY S S000000003
__ SITE PLAY S S000000002
__ SITE PLAY S S000000001
------------------------------- Bottom of List -------------------------------
Container definition
A Container is a collections of components/modules that belong to an Application change request. Your organization may call these projects, work packages, or change requests. Code Pipeline has three types of Containers:
- Assignment – the most basic Container, used to help Applications staff structure and organize their project work.
- Release – a grouping of Assignment Containers (or Assignments) into a larger package, or a collection of modules from various Assignments.
- Set – a temporary Container used to bundle modules for mass operations such as authorizations, generations, or promotions from level to level.
Containers have Task Lists, where Tasks are the modules that need to be added, deleted, or changed for some particular piece of work.
Container type designations
In the example shown in the following figure, there are twelve work Containers associated with user USER002. By default, Code Pipeline users see only the Containers with which they are associated. Different Code Pipeline users will see different Container Lists, depending on their work. Notice the Container types designation in column T:
- The first nine rows are Assignments (A in the second column).
- The tenth row is a Release (R in the second column).
- The last two rows are Sets (S in the second column).
All of these containers belong to an Application called PLAY, which is listed in the Appl column.
The following figure shows a customized view of the Container List for user 'USER002'.
Container List for USER002
Command ===> Scroll ===> CSR
More -->
View: U Closed: N User: USER002_
Appl SubAppl T Container Tag Description
________ ________ _ __________ ____ ______________________________
__ PLAY PLAY A PLAY000007 USER002 TESTS #3
__ PLAY PLAY A PLAY000006 USER002 TESTS #2
__ PLAY PLAY A PLAY000005 USER002 TESTS #1
__ PLAY PLAY A PLAY000004 TEST ASSEMBLER AND PLI
__ PLAY PLAY A PLAY000003 TEST COMPILES
__ PLAY PLAY A PLAY000002 IVP2 - TEST COMPILES
__ PLAY PLAY A PLAY000001 IVP1 - LOAD
__ SITE PLAY A SITE000002 IVP2 – IMPLEMENT
__ SITE PLAY A SITE000001 IVP1 – FIRST ASSIGNMENT
__ PLAY PLAY R R5445 DEMO SYSTEM RELEASE
__ SITE PLAY S S000000002
__ SITE PLAY S S000000001
------------------------------- Bottom of List -------------------------------
The following table describes the Container List Columns:
Column | Description |
|---|---|
Appl | the Application or System this Container is associated with |
SubAppl | the SubApplication this container is associated with |
T | the type of Container (Assignment, Set, or Release) |
Container | the system-generated container number |
Tag | a user-definable 4-character field |
Description | a text field |
Owner | the UserID of the person who created the Container |
Release | used to group Containers together |
Path | the circuit or change cycle that the modules will transit through |
Stream | defines the level structure and other rules (including types, flags, and associations) about the application definition. |
WorkRef | an associated budget or change ticket number |
Codeline Path | a field used to identify a codeline |
Input fields color
In Code Pipeline, input fields, masks, and filters are displayed in a contrasting color. The default color is pink.
Filtering the Container List
A column filter can further narrow the Container List to specific Containers. The following figure shows Containers for user 'USER001' with Descriptions beginning with the word IVP. The filter IVP* (* = wildcard character) looks for descriptions beginning with the word IVP followed by any characters.
By using different filters you can further change the displayed results. Clearing all fields and filters will cause all of the Containers to be displayed. Try filters under various column headers, such as filtering on the Path column or the Description column.
Filtered Container List
Command ===> Scroll ===> CSR
More -->
View: U Closed: N User: USER001_
Appl SubAppl T Container Release Description
________ ________ _ __________ __________ IVP*___________________________
__ PLAY PLAY A PLAY000002 IVP2 - TEST COMPILES
__ PLAY PLAY A PLAY000001 IVP1 - LOAD
__ SITE PLAY A SITE000002 IVP2 – IMPLEMENT
__ SITE PLAY A SITE000001 IVP1 – FIRST ASSIGNMENT
------------------------------- Bottom of List -------------------------------
Arranging columns
Users can customize displays under Code Pipeline Main Menu Option U to show the information most important to them (see Option U – User Preferences). For example, QA staff may want to see different columns on their display than programmers. However these are just different logical views of the same data.