apigee-ci-cd

• In the pom file, update the apigee.org property under test and prod POM profile to point to your Apigee org, or pass in a maven property named apigeeorg
• The repo has a Jenkinsfile with the build info, so you can automatically import this repo using the Blue Ocean UI
  • Please configure the Apigee crendetials in Jenkins. The current Jenkinsfile uses apigee as the ID. If you wish to change that, please update the Jenkinsfile with the provided ID under the environment section - APIGEE_CREDS = credentials('apigee')
• Alternatively, if using Cloud Build the repo contains build configuration files that can be used
• If using the provided Cloud Build configuration file you should provide the following variable subsitutions in your build trigger settings:
  • _APIGEE_PROFILE - value should correspond to one of the profiles in the POM e.g. test, prod
  • _APIGEE_ORG - Apigee org name
  • _APIGEE_USER - Apigee admin account username
  • _APIGEE_PREFIX - optional value to use as a deployment suffix
• Additionally you should create a secret using Secret Manager named apigee-admin-pw containing the password corresponding to the _APIGEE_USER account
• When developing locally run the following commands to package, test and deploy:
  1. mvn test - run linting, unit test and code coverage steps
  2. mvn apigee-enterprise:configure apigee-enterprise:deploy -Ptest -Dapigeeorg={apigee org name} -Dusername={admin username} -Dpassword={admin password} - package and deploy the API proxy bundle
  • Running both of these commands will deploy a bundle with the local user name as the deployment suffix