codedeploy-agent keeps a default of 11 and a minimum of 5 copies of my application on disk

[aws]

codedeploy-agent keeps a default of 11 and a minimum of 5 copies of my application on disk

[lperezdude]

Im having a issue where my deployment scrip is failing and i'm not sure why. When i use locate i can se that there are some files kept in the deployment-archive

/opt/codedeploy-agent/deployment-root/b0262369-...-4c44-ab6d-6ee70839a1ae/d-.../deployment-archive/deploy/scripts/ApplicationStop.sh
/opt/codedeploy-agent/deployment-root/b0262369-...-4c44-ab6d-6ee70839a1ae/d-.../deployment-archive/deploy/scripts/ApplicationStop.sh
/opt/codedeploy-agent/deployment-root/b0262369-...-4c44-ab6d-6ee70839a1ae/d-../deployment-archive/deploy/scripts/ApplicationStop.sh.

And these are Old deployments (failed attempts). I believe i've fixed my scrip issue but i don't know how to make the codedeploy agent use the new scripts from GitHub and not try to pick up from the old deployments. is there like a deployment-archive cache clear or something for this ?

[manikarnam]

[gaohan137]

Hi timgilbert,

max_revision is not documented anywhere? hmm -> http://docs.aws.amazon.com/codedeploy/latest/userguide/host-cleanup.html

The fix for #57 will be fixed in next release of the host agent.

[webmutation]

I configured the :max_revisions: parameter to 3 and it continues to have 5 folders and going over the amount of space... currently the only thing that seems to work is to force the cleanup thru a hook.

Installed Packages
Name : codedeploy-agent
Arch : noarch
Version : 1.0
Release : 1.1352
Size : 16 M
Repo : installed
Summary : Provides the required files for CodeDeploy agent to run in EC2 instances
License : Amazon.com Internal
Description : CodeDeploy instance agent is responsible for doing the actual work of deploying software
: on an EC2 instance.

[annamataws]

Hi,

The max_revisions works in the new agent releases and deletes the extra deployment revisions within a deployment group. It works when being set to an integer that is 1 or greater. If you have multiple deployment groups, each deployment group will honor the max_revisions separately.

aws-codedeploy-agent/lib/instance_agent/plugins/codedeploy/command_executor.rb

Line 77 in c3860f7

cleanup_old_archives(deployment_spec)

Please let me know if you are still seeing problems.

Thank you

[annamataws]

Will close this since the fix has been out for a while.

[manikarnam]

Team,
I have an issue with AWS Codedeploy Cache after completed the pipeline but it is taking old data.
How do I solve the issue over the Pipeline?

Could anyone help me, guys?
Thanks in advance.

[manikarnam]

But MySQL service everything has been deleted. I don't know why how it comes to the old data after completed the Pipeline.

Could you please help me on this issue

[send2kbl]

@manikarnam
Any updates or workaround on this issue ?

Besides the same Log error from a previous deployment, I'm getting this error message on the console:
The overall deployment failed because too many individual instances failed deployment, too few healthy instances are available for deployment, or some instances in your deployment group are experiencing problems.

PS. I did restart the agent