Can't use version 1.1.0-SNAPSHOT

[jenzhang2000]

ERROR] Plugin br.com.ingenieux:beanstalk-maven-plugin:1.1.0-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for br.com.ingenieux:beanstalk-maven-plugin:jar:1.1.0-SNAPSHOT: Could not find artifact br.com.ingenieux:beanstalk-maven-plugin:pom:1.1.0-SNAPSHOT -> [Help 1]

If I downgrade to 1.0.1, it seems to work with this cmd
mvn beanstalk:check-availability -Dbeanstalk.cnamePrefix=test-war

but 1.0.1 seems to have issue with mvn beanstalk:upload-source-bundle as it doesn't seem to take s3Bucket argument when constructing s3 path

[aldrinleal]

1.0.1 is the most curent version. Can you post the logs for upload-source-bundle (perhaps a mvn -X)?

[jenzhang2000]

upload-source-bundle worked. But having issue with other commands:

mvn beanstalk:update-application-version -Denv=uat -Dbeanstalk.versionLabel=20130822-143424

it shows success

INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building posservice 2.4.2-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- beanstalk-maven-plugin:1.0.1:update-application-version (default-cli) @ posservice ---
[INFO] SUCCESS
[INFO] * sourceBundle: {S3Bucket: elasticbeanstalk-mvn-deploy, S3Key: POS service/posservice-2.4.2-SNAPSHOT-20130822-143424.war, } [class: S3Location]
[INFO] * versionLabel: 20130822-143424 [class: String]
[INFO] * description: posservice [class: String]
[INFO] * applicationName: POS service [class: String]
[INFO] * dateCreated: Thu Aug 22 14:35:48 PDT 2013 [class: Date]
[INFO] * dateUpdated: Thu Aug 22 15:13:58 PDT 2013 [class: Date]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.211s
[INFO] Finished at: Thu Aug 22 15:13:58 PDT 2013
[INFO] Final Memory: 7M/81M
[INFO] ------------------------------------------------------------------------

but when I logged into aws console, it still use existing app version, nothing changed

[aldrinleal]

you need to call upload-source-bundle update-aplication-version and then
update-environment. it is so boring we actually prefer git (mvn
archetype:generate -Dfilter=elasticbeanstalk to get an idea)
On Aug 22, 2013 7:18 PM, "jenzhang2000" notifications@github.com wrote:

upload-source-bundle worked. But having issue with other commands:

mvn beanstalk:update-application-version -Denv=uat
-Dbeanstalk.versionLabel=20130822-143424

it shows success

INFO] Scanning for projects...
[INFO]

[INFO]

[INFO] Building posservice 2.4.2-SNAPSHOT

[INFO]

[INFO]
[INFO] --- beanstalk-maven-plugin:1.0.1:update-application-version
(default-cli) @ posservice ---
[INFO] SUCCESS
[INFO] * sourceBundle: {S3Bucket: elasticbeanstalk-mvn-deploy, S3Key: POS
service/posservice-2.4.2-SNAPSHOT-20130822-143424.war, } [class: S3Location]
[INFO] * versionLabel: 20130822-143424 [class: String]
[INFO] * description: posservice [class: String]
[INFO] * applicationName: POS service [class: String]
[INFO] * dateCreated: Thu Aug 22 14:35:48 PDT 2013 [class: Date]
[INFO] * dateUpdated: Thu Aug 22 15:13:58 PDT 2013 [class: Date]

[INFO]

[INFO] BUILD SUCCESS

[INFO]

[INFO] Total time: 2.211s
[INFO] Finished at: Thu Aug 22 15:13:58 PDT 2013
[INFO] Final Memory: 7M/81M

[INFO]

but when I logged into aws console, it still use existing app version,
nothing changed

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/34#issuecomment-23130638
.

[aldrinleal]

sorry, its:

upload-source-bundle, create-application-version, and update-environment
On Aug 22, 2013 7:24 PM, "Aldrin Leal" aldrin@leal.eng.br wrote:

you need to call upload-source-bundle update-aplication-version and then
update-environment. it is so boring we actually prefer git (mvn
archetype:generate -Dfilter=elasticbeanstalk to get an idea)
On Aug 22, 2013 7:18 PM, "jenzhang2000" notifications@github.com wrote:

upload-source-bundle worked. But having issue with other commands:

mvn beanstalk:update-application-version -Denv=uat
-Dbeanstalk.versionLabel=20130822-143424

it shows success

INFO] Scanning for projects...
[INFO]

[INFO]

[INFO] Building posservice 2.4.2-SNAPSHOT

[INFO]

[INFO]
[INFO] --- beanstalk-maven-plugin:1.0.1:update-application-version
(default-cli) @ posservice ---
[INFO] SUCCESS
[INFO] * sourceBundle: {S3Bucket: elasticbeanstalk-mvn-deploy, S3Key: POS
service/posservice-2.4.2-SNAPSHOT-20130822-143424.war, } [class: S3Location]
[INFO] * versionLabel: 20130822-143424 [class: String]
[INFO] * description: posservice [class: String]
[INFO] * applicationName: POS service [class: String]
[INFO] * dateCreated: Thu Aug 22 14:35:48 PDT 2013 [class: Date]
[INFO] * dateUpdated: Thu Aug 22 15:13:58 PDT 2013 [class: Date]

[INFO]

[INFO] BUILD SUCCESS

[INFO]

[INFO] Total time: 2.211s
[INFO] Finished at: Thu Aug 22 15:13:58 PDT 2013
[INFO] Final Memory: 7M/81M

[INFO]

but when I logged into aws console, it still use existing app version,
nothing changed

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/34#issuecomment-23130638
.

[jenzhang2000]

That worked. But new issue I having is
mvn beanstalk:rollback-version beanstalk:update-environment -Denv=uat
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building posservice 2.4.2-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- beanstalk-maven-plugin:1.0.1:rollback-version (default-cli) @ posservice ---
[INFO] Changing versionLabel for Environment[name=posservice; environmentId=e-anqmamvhd5] from version 20130822-143424 to version 20130822-141156
[INFO] SUCCESS
[INFO]
[INFO] --- beanstalk-maven-plugin:1.0.1:update-environment (default-cli) @ posservice ---
[INFO] Calling update-environment, and using versionLabel: 20130822-163115
[WARNING] FAILURE
org.apache.maven.plugin.MojoFailureException: Failed
at br.com.ingenieux.mojo.aws.AbstractAWSMojo.handleException(AbstractAWSMojo.java:395)
at br.com.ingenieux.mojo.beanstalk.cmd.BaseCommand.handleException(BaseCommand.java:84)
at br.com.ingenieux.mojo.beanstalk.cmd.BaseCommand.execute(BaseCommand.java:76)
at br.com.ingenieux.mojo.beanstalk.env.UpdateEnvironmentMojo.executeInternal(UpdateEnvironmentMojo.java:79)
at br.com.ingenieux.mojo.aws.AbstractAWSMojo.execute(AbstractAWSMojo.java:356)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: Status Code: 400, AWS Service: AWSElasticBeanstalk, AWS Request ID: f24a5b5f-0b82-11e3-b361-af00da2b13f1, AWS Error Code: InvalidParameterValue, AWS Error Message: No Application Version named '20130822-163115' found.
at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:614)
at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:312)
at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:165)
at com.amazonaws.services.elasticbeanstalk.AWSElasticBeanstalkClient.invoke(AWSElasticBeanstalkClient.java:1336)
at com.amazonaws.services.elasticbeanstalk.AWSElasticBeanstalkClient.updateEnvironment(AWSElasticBeanstalkClient.java:971)
at br.com.ingenieux.mojo.beanstalk.cmd.env.update.UpdateEnvironmentCommand.executeInternal(UpdateEnvironmentCommand.java:58)
at br.com.ingenieux.mojo.beanstalk.cmd.env.update.UpdateEnvironmentCommand.executeInternal(UpdateEnvironmentCommand.java:26)
at br.com.ingenieux.mojo.beanstalk.cmd.BaseCommand.execute(BaseCommand.java:74)
... 23 more
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3.567s
[INFO] Finished at: Thu Aug 22 16:31:19 PDT 2013
[INFO] Final Memory: 7M/81M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal br.com.ingenieux:beanstalk-maven-plugin:1.0.1:update-environment (default-cli) on project posservice: Failed: No Application Version named '20130822-163115' found. -> [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] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

[jenzhang2000]

as you can see, it did try to rollback to previous version,

[INFO] Changing versionLabel for Environment[name=posservice; environmentId=e-anqmamvhd5] from version 20130822-143424 to version 20130822-141156

but the update-env still use a newly generated label
INFO] Calling update-environment, and using versionLabel: 20130822-163115

Great thanks!!!

[jenzhang2000]

Another question I had is every time i call beanstalk:upload-source-bundle it tries to build the war file
but I have created war using mvn clean install and I just need to upload war without rebuilding it. Is there another command I can use?

Thanks!

[aldrinleal]

Instead of env, use cnamePrefix - it does the same stuff

There's nothing in beanstalker requiring a phase to be bound, so it makes no sense when you say it tries to build. Can you ellaborate more on that (perhaps on another issue? or on the mailing list)

Thank you

[aldrinleal]

In case of rollback-version, it does the call for update-environment, so this command would do the same result:

mvn beanstalk:rollback-version -Denv=uat