I have a Bitbucket pipeline configured for maven project and it was working well.
I have not did any changes regarding build flow (maven config or pipeline config) but pipeline started failing because of: "Could not transfer artifact org.apache.maven:maven-plugin-api:pom:3.0 from/to central (https://repo.maven.apache.org/maven2)".
Here is more detailed error text:
Plugin org.apache.maven.plugins:maven-resources-plugin:3.0.1 or one of its dependencies could not be resolved: Failed to collect dependencies at org.apache.maven.plugins:maven-resources-plugin:jar:3.0.1 -> org.apache.maven:maven-plugin-api:jar:3.0: Failed to read artifact descriptor for org.apache.maven:maven-plugin-api:jar:3.0: Could not transfer artifact org.apache.maven:maven-plugin-api:pom:3.0 from/to central (https://repo.maven.apache.org/maven2): Connection reset -> [Help 1]
It appears that your connection to the maven repository timed out, causing your build to fail. This could be for a number of factors. Rerunning your pipeline should be sufficient to resolve this though.
If this continues to be a persistent problem, you can look into increasing your timeout for retrieving dependencies:
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs