Closed awaqas closed 10 months ago
Can you provide the version you are using? Share the console output from your logs?
Did you also set the Maven proxy (.m2/settings.xml or exporting the variables)? In the logs, do you see the plugin using it?
The version used is 1.3.3 I cannot use the latest version we are still on the Apigee Edge. I have not set the .m2/settings. its set default by the jenkins server
And the connectivity is fine from the jenkins server, I can deploy the apiproxy using curl, curl_output_jenkins.LOG
I dont think the Maven settings is picking it. If it did you will see the logs print it
You should see that printed. I cannot find that in the logs you shared. So please check if its set.
I dont find any specific maven .m2/settings.xml on the readme pages. Is it the parent pom where we define the Profiles? This setting is read by the plugin to call the apigee. The same works on local, and it sometime work on Jenkins server aswell. Kindly can you guide which setting file to add? many thanks again
A kind reminder I am using the 1.3.3 version, the latest version do not support Apigee Edge :(
A kind reminder I am using the 1.3.3 version, the latest version do not support Apigee Edge :(
You are using the latest version of the plugin that works with Apigee Edge
I dont find any specific maven .m2/settings.xml on the readme pages. Is it the parent pom where we define the Profiles? This setting is read by the plugin to call the apigee. The same works on local, and it sometime work on Jenkins server aswell. Kindly can you guide which setting file to add? many thanks again
Its available in this link --> https://github.com/apigee/apigee-deploy-maven-plugin/tree/1.x#to-configure-a-proxy You will need to follow the steps provided to configure the proxy as described by Maven. The plugin just uses that as part of its executing.
did it work?
Closing this issue as there are no updates
Hello, I am using apigee maven plugin to deploy apiproxies. The builds are triggered from our Jenkins servers behind corporate firewall, so it there is a delay making a connection. It works sometimes but most of the time I receive Gateway Timeout 504 error. I tried from our jenkins servers using Curl command to create the apiproxy, this works fine but there is visible delay.
In the current implementation, the HttpClient ConnectTimeout and SocketTimeout are not configured. Kindly can you add this feature to configure these parms.
Thanks alot