What is the meaning of 10 jobs limitation in Bamboo Starter Edition?

What is 10 jobs limitation in Bamboo Starter Edition, Is it max jobs I can create or max jobs I can run concurrently?

5 answers

1 accepted

Accepted Answer
7 votes
Daniel Wester Community Champion Mar 04, 2014
The starter license is limited to 10 jobs in the system. From my experience this includes branch plans. Starter agents only has local agents. The system will only allow you to create 10 jobs system wide. (Deployment plans are not included).

I just created more than 10 jobs in a project and it let me create and run them, I am not sure what they mean by jobs here.

Were you on the $10 starter license, or were you on evaluation?

https://www.atlassian.com/software/bamboo/pricing/?tab=download#download-license-details

They call them agents instead of jobs. You will be able to use 10 concurrent agents at any one time. As long as you have an agent free you will be able to build or test a job.

If you try to run 11 jobs at once, 1-10 will start and 11 will wait until an agent is ready.

I'm not sure this is correct. Agents and jobs are different things. You can have unlimited local agents on any plan, but you can't (from what I can tell) _define_ more than 10 jobs in total on the Starter plan.

As stated in Balazs's comment, they have an answer in their starter licensing page at the bottom.  Bamboo's hierarchy is Project->Plan->Stage->Job->Task.  So I have one branch in one repository I automatically build from Bitbucket Server locally.  That's one project containing one plan containing 1 stage with 1 Job that has 5 tasks (checkout, build, custom script, run tests, parse test results).  So I could automatically build and test 10 separate branches in the same or different repositories with this simple setup.

Bamboo

1. What restrictions are there when using a Bamboo Starter License?

With a Bamboo Starter License, you are restricted to 10 build Jobs, and 0 remote agents, but can run unlimited local agents.  A Job is a single build unit within a Plan. One or more Jobs can be organised into one or more Stages. Given a 10 Job limit, you may distribute your Jobs between up to 10 Plans - for example, one Job per Plan or all 10 Jobs within one Plan. There is no limit on the number of times a Plan is built/executed.

Please note that use of the Plan Branches has a multiplicative effect on the number of jobs configured, and therefore an effect on the 10 jobs cap. For example, a plan with two jobs that is building against a total of three branches (the plan's original branch, plus two additional branches) will contribute 6 jobs toward the limit. 

0 votes

The limitation is on Plans, there's no limit on the amount of Jobs in these plans.

Actually the opposite is stated here: https://www.atlassian.com/licensing/starter#bamboo-1

With a Bamboo Starter License, you are restricted to 1 local agent and 10 Jobs. .... Given a 10 Job limit, you may distribute your Jobs between up to 10 Plans - for example, one Job per Plan or all 10 Jobs within one Plan.

The job multiplier on branches is an unfairly onerous restriction, especially for Bitbucket git repositories using a release branch management style as apparently the master branch is automatically included along with other configured branches.

For example, we added develop and a feature branch to our plan with two jobs.  That is counting as 6 jobs (including master branch) toward the starter license limit!  Unless there are some settings or hidden jobs I am missing.

Yeah, that's one thing that drove me to TeamCity.  They should eliminate branches taking up jobs as you can't get very much done with that.  You'd end up with a couple plans with branches at most which isn't very helpful.  TeamCity doesn't use branches as part of it and you get 100 build configurations for free with 3 build agents.  Bamboo can't nearly match that right now.  It's too bad because I like the design of Bamboo better.  Jenkins Blue Ocean is probably the next best bet.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published 2 hours ago in Jira Ops

Jira Ops Early Access Program Update #1: Announcing our next feature and a new integration

Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...

40 views 0 3
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you