Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,653
Community Members
 
Community Events
176
Community Groups

Unable to publish bigger size artifacts

Edited

For frontend we have one tar.gz that is publishing fine which is around 8MB. And for backend we have one fat jar which is around 150MB. (Also tried to compress it around 120MB and publish, yet failed. How ever small size file publishing in the same stage works fine.) since it is a build fat jar, which we use only once to deploy on PCF, it is fine to not store it on nexus.

1 answer

0 votes
Jimmy Seddon Community Leader Jul 23, 2020

Hi @Neha,

Welcome to the Community!

What error message is displayed in the build log when you are trying to publish that artifact?  We have a 500 MB package that we store regularly without any issues.

Thanks!

-Jimmy

Hi @Jimmy Seddon  

Here is the error

21-Jul-2020 05:11:26 com.atlassian.bamboo.build.artifact.BambooRemoteArtifactHandler: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

Jimmy Seddon Community Leader Jul 23, 2020

Hi @Neha,

I'd take a look at the answers in either of these two posts both look to point to the same type of root issue:

https://community.atlassian.com/t5/Bamboo-questions/PKIX-path-building-failed-on-Bamboo/qaq-p/1066964

https://community.atlassian.com/t5/Bamboo-questions/Bamboo-remote-agent-setup-getting-error-as-quot-Unable-to-find/qaq-p/9374

In either case it sounds like SSL Cert issues.  Is this building on a remote agent that may not have the Bamboo Server's certificate installed?

I hope those answers lead you to the solution.

-Jimmy

Hi @Jimmy Seddon 

I am just wondering If this is SSL cert issue then how it is working for artifacts with smaller size.

Jimmy Seddon Community Leader Jul 24, 2020

To answer that, we'd need to start by looking closer at your Bamboo environment.  Do you have multiple remote agents?  Are both of these artifacts a part of the same build job?  It's possible that the smaller one that is working is building either on a local agent, or one of the remote agents that doesn't have SSL issues.

I hope that helps!

-Jimmy

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events