Hi there, I see you already filed one of the issues on JIRA a week ago: https://issues.jenkins-ci.org/browse/JENKINS-31705
It seems that there are two AWS EB plugins which do the same thing and have similar names, so hopefully that's filed against the correct plugin.. :) Anyway, if you could file the other issues separately on JIRA as well, that would be the best place to keep track of them. Not all plugin maintainers necessarilyt read this mailing list all the time. This wiki page gives a good guide as to what information you should include in your bug report / feature request: https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue Regards, Chris 01/12/15 09:17, [email protected] wrote: > Hi Team, > > I found out some bugs while working on the AWS Elastic Beanstalk > Deployment and AWS Elastic Beanstalk Publisher Plugin. > > *1. AWS Elastic Beanstalk Plugin* > > In this, > > *a) The most vulnerable issue is that, AWS secret key is visible and > its not hiding. So its a security issue.* > > And to avoid the above security issue, I used *AWS Elastic > Beanstalk Publisher* Plugin which helped me to declare the IAM user and > secret key globally in Jenkins. And the secret key also was being > hidden. By this plugin, in the job level configuration, I need not have > to mention the secret key anymore. > > *b) Another issue is, it does not take wild card character like ' * ' .* > > And because of this, I was unable to declare the value of the > parameter ' Root Object (File/Directory) ' as target/ *.war > It did not filter out the war file. As a result of which when this > plugin was trying to deploy the zip file to Elastic > Beanstalk, it threw *HTTP 404 Error, Resource not found. * > * > * > * *And to avoid this above issue, I did another work around like I > filtered the particular war file to a new folder, then > unzipped that war file there itself. After unzipping the war file, then > I removed the war file from that location. > All these I did in the *Execute Shell* prompt. > > Execute Shell > Command - #!/bin/bash > > mkdir -p ${WORKSPACE}/target/war > > cp -r ${WORKSPACE}/target/*.war > ${WORKSPACE}/target/war/. > > echo War copied successfully !!! > > cd ${WORKSPACE}/target/war/ > > unzip *.war > > rm *.war > After this above steps I mentioned the details in the plugin and then > finally it got deployed in Beanstalk. > > *c) The " Includes " and " Excludes " doesn't take the wild card " * " > character as well.* > > *2. AWS Elastic Beanstalk Publisher Plugin* > > In this, > > *a) It does not take wild card character like ' * ' .* > > Work around is same as above. > > *b) The " S3 overwrite exisiting file " parameter is not working, it's > not updating.* > * > * > * c) The " Includes " and " Excludes " doesn't take the wild card " * " > character as well.* -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/565E0AB7.30206%40orr.me.uk. For more options, visit https://groups.google.com/d/optout.
