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.
I understand that Bamboo is still not compatible with Java 11.
I have some software in my server that requires Java 11 to work, but I also have Bamboo in the same server. I know you can install both. Java 8 and Java 11 and keep them at the same time...
For the JAVA_HOME variable (Windows Server 2012), I see I can add multiple entries, but that won't necessarily mean that Bamboo will find the compatible one in the list?
It there a setup or arrangement I can do in my server so that Bamboo detects there's a Java 8 and uses it, and the other Software uses Java 11? (I can't edit anything in the other software, so the default pointers/variables must direct to Java 11 so that the other software detects it).
i think you need to edit some config file, there are options to set envionment (i know from jira) you can set in config file where java_home which one to use, i think this way can be correct or looking for solution to set env for (bamboo user)
bamboo directory and files
https://confluence.atlassian.com/bamboo/locating-important-directories-and-files-289277247.html
plan B
found something maybe will helps
https://stackoverflow.com/questions/26993101/switching-between-different-jdk-versions-in-windows
There are some code block that said how to
The set
command only works for the current terminal. To permanently set a system or user environment variable you can use setx
.
setx JAVA_HOME "C:\Program Files\Java\jdk1.7.0_72" /m
setx doc:
https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/setx
p.s. test it on stage before prod, and make backup copy of config files
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.