Clear Caches Pipe does not work

Antoni Florit

We are using Clear Caches Pipe to clear the "node" cache and the "cypress" custom cache so every run we do the step with Bitbucket's Clear Caches Pipe script ends with a 404 error with the following message:

 

<span>&#10006; Failed to retrieve caches: 404 {"type": "error", "error": {"message": "Resource not found"}} <a href="https://api.bitbucket.org/2.0/repositories/thebellhop/ess-front/pipelines-config/caches/?page=1&pagelen=100" rel="noopener nofollow noreferrer" target="_blank">https://api.bitbucket.org/2.0/repositories/thebellhop/ess-front/pipelines-config/caches/?page=1&pagelen=100</a></span>

The step with the script is as follows:

    - step: &clear-cache

        name: delete cache if changes in the build dependencies

        script:

        - pipe: atlassian/bitbucket-clear-cache:3.1.1

          variables:

             BITBUCKET_USERNAME: $BITBUCKET_USERNAME

              BITBUCKET_APP_PASSWORD: $BITBUCKET_APP_PASSWORD

             CACHES: ["cypress", "node"]

        condition:

          changesets:

            includePaths:

             - package.json

Can anyone help us?

Patrik S

Hello @Antoni Florit ,

Thank you for reaching out to Atlassian Support.

The error you are receiving is from one of the API calls the pipe is doing behind the scenes, where it gets all the caches from the repository. A 404 response from that API either means that the repository does not exist (which is not the case here), or the credentials being used to authenticate does not have access to it.

So could you please confirm if the bitbucket username you set as the variable $BITBUCKET_USERNAME is correct, and if that user has access to the repository where the pipeline is running ? Also, make sure this is the bitbucket username of the account, not the e-mail address. You can check the username going to the account's personal settings https://bitbucket.org/account/settings/

Additionally, please make sure the App Password you are using has the required permissions. To narrow down if the issue if with the permissions of the app password you are currently using, you can try creating a new app password with full permissions checked and test if using it the pipe completes successfully.

Hope that helps! Let me know if you run into any issues.

Thank you @Antoni Florit ,

Kind regards,

Patrik S