Clear clone cache in self hosted linux arm64 runner

Question

Setup:
-  Running pipelines on a self hosted linux docker (arm64) runner with dind

Problem:
- Not able to clear the repository clone cache

I am running a pipeline on a self-hosted linux docker (arm64).
The pipeline configuration is to run dind (with a custom docker image running "in-d") and all the pipeline scripts executing on the custom docker image.

On running docker compose up, the docker-compose.yml being used is the cached file and not the updated file.

I tried clearing the cache using the pipe atlassian/bitbucket-clear-cache, but it turns out, this is not available for the arm64 achitecture.

Any help would be greatly appreciated.

Ananya Pandey_x2y7bi · Answer

Hi @Patrik S ,
Thank you for your response.

I implemented a work-around by cross-compiling the atlassian/bitbucket-clear-cache for arm64 architecture and using a docker image pipe instead of a repository.

Thanks for your solution though.

Patrik S · Answer

Hello @Ananya Pandey , and welcome to the Community!

Bitbucket Pipelines will only cache files/folders that were explicitly defined to be cached in your YML file. E.g. :

definitions:
  caches:
     bundler: vendor/bundle

pipelines:
  default:
     - step:
       caches:
         - bundler #cache is defined above in the definitions section
       script:
         - bundle install --path vendor/bundle

Could you please confirm if you have a cache defined in your YML file? If yes, you can manually remove any cache following the below instructions:

* Navigate to the repository
* Select Pipelines option on the left side menu
* Click on the Caches button in the top right
* Delete any existing cache by clicking on the Trash icon right after it.

After deleting all the caches you can trigger a new pipeline and check how it goes.

If you are still facing issues after following those steps, we kindly ask you to share your YML file here so we can have a better understanding of your pipeline setup.

If you prefer not to share that information here publicly, I see your workspace has an active paid plan that is entitled to Standard support. In this case, feel free to open a support ticket with us on Atlassian Support portal , selecting Technical Issues and bugs > Bitucket Cloud and providing the workspace URL of the paid workspace when asked in the form.

Thank you, @Ananya Pandey !

Patrik S