Can't parameterize the deployment group

awslabs / aws-codedeploy-plugin

Jenkins plugin for AWS CodeDeploy

Apache License 2.0

153 stars 131 forks source link

Can't parameterize the deployment group #24

Closed jimadamsss closed 8 years ago

jimadamsss commented 9 years ago

I have a set up deployment groups that I want to automation Jenkins. Each build is exactly the same except for the name of the deployment group. I tried to create a parameterized build but the fields for the CodeDeploy plugin do not substitute from the parameters. Here is the console output: CODEDEPLOYGROUP=CodeDeployDesignGroup-group-Jim

[EnvInject] - Variables injected successfully. Failed CodeDeploy post-build step; exception follows. Cannot find deployment group named '${CODEDEPLOYGROUP}' java.lang.IllegalArgumentException: Cannot find deployment group named '${CODEDEPLOYGROUP}'

cosmincatalin commented 9 years ago

I will look into making this happen. I have already added support for variables to the S3 path.

jordiclariana commented 9 years ago

This feature would be really apreciated. +1

aerostitch commented 9 years ago

Having the same issue. It would indeed be really appreciated! +1 :)

jakeleveroni commented 9 years ago

It would be great, I would also appreciate the add as well :)

suryanarayanan commented 9 years ago

Merged https://github.com/awslabs/aws-codedeploy-plugin/pull/35 to use environment variable for deployment group.

jimadamsss commented 8 years ago

I see a fix was pushed for this but I guess my request wasn't clear enough. I need ALL parameters to the plugin to all the use of environment variables. I see that issue #42 was added to address just one more parameter but, really, all parameters should be able to be fixed at run time.

Jmcfar commented 8 years ago

Hi,

The App Name, Deployment Group Name, Deployment Config Name, S3 Bucket and S3 Prefix fields should now all support parameterization as of version 1.8. If there are any we missed that you'd like to parameterize please feel free to re-open.