dscorpian29
commented
6 years ago Hey I got it resolved thanks. That was a stupid mistake :)
Closed dscorpian29 closed 6 years ago
dscorpian29
commented
6 years ago Hey I got it resolved thanks. That was a stupid mistake :)
rajgaekwad
commented
5 years ago I too got the same problem in jenkins can you please let me know how to resolve
AWSEB Deployment Plugin Version 0.3.19 (aws-java-sdk version: 1.11.403) FATAL: Deployment Failure java.lang.IllegalArgumentException: Empty/blank versionLabel parameter at org.apache.commons.lang.Validate.notEmpty(Validate.java:321) at br.com.ingenieux.jenkins.plugins.awsebdeployment.cmd.DeployerCommand$ValidateParameters.perform(DeployerCommand.java:126) 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.LocalChannel$1.call(LocalChannel.java:52) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused: java.util.concurrent.ExecutionException at java.util.concurrent.FutureTask.report(FutureTask.java:122) at java.util.concurrent.FutureTask.get(FutureTask.java:192) at hudson.remoting.LocalChannel$2.get(LocalChannel.java:77) at br.com.ingenieux.jenkins.plugins.awsebdeployment.DeployerRunner.perform(DeployerRunner.java:71) at
aldrinleal
commented
5 years ago @rajgaekwad you haven't set your version label when configuring. thats the reason.
rajgaekwad
commented
5 years ago Hello Aldrin
Can you please let me where I can set the version label and send the detailed configuring jenkins and aws
On Tue, Nov 27, 2018 at 5:16 AM Aldrin Leal notifications@github.com wrote:
@rajgaekwad https://github.com/rajgaekwad you haven't set your version label when configuring. thats the reason.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ingenieux/awseb-deployment-plugin/issues/80#issuecomment-441843684, or mute the thread https://github.com/notifications/unsubscribe-auth/ArHFydUC0ooLCCy2-gb3rTkBdVSBxZqcks5uzH1ogaJpZM4U-ova .
-- Best Regards
Rajesh Gaekwad +919440487007 +918686318889
aldrinleal
commented
5 years ago https://wiki.jenkins.io/display/JENKINS/AWSEB+Deployment+Plugin
Setting up your Jobs ... As for Version Label Format, see some available variables on this url. ... https://wiki.jenkins.io/display/JENKINS/Building+a+software+project#Buildingasoftwareproject-below
Also, the help icon should show you the text below:
How to set the version label? For instance, for "${GIT_COMMIT}-${BUILD_TAG}", and with "Key Prefix" set to "myapp/builds/myapp-prod-env/", the S3 Object Key is set to myapp/builds/myapp-prod-env/4b5f7669b3376a1ce504bf7ef8bf7aeee9d21746-myjob-41.zip and the version Label will be 4b5f7669b3376a1ce504bf7ef8bf7aeee9d21746-myjob-41 on AWS EB Application Versions Bear in mind a prerequisite is understanding how AWS Elastic Beanstalk works. See https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/applications-versions.html for more details
rajgaekwad
commented
5 years ago Hello Aldrin
Thank you for helping me in this issue.
I wan to create auto instance using my AMI (images) Instances from Jenkins can you please help me out
On Tue, Nov 27, 2018 at 1:41 PM Aldrin Leal notifications@github.com wrote:
https://wiki.jenkins.io/display/JENKINS/AWSEB+Deployment+Plugin
Setting up your Jobs ... As for Version Label Format, see some available variables on this url. ...
https://wiki.jenkins.io/display/JENKINS/Building+a+software+project#Buildingasoftwareproject-below
Also, the help icon should show you the text below:
How to set the version label? For instance, for "${GIT_COMMIT}-${BUILD_TAG}", and with "Key Prefix" set to "myapp/builds/myapp-prod-env/", the S3 Object Key is set to myapp/builds/myapp-prod-env/4b5f7669b3376a1ce504bf7ef8bf7aeee9d21746-myjob-41.zip and the version Label will be 4b5f7669b3376a1ce504bf7ef8bf7aeee9d21746-myjob-41 on AWS EB Application Versions
Bear in mind a prerequisite is understanding how AWS Elastic Beanstalk works. See https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/applications-versions.html for more details
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ingenieux/awseb-deployment-plugin/issues/80#issuecomment-441965128, or mute the thread https://github.com/notifications/unsubscribe-auth/ArHFyd5Vn__hN2gQ-jhQBeOqWdVhYiRtks5uzPOqgaJpZM4U-ova .
-- Best Regards
Rajesh Gaekwad +919440487007 +918686318889
aldrinleal
commented
5 years ago Sorry, but this is beyond the scope of the Plugin. It is just responsible for deployment.
Also: Never ever hijack tickets again. Thank you.
Hi,
I am zipping in the files and folders inside the directory.
I provide the Zip file name, but it's giving me the below error:
Commands I am using: Shell: zip -r ${GIT_COMMIT}.zip .
Root Object?File Directory: ${GIT_COMMIT}.zip
Error: AWSEB Deployment Plugin Version 0.3.19 (aws-java-sdk version: 1.11.341) FATAL: Deployment Failure java.lang.IllegalArgumentException: Empty/blank versionLabel parameter at org.apache.commons.lang.Validate.notEmpty(Validate.java:321) at br.com.ingenieux.jenkins.plugins.awsebdeployment.cmd.DeployerCommand$ValidateParameters.perform(DeployerCommand.java:126) at br.com.ingenieux.jenkins.plugins.awsebdeployment.cmd.DeployerChain.perform(DeployerChain.java:54) at br.com.ingenieux.jenkins.plugins.awsebdeployment.SlaveDeployerCallable.call(SlaveDeployerCallable.java:
If you can help me with it. Many Thanks!