We are currently attempting to use Bitbucket Pipelines to build our Maven project. When I run the build locally using the guide in the documentation, allocating 4g of memory and 4g of swap memory, the build passes correctly with no issues. Once deployed to the environment, however, the build fails about 90% of the time.
I am using a custom docker image and mvn install to build our project. When I dig through the pipelines logs, it turns out that there are no errors and the command doesn't appear to finish. The logs appear to end half way through the execution.
Our build process is computationally intense so it is my opinion that the fails are caused by some sort of resource limitation. Is there a way to figure out why the command doesn't finish or if there is some environment fail?
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