how to push only the code changes

zzzro

Hello,

I am new to bitbucket. We have succcesfully configired bitbucket pipeline to push a repository branch to AWS EC2 instance using Code Build and Code Deploy.

But, the issue is, when we run the pipeline, it creates a zip file of entire repository and replaces the entire content on EC2. We want to push only the changes we did (say a single php file). Zipping entire repostiroy with images, and media files is a overkill and doesn't allow us to promote only bugfix.

How can we do that - any help will be great.

Pls. find our pipeline yml file content below.

- step: script:

- apt-get update

- apt-get install -y zip - zip -r appProd.zip

 - pipe: atlassian/aws-code-deploy:0.2.5

variables:

AWS_DEFAULT_REGION: $AWS_DEFAULT_REGION

AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID

AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY

APPLICATION_NAME: $APPLICATION_NAME

S3_BUCKET: $S3_BUCKET

COMMAND: "upload"

ZIP_FILE: "appProd.zip"

VERSION_LABEL: "app-web-prod-1.0.0"

- pipe: atlassian/aws-code-deploy:0.2.5

variables:

AWS_DEFAULT_REGION: $AWS_DEFAULT_REGION

AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID

AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY

APPLICATION_NAME: $APPLICATION_NAME

DEPLOYMENT_GROUP: "xx_Www_Pppp"

S3_BUCKET: $S3_BUCKET

COMMAND: "deploy"

WAIT: "true"

VERSION_LABEL: "app-web-prod-1.0.0"

IGNORE_APPLICATION_STOP_FAILURES: "true"

FILE_EXISTS_BEHAVIOR: "OVERWRITE"

Halyna Berezovska

@zzzrothanks for using the pipe.

Looks like --file-exists-behviour OVERWRITE does not do actually what you want. It does not compare what files have changed:

First option

In aws docs I see that this param can be described as the following:

OVERWRITE: The version of the file from the application revision currently being deployed replaces the version already on the instance.

So overwrite file-exists-behaviour option does not actually define what files have changed - there is nothing in the doc about that.

First option for you is try to use RETAIN for --file-exists-behaviour. I am not sure it does what you need, it seems it will not also detect the changed files.  Doc is here .

 

Second option

But I'd like to propose one more option, that you could go with:

So if aws deploy does not support RETAIN option in the way you like, I propose you to zip earlier (at build step) only changed files at the build step and pass this file.

I found some examples how can you do it through zip and git tools:

https://askubuntu.com/questions/205421/is-it-possible-to-zip-changed-files-into-a-separate-archive-with-only-the-change

https://stackoverflow.com/questions/4126300/git-how-to-get-all-the-files-changed-and-new-files-in-a-folder-or-zip .

 

P.S. Besides that, I cannot understand part of your case: when you deploy to instance, is there a possibility you have other changes, aimed not for that instance you deploy to?

Just in case we want to give some recommendation for CD best practices:

If you make bugfix to ec2 code, it is better to branch  from that revision (tag, version, whatever) that you have on that ec2 instance.

 

Waiting for your feedback, we are ready to improve our pipes, if we find that we could support some interesting cases, that makes our code more flexible for all users.

 

Regards, Galyna