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
Bamboo does not have a built-in way to download only changes from any version control system (VCS). Though, you should be able to configure a series of custom script tasks using VCS commands (Git, SVN, etc) to detect any changes to the repository then pull only the changes.
Bamboo does not have a way to determine what changes were made to a repository between builds as Bamboo leaves the tracking of changes to repositories to the VCS. Perhaps the builds times could be queried from the Bamboo database and correlated to repository changes made afterward.
The following query should provide a list of code commits and commit files per build, and can be used as a starting point for the database deployment automation. Please note that the query may need to be adjusted slightly depending on the database server type being used.
FROM USER_COMMIT uc
JOIN REPOSITORY_CHANGESET rc ON (uc.REPOSITORY_CHANGESET_ID = rc.REPOSITORY_CHANGESET_ID)
JOIN BUILDRESULTSUMMARY brs ON (rc.BUILDRESULTSUMMARY_ID = brs.BUILDRESULTSUMMARY_ID)
JOIN AUTHOR a ON (a.AUTHOR_ID = uc.AUTHOR_ID)
JOIN COMMIT_FILES cf ON (uc.COMMIT_ID = cf.COMMIT_ID)
WHERE brs.BUILD_KEY = '<BUILD_KEY>'
AND brs.BUILD_NUMBER = <BUILD_NUMBER>;