Announcements
The Google Cloud Community will be in read-only from July 16 - July 22 as we migrate to a new platform; refer to this community post for more details.
Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

Issue while deploying proxy via maven jenkins however proxy getting deployed successfully through GUI

Not applicable

Team,

We are facing issue while deploying "Authentication" proxy via maven through jenkins. Changes done in assign message AM-Set-Profile-Exist-Status.xml policy that is in "Authentication" proxy is as below:-

AM-Set-Profile-Exist-Status.xml was existing policy and "Authentication" was existing proxy and very minimal changes were done in the policy that is removed <headers> tag from <remove> tag. and since then we are able to deploy the proxy via GUI directly but facing issues while deploying through maven jenkins.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<AssignMessage async="false" continueOnError="false" enabled="true" name="AM-Set-Profile-Exist-Status">
<DisplayName>AM-Set Profile Exist Status</DisplayName>
<AssignVariable>
<Name>emailId</Name>
<Ref>request.queryparam.emailId</Ref>
</AssignVariable>
<AssignVariable>
<Name>siteId</Name>
<Ref>request.header.X-bbb-site-id</Ref>
</AssignVariable>
<Add>
<FormParams>
<FormParam name="arg1">{emailId}</FormParam>
<FormParam name="arg2">{siteId}</FormParam>
</FormParams>
</Add>
<Remove>
<QueryParams>
<QueryParam name="emailId"/>
</QueryParams>
</Remove>
<AssignVariable>
<Name>request.verb</Name>
<Value>POST</Value>
</AssignVariable>
<IgnoreUnresolvedVariables>true</IgnoreUnresolvedVariables>
<AssignTo createNew="false" transport="http" type="request"/>
</AssignMessage>

Errors received while deploying proxy is as below:-

[ERROR] Failed to execute goal io.apigee.build-tools.enterprise4g:apigee-edge-maven-plugin:1.1.5:deploy (deploy-bundle) on project authentication: MojoExecutionException: 400 Bad Request
[ERROR] {
[ERROR] "code" : "rest.ValidationFailure",
[ERROR] "message" : "Error occurred while validation of bean AM-Set-Profile-Exist-Status.xml. Reason: - Unexpected Repository Error null.",
[ERROR] "contexts" : [ ]
[ERROR] }
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] <a href="http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException">http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException</a>
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // stage
[Pipeline] slackSend
run slackstepsend, step null:false, desc K0ZfD9Yqx1n83lj1ahxhSWOe:false
Slack Send Pipeline step configured values from global config - baseUrl: true, teamDomain: true, token: true, channel: true, color: false
ERROR: Slack notification failed. See Jenkins logs for details.
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
ERROR: script returned exit code 1
Finished: FAILURE
0 1 661
1 REPLY 1