GLYPH<SM590000> helmChartName  - default of ’ibm-ace-server-icip-prod’ GLYPH<SM590000> helmChartVersion  - default of ’1.1.2-icp4i-jenkins-01 GLYPH<SM590000> aceBaseImageName  - base IBM App Connect Docker image to build FROM (also used to  run container for BAR file build), defaults to ’ace-base-11004’ GLYPH<SM590000> aceBaseImageTag  - tag of IBM App Connect base image, default of latest 1. Sign in to your Jenkins server and on the home page click  New Item . See Figure 7-33 on  page 478. Chapter 7. Field notes on modernization for application integration  477 Downloads IBM App Connect application source code from a Git repository specified in the  applicationSourceRepoName  variable in the Jenkinsfile. Builds a BAR file from source code retrieved by pullSource.sh, by temporarily running an IBM  App Connect container locally on the Jenkins server with the source code mounted into that  container. Builds a new Docker image FROM the base image, adding in the BAR file built by barBuild.sh. Performs Helm deployment. A new values.yaml file is created for each deployment,  referencing the image made for the build. The secret containing the IBM App Connect  override-able information is currently hard coded in the values.yaml as ’ace-secret-dev’. These scripts perform two tests, one to ping the service’s admin port and one to make a  series of calls to the API by using curl. After you have installed the prerequisites and configured a solution to manage credentials to  your application source code repository, Docker registry and your Cloud Pak CLI tools you  can proceed to set up the example pipeline in Jenkins. pullSource.sh barBuild.sh deployChart.sh dockerBuild.sh pingService.sh and apiTest.sh Set up the pipeline in Jenkins