Deploy fails if 'Environment Name' is empty

[ryanmurakami]

Reported earlier in #4, but perhaps it's something different now?

According to the documentation, Environment Name is an optional value. When leaving it blank with Jenkins version 2.47, it is failing the deployment entirely.

Does the documentation need to be updated, or is the implementation broken? If so, does anyone have a suggestion to bypass environment deployment after registering an application version without failing the step?

Here's the stack trace:
AWSEB Deployment Plugin Version 0.3.15
ERROR: Failed to parse POMs
java.io.IOException: Deployment Failure
at br.com.ingenieux.jenkins.plugins.awsebdeployment.AWSEBDeploymentBuilder.perform(AWSEBDeploymentBuilder.java:188)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)
at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.build(MavenModuleSetBuild.java:919)
at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:870)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
at hudson.model.Run.execute(Run.java:1728)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:405)
Caused by: java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException: Empty/blank environmentName parameter
at hudson.remoting.Channel$2.adapt(Channel.java:862)
at hudson.remoting.Channel$2.adapt(Channel.java:857)
at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55)
at br.com.ingenieux.jenkins.plugins.awsebdeployment.DeployerRunner.perform(DeployerRunner.java:66)
at br.com.ingenieux.jenkins.plugins.awsebdeployment.AWSEBDeploymentBuilder.perform(AWSEBDeploymentBuilder.java:184)
... 9 more
Caused by: java.lang.IllegalArgumentException: Empty/blank environmentName parameter
at org.apache.commons.lang.Validate.notEmpty(Validate.java:321)
at br.com.ingenieux.jenkins.plugins.awsebdeployment.cmd.DeployerCommand$ValidateParameters.perform(DeployerCommand.java:119)
at br.com.ingenieux.jenkins.plugins.awsebdeployment.cmd.DeployerChain.perform(DeployerChain.java:54)
at br.com.ingenieux.jenkins.plugins.awsebdeployment.SlaveDeployerCallable.call(SlaveDeployerCallable.java:42)
at br.com.ingenieux.jenkins.plugins.awsebdeployment.SlaveDeployerCallable.call(SlaveDeployerCallable.java:27)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:336)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
at ......remote call to CHELGCOJKS008(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1545)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:253)
at hudson.remoting.Channel$2.adapt(Channel.java:860)
... 13 more

[wallyhall]

+1

[rednikov]

+1

[hshiozawa]

I've found a workaround to skip the deployment process.

What we should do is to specify a name which actually doesn't exist on Application (like 'NOT_SPECIFIED_ENVIRONMENT') into 'Environment Name(s)'.

screenshot

details

If the plugin could not find a Environment ID which corresponds to the environment name on Application, the plugin skips the deployment process.

Please see below.

awseb-deployment-plugin/src/main/java/br/com/ingenieux/jenkins/plugins/awsebdeployment/cmd/DeployerCommand.java

Line 196 in 5a44d05

if (result.getEnvironments().size() < 1) {

[aldrinleal]

Ok. I'll add an option to skip environment updates