Solved: Apigee facing deployment issue with timestamp

avinayagam · 10-08-2017 06:19 PM

Hi Team,

I am using latest version of Maven and we have more than 300+ proxies in our environment. Though there are changes only on 1 or 2 proxies on our repository, every-time my maven plugin picks all the proxies and redeploy all the 300+ proxies. Is there any way we shall control this from apigee side to deploy only the changed proxies and skip rest of the proxies other than changing the plug-in code.

Regards

Arjun

ssvaidyanathan

Thanks @Dino

Along with what @Madhan Sadasivam mentioned, you can break it to build for a very specific proxy if you are using the module concept within Maven. For more info, please look into this doc which also provide an example.

Hope this clarifies. With the git commands (diff, log, etc), you can find the list of modules changed and then you can use that to call the corresponding module within maven to deploy

View solution in original post

DChiesa

@Sai Saran Vaidyanathan might know the answer to this.

madhans

Each API bundle will have a pom.xml like so,

https://github.com/apigee/apigee-deploy-maven-plugin/blob/master/samples/forecastweatherapi-recommen...

When a "mvn" command is run in the same folder only this API bundle will be deployed. You can build a script based on "git diff" to find the APIs that have changed and only run the deploy command for those APIs.

It looks like you have a script to deploy all API bundles on every merge (or when invoked manually). This can be used only when required.

ssvaidyanathan

Thanks @Dino

Along with what @Madhan Sadasivam mentioned, you can break it to build for a very specific proxy if you are using the module concept within Maven. For more info, please look into this doc which also provide an example.

Hope this clarifies. With the git commands (diff, log, etc), you can find the list of modules changed and then you can use that to call the corresponding module within maven to deploy