Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
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

Job limit on starter license

I'm currently using Bamboo with the starter license, and I'm supposed to have a 10 job limit. I thought that Plan Branches were counted as well, but I've been able to create 13 or so plan branches on this license (the plan having 1 job).

I've been writing a custom integration between my git repository and Bamboo, and I was hoping the API endpoint would fail if I tried to go over the job limit, but it does not.

Is this an error, or is this by design? How is the job limit enforced? Or have they changed how they count jobs?

3 answers

2 votes

We've changed the way we count the jobs in Bamboo 6.9. We only count 'unique'*)  jobs and branched jobs are not considered 'unique'.

*) unique being somewhat a loose term, we don't compare the actual content of the jobs...

1 vote

Hi @Daniel_Adolfsson ,

Thank you for your inquire.

Atlassian Bamboo has changed over past releases (as @Marcin Gardias mentioned) and the documentation has not been updated to reflect all of those, therefore, I will try to summarise the Starter License count.

  • PROJ-PLAN-JOB1, counted against license
  • If PROJ-PLAN-JOB1 and PROJ-PLAN0-JOB1 are equal, not counted against license
  • If PROJ-PLAN-JOB1 and PROJ-PLAN0-JOB1 are divergent, counted against license
  • If PROJ-PLAN doesn't have Bamboo Specs code, all branches are same and don't
  • count against license
  • If PROJ-PLAN contains Bamboo Specs code, all branches are divergent and count against license

Disabling a JOB does not free the license count, it is require to delete the JOB so a new one can be created. Due to this "limitation", it would be wise to make use of Bamboo Specs, so you can have your plans configuration in YAML or Java as a backup in case you need to restore it/them.

Please, have a look at Exporting existing plan configurations to Bamboo Specs for more information.

Hope the above clarifies things.

Kind regards,
Rafael

Hi @Daniel_Adolfsson ,

I have created a feature request to reduce friction on this matter - https://jira.atlassian.com/browse/BAM-20919 - Starter License should allow unlimited jobs with 1 local agent

Please, feel free to comment on the link above.

Kind regards,
Rafael

0 votes
Jeyanthan I Atlassian Team Dec 02, 2020

Just in case if anyone landed in this thread via search engines, we created a dedicated page that explains these scenarios in detail along with a query that you can run to list those Bamboo jobs that are counted for license restrictions. 

Cheers,
Jey

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 ...

190 views 4 6
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