You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I am using a product where in the deployment needs to happen in a particular directory of unix, which not only contains the source archived in bit bucket but also contains some dynamic files which should not be touched during the deployment and hence cannot delete the whole diretory and redeploy using untar command.
I am using unix server where the files are deployed using a untar command.
eg. tar -xvf cust.tar
I am stuck in the below scenario.
Step1 ) Bit bucket branch contains version1
deployment from bitbucket happened, the 3 files got deployed in the server using untar command tar -xvf <tarfilename>
Bit bucket branch contains version2
a.sh (got deleted)
deployment from bitbucket happened, the 2 files got deployed in the server using untar command tar -xvf <tarfilename>. The deployment server contains the below file after using the untar command
a.sh (ver1) (contains the file from the previous deployment, which is not needed now)
Problem statement :- after the deployment in step2, I would require a handle to know the deleted file in the branch.
I have tried mutiple option like
git log --diff-filter=D --summary | grep deleted (this command give the entire list of master branch as well, I am looking for the file deleted only in that particular branch).
Request help regarding the same. I am using Bamboo for CI and CD.
Have you using task clean working directory for every start or finish of your plan?
Also, for handling you can set is as artifact, then fetch from previous run by rest api.
Hi Gonchik Tsymzhitov ,
Sorry for the delayed response, no we are not using the clean working directory as, the directory contains some of the files which is not in source versioning and hence cannot have the clean working directory.
We are using bit bucket for our source versioning.