- In the pom file, update the
apigee.org
property undertest
andprod
POM profile to point to your Apigee org, or pass in a maven property namedapigeeorg
- The repo has a Jenkinsfile with the build info, so you can automatically import this repo using the Blue Ocean UI
- 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:
mvn test
- run linting, unit test and code coverage stepsmvn 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
forked from ssvaidyanathan/apigee-ci-cd
-
Notifications
You must be signed in to change notification settings - Fork 0
License
drush1980/apigee-ci-cd
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
About
No description, website, or topics provided.
Resources
License
Stars
Watchers
Forks
Releases
No releases published
Packages 0
No packages published
Languages
- JavaScript 87.5%
- Gherkin 12.5%