Using Code Pipeline for Eclipse with GIT

It is recommended that users review the Git to Code Pipeline Integration - A Tutorial to perform the Git to Code Pipeline integrations for the complete functionality. Below is the functionality that can be performed directly from within Code Pipeline for Eclipse.

Code Pipeline actions, such as performing a build or generate, can be performed for a GIT project. In order to perform Code Pipeline actions on a GIT project, the project must be imported from GitHub or Bitbucket into Eclipse, point to a valid YAML configuration file (ispwconfig.yml), and indicate the life cycle level of the project.

Refer to the Code Pipeline to GIT Integration: Code Pipeline YAML Configuration File for information on the available Code Pipeline property settings and path mappings that can be in the ispwconfig.yml file.

Important

Editing any project files does not update the mainframe files.

To configure the GIT project for Code Pipeline support

  1. From the Project Explorer view, right-click the GIT project's project node and select Configure>Configure to Use Code Pipeline. The following occurs:
    • If a YAML configuration file is not found at the root of the selected project, the Configure Code Pipeline and GIT Mapping wizard appears.If a YAML configuration file is found at the root of the selected, the wizard does not appear but, behind the scenes, the project nature is set so Code Pipeline actions can be performed on the projec Skip past the Configure Code Pipeline and GIT Mapping wizard step below.
  2. In the Configure Code Pipeline and GIT Mapping wizard, do one of the following to specify the YAML file to be used:

    • Select Create a new .yml file to create a new .yml file. Click Next, complete the fields, then click Finish. The YAML file is created and added to the root of the selected project in the Project Explorer view.

      Important

      Optionally, click Configure to configure a new host.

    • Select Use an existing .yml file, enter or browse to the location to use an existing YAML configuration file, then click Finish. By default, the YAML file will be copied to the root of the selected project and be renamed to ispwconfig.yml. Optionally, clear the Copy the file into the selected project check box to not copy the YAML file to the root of the project and not rename the file.

      If the GIT project contains files, path mappings are added to the YAML file based on those files. If the project does not contain files, default path mappings are added to the YAML file but may need to be revised for your site's Code Pipeline instance.
      If you configure a project to use the Code Pipeline project, SubAppl will be added automatically in ispwconfig.yml.

  3. From the Project Explorer view, right-click the GIT project's project node and select Properties>Code Pipeline. The Code Pipeline page of the Properties dialog box appears. The values shown for the host and port, runtime configuration, stream, application, sub application, and assignment prefix are prepopulated based on the YAML configuration file. The level value is required to perform any Code Pipeline action and must be entered manually.

    Important

    If you need the Assignment Prefix field to display a value in the Properties dialog box, you must manually add assignmentPrefix in the YAML file and assign the required value. This is an optional field and is used for the assignment creation.

  4. In the Level field, enter the life cycle level for the project (such as DEV1 or DEV2), which will be used to load the file into Code Pipeline at that level.
  5. Optionally, revise any of the properties.
  6. Click Apply and Close. Any property changes are updated in the YAML configuration file except for the level. The level is persisted for the project but not in the YAML configuration file.

Important

The YAML configuration file property settings can be edited at any time via the Properties dialog box.

Code Pipeline actions, such as loading files into a Code Pipeline container or performing a build or generate, can now be performed.

To load files into a Code Pipeline container

  1. Ensure that the GIT project is configured for Code Pipeline.

  2. From the Project Explorer view, right-click the desired GIT project files and select Code Pipeline>Load into Code Pipeline. 

    The selected files are loaded into a Code Pipeline container at the level set in the Code Pipeline properties. If the files were previously loaded at the specified level, the files are loaded to the same container, replacing the component in that container. If the files were not previously loaded at the specified level, the files are loaded to a new container. The Console view shows the container and level at which the component was loaded.

To copy Code Insight files into a Code Pipeline container

  1. From the Project Explorer view, right-click the desired Code Insight project files and select Code Pipeline>Copy to Code Pipeline.
  2. The selected files are copied into a Code Pipeline container at the level set in the properties. If the files were previously copied at the specified level, the files are copied to the same container, replacing the component in that container. If the files were not previously copied at the specified level, the files are copied to a new container. The Console view shows the container and level at which the component was copied.
  3. Select the files to copy. Optionally, you can select the following options and choose the required tasks type :
    • Click Change type and specify the type for the selected task.
    • Click Configure to specify the task type. Do any of the following in the Code Insights dialog box:
      • Select the Program type (for .cbl files) from the list.
      • Select the Copybook type (for .cpy files) from the list.
  4. In the Add to Assignment, perform the following actions:
    1. From the Assignment list, select the name of the assignment that contains or will contain this task. If Code Pipeline can determine the assignment based on the context, this field will be prepopulated; even so, the assignment can be changed, if desired. Optionally, do any of the following to select the assignment:
      1. Click <New> to select the newly created assignment.
      2. Click <Assignment View> to open the active assignment in the Assignment view.
      3. Click <Selected Tasks> to select the assignment of the selected tasks or component versions. 
      4. Click <Filtered> to select any assignment from the filtered list.
      5. Click Filter to open the assignments filter dialog box and enter criteria to filter the Assignment list.
      6. Click New to add a new assignment.

      7. Filter-the-Containers-View

        Important

        All the above prefixes are displayed only if they are applicable to the assignment.

        In the Assignment list, the <New>, <Assignment View>, <Selected Tasks>, and <Filtered> fields contain a prefix, assignment ID, and assignment description as shown in the following example:

        <Filtered> APPP000001 description
    2. From the Path list, select the checkout path or signout level.

    3. From the Release list, select the release to be used to associate logically related assignments. Tasks added to the assignment will default to this release.

      • Select <Default> to associate the task with the default release for the currently selected assignment. If the assignment has a default release, this is the default selection.
      • Select <Selected Tasks> to select the release of the selected tasks or component versions. 
      • Select <Release View> to open the release in the Release view.
      • Select <Filtered> to select any release from the filtered list.
      • Optionally, to filter the list of releases, click Filter to open the Releases Filter dialog box and enter criteria to filter the release list.
      • Optionally, click <New>, if desired, to add a new release.
      • Select <None> to not relate assignments to a release.

      Important

      • All the above prefixes are displayed only if they are applicable to the release.
      • An assignment can have tasks in different releases. 

      • In the Release list, the <New>, <Default>, <Selected Tasks>, <Release View>, and <Filtered> fields contain a prefix, release ID, and release description as shown in the following example:

        <Filtered> APPP000001 description
  5. Click OK.

To build impacted components

  1. Ensure that the GIT project is configured for Code Pipeline.
  2. From the Project Explorer view, right-click the desired GIT project tasks and select Code Pipeline>Build. The files are loaded into Code Pipeline and then the build process begins.
  3. See the Build topic for details on Code Pipeline's build functionality.

To generate

  1. Ensure that the GIT project is configured for Code Pipeline.
  2. From the Project Explorer view, right-click the desired GIT project tasks and select Code Pipeline>Generate. The files are loaded into Code Pipeline and then the generate process begins.
  3. See the Generate topic for details on Code Pipeline's generate functionality.

To generate with parms

  1. Ensure that the GIT project is configured for Code Pipeline.
  2. From the Project Explorer view, right-click the desired GIT project tasks and select Code Pipeline>Generate with Parms. The files are loaded into Code Pipeline and then the generate process begins.
  3. See the Generate topic for details on Code Pipeline's generate with parms functionality.

To generate with options

  1. Ensure that the GIT project is configured for Code Pipeline.
  2. From the Project Explorer view, right-click the desired GIT project tasks and select Code Pipeline>Generate with Options. The files are loaded into Code Pipeline and then the generate process begins.
  3. See the Generate topic for details on Code Pipeline's generate with options functionality.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*