Using composer custom cache location in bitbucket pipeline Edited

[Stetson Lewis]

Hello,

  I am trying to cache my composer dependencies between builds.  From what I have seen, I am using a custom composer cache location since the image does not use the default `~/.composer/cache` location.  Upon running the following script, I see in the build teardown section of the Composer install section that a cache is indeed being created: "Assembling contents of new cache 'composer-custom'".  However, on subsequent runs of the build, it installs fresh composer dependencies and does not read from the cache. 

Since I can't quite seem to get the code snippet to look nicely in this textarea, here is a gist of my file.

[Theodora Boudale]

Hi @Stetson Lewis  and welcome to the community.

It's a bit difficult to say why this is happening without checking the builds.

I would suggest opening a ticket with the support team and share the URL of a build where you see the cache being created, and of a subsequent one where it is not being used. The support ticket will be visible only to you, Atlassian staff, and any colleagues you may want to CC.

If there is an open ticket, the engineer working on your case will be able to access the builds and assist with this issue. You can open a ticket via https://support.atlassian.com/contact/#/, in "What can we help you with?" select "Technical issues and bugs" and then Bitbucket Cloud as product.

If you have any questions, please feel free to let me know.

Kind regards,
Theodora

[Stetson Lewis]

Hi Theodora, thank you for your response and suggestion.  I have went ahead and opened a ticket and will follow up here once there is a resolution.