Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
Level
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Bamboo - Capabilities configuration is read-only because of specs

Hi guys,

I have a question regarding the agent management and its permissions in bamboo. The documentation and the found threads unfortunately didn't provide the crucial hint.

Preconditions:
-I'm using bamboo specs (yaml)
-I'm not the bamboo administrator


Problem:
While I try to deploy my already build artifact, the build fails because the used java version is not suitable:

[...]Exception in thread "main" java.lang.UnsupportedClassVersionError: <...> has been compiled by a more recent version of the Java Runtime (class file version 55.0),
this version of the Java Runtime only recognizes class file versions up to 52.0 [...]

I'm pretty sure this is related to the used bamboo agent. Sadly it seems like I can't change the used agent because I'm missing some permissions (I want to select an agent which uses Java 11 instead of 8):

 

1.png

 

Assumption:
For now, I guess it's needed to add some magic permission to the spec to be able to set the capability configuration on writable.

But I don't know which one is needed :)

 

currently, the permissions look like:

2.png

 

Thanks in advance guys.

1 answer

1 accepted

2 votes
Answer accepted

I think you don't need any additional permission here but to configure requirements for given evironment:

 

My environment:
tasks:
- clean
- artifact-download:
artifacts:
- {}
- script:
interpreter: SHELL
scripts:
- echo hello
requirements:
- java: '1.8'

Thanks, it seems to work like charm!

I didn't know that capabilities <-> requirements connection.

 

I managed to create a new capability, now I just need to find the correct name&value to get a suitable agent. But that's not within this question's scope.

SOLVED.

It's confusing UX, message should say that requirement is not editable because of Specs. Will be fixed at future versions

Like # people like this

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bamboo

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

73 views 2 5
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you