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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi,
The documentation on page https://support.atlassian.com/bitbucket-cloud/docs/deploy-to-heroku/ says the following:
Heroku deployments require a full Git clone. By default, Pipelines clones your repository with a depth of 50 to shorten your build time. You can configure your Pipeline to do a full Git clone in your bitbucket-pipelines.yml file.
I don't understand why do I need a "full Git clone".
Bitbucket only needs to create a tgz with the source code and send that package to Heroku. The tgz should not contain the ".git" directory because it has no use for Heroku. Heroku only needs the source code.
So, why a "full Git clone"?
Hi Bruno,
We are not entirely sure of this to be honest. Heroku is a third-party application and based on previous troubleshooting - does not accept an outbound connection properly when deploying without a full clone.
I would suggest reaching out to Heroku support for this enquiry:
https://www.heroku.com/support
Cheers!
- Ben (Bitbucket Cloud Support)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.