search

awslabs / aws-codepipeline-plugin-for-jenkins

Use this plugin to integrate your Jenkins project with a pipeline in AWS CodePipeline. For more information and step-by-step directions on how to install and configure this plugin, follow the Four Stage Pipeline Tutorial. http://docs.aws.amazon.com/codepipeline/latest/userguide/getting-started-4.html
Apache License 2.0
82 stars 68 forks source link

Support for WAR file artifact in addition to zipped folder #8

Closed Jon-DeWitt closed 8 years ago

Jon-DeWitt commented 8 years ago

I'm not currently seeing a way to get this to work for deployment to an Elastic Beanstalk Tomcat environment which expects a WAR file and not a zipped directory. My CodePipeline is running fine and sending back either a directory, or an appropriately sized but corrupt file if I try to specify the WAR file in the Post Build Publisher Location.

If there's some other work around that would be great also, just trying to set up a proof of concept at the moment.

Thanks, --Jon

Jon-DeWitt commented 8 years ago

Closing as not an issue. WAR files are apparently just zip files, so using compile war:exploded in the maven goal will prepare an output directory that will work as an output artifact for Elastic Beanstalk.

Other thoughts as I finished configuring this: 1) Naming convention of the artifact in S3 could be better, project name and utc date like the EB versions 2) Multiple deployments of the same artifact to Elastic Beanstalk create different EB "versions" which is confusing. For example, using the same artifact deploy the same code base to 9 different environments in the same EB application. Each looks like it's running a different version of the application. The source is the same in the console, but the version label and description differs by the guid and microsecond.