Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Why do I need a "full Git clone" when deploying to Heroku?

Bruno Zica
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 6, 2023

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"?

 

1 answer

0 votes
Ben
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 8, 2023

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)

  

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events