Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Why bamboo takes the branch as a job.

I'm using the standard version of bamboo. I know it's limited to 10 jobs. I have define only one job. But now there is a message on page footer saying: Unleash the full power of Bamboo - Upgrade to unlimited jobs and remote agents today! (1 free jobs remaining). Why this is happening, my thoughts are that you are taking a branch execution as a new job, because I deleted one and decreased that number. In that job I have setup the Plan Branch. Please this is how it have to be, I'm wrong? Please need some help.


Thanks in advance! 

1 answer

0 votes

Hi @Carlos Luis Castro Marquez,

That is how Bamboo works by design when using an starter license. The details on how this type of license work are stated in the Starter Licensing and Pricing page.

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

I hope that can clarify this scenario.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events