Pipeline started to fail with "Could not transfer artifact"

[guy sharon]

hi,

My pipeline started to fail a few days ago after passing for months. The message is:

Could not transfer artifact org.apache.maven.plugins:maven-shade-plugin:pom:2.4.3 from/to central (https://repo.maven.apache.org/maven2): Connection reset

 It's not always the same artifact or the same repository. I re-ran an old pipeline which passed and it failed, so I assume this is a caching issue. I tried to clear the cache using the button in Bitbucket's UI but it said no cache was defined. Here's the content of my bitbucket_pipelines.yml.

pipelines:
  default:
    - step:
        caches:
          - bower-20180619
          - npm-20180619
          - maven-20180619
        script: 
          - mvn clean package
        image:
          name: myimage/ci:1.0.1
          username: $DOCKER_HUB_USERNAME
          password: $DOCKER_HUB_PASSWORD
          email: $DOCKER_HUB_EMAIL

definitions:
  caches:
    bower-20180619: web/war/src/main/webapp/libs
    npm-20180619: web/war/src/main/webapp/node_modules
    maven-20180619: ~/.m2/repository

Any ideas on what I'm doing wrong?

[davina]

Hi @guy sharon

Have you tried to run this locally, just in your own local dev environment?

You can also debug your pipeline locally with Docker by following the guide here.

If the issue is not reproducible, then it could be cache related as you mentioned.

Caches are cleared after a week, and require a successful build for them to be uploaded again as mentioned in our docs. This is probably why you aren't seeing it the UI.

Otherwise it could configuration that needs to be updated potentially.

Hope this helps! Let me know if there's more information that could help debug the issue.