You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
When running a build (first one triggered with merge) the build stalls and eventually fails. Upon rerunning manually the build succeeds. Repeatable.
In the log there is a warning message just prior the stall that says:
"The size of environment is 4862, make sure your build environment handles this correctly"
Is the build running out of java env and if so, how can I bump that up?
Hi @Jeff_Schaeffer,
This is a message that informs you that there are a lot of environment variables configured on the system.
There is a kb article about the issue and the recommendation is trimming down the variables.
Build fails because the environment block used to start a process cannot be longer than X bytes
Yep, saw that, the error is different but has some similarities I agree. If I were to run out of env I'd expect and error similar. So how do I go about bumping that env space up as there aren't an excess amount of variables (No Globals, No Plan level, only scripting)?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.