Create a Code Pipeline Project and Adding Files

Perform the following steps to create a project and add files to it. A Code Pipeline project is created based on one working path (life cycle level) but the path can be switched as described below. The Code Pipeline project displays the first version found of each component at one Code Pipeline-defined TEST level and above. In other words, if there are multiple versions in the life cycle, one version of the component that is the first one found at the Code Pipeline-defined TEST level and any levels in the path above it displays.

To create a project and add files to it

1. Do one of the following:
   • From the Repository Explorer view, right-click the application node and select Create Code Pipeline Project. The New Code Pipeline Project wizard appears.
   • From the File menu, select New>Project. The New wizard appears. Toggle open the BMC node, select Code Pipeline Project, and click Next. The New Code Pipeline Project wizard appears.
   • From the File menu, select New>Other. The New wizard appears. Toggle open the BMC node, select Code Pipeline Project, and click Next. The New Code Pipeline Project wizard appears.
   • In the Project Explorer view, right-click a Code Pipeline project and select New>Project. The New Project wizard appears. Toggle open the BMC node, select Code Pipeline Project, and click Next. The New Code Pipeline Project wizard appears.
2. From the Stream list, select the desired stream. From the Repository Explorer view, the default is the stream selected in the Repository Explorer view. From the New Code Pipeline Project wizard, the default is the last saved stream.
3. From the Application list, select the desired application, available under the selected stream. From the Repository Explorer view, the default is the application selected in the Repository Explorer view. From the New Code Pipeline Project wizard, the default is the last saved application.
4. From the SubAppl list, select the desired sub application, available under the selected application. From the Repository Explorer view, the default is the sub application selected in the Repository Explorer view. From the New Code Pipeline Project wizard, the default is the last saved sub application.
5. From the Path list, select the project's working path (the Code Pipeline-defined TEST level in the life cycle for the application). From the Repository Explorer view, the default is the working path selected in the Repository Explorer view. From the New Code Pipeline Project wizard, the default is the last saved working path.
6. Click Next. The Code Pipeline Project Filter page of the New Code Pipeline Project wizard appears to allow the user to filter the contents of the Code Pipeline project based on component type and/or component name.
7. Specify the filter criteria by doing either or both of the following:
   • To filter by component type, in the Types section, select the check boxes for the component types to be included in the filter.

   • To filter by component name, in the Names section, type the filter text in the field and click Add. Repeat for any additional component names on which to filter.

     Warning

     Important

     • A maximum of 25 component types can be selected and a maximum of 25 component names can be added.
     • Filter criteria is saved in the project's properties and can be modified and viewed on the of the Preference dialog box.
8. Click Finish. A project is created with all repository content in the selected application, stream, and working path, filtered based on any filter criteria that was entered. The project appears in the Project Explorer view in the format: <application> <stream> [<working path>].

To switch the project's working path

In the Project Explorer view, right-click the Code Pipeline project and select Code Pipeline>Switch Project Path. Then select the desired working path from the list of Code Pipeline-defined TEST levels in the life cycle for the application. The project content for the original working path is deleted and replaced with the content of the new working path. The Code Pipeline project in the Project Explorer view tree refreshes based on the new working path.