Man. This is a really "open" question. This kind of hardware measure depends on a lot of things:
Maybe other people "basic setup" for Bamboo just applies to their Infrastructure ;)
On internal Atlassian instances we have 16GB on physicaly servers and 8GB inside a virtual machine (KVM).
Base OS is RHEL 5 though migrating to Scientific Linux 6.1. We use Postgres 8.4 on a separate host for the DB.
We try to get at least 16 CPU cores and around 600GB of disk space. All shared artifacts, results and logs are stored on the Bamboo server (after the build), not on the agents. So you want to plan for that.
This scales up pretty well to around 200-400 build plans, 60-120 remote agents. We really try to avoid monolithic, centralised instances choosing instead to give individual Product teams the flexibility and autonomy of their own instance. It has nothing to do with performance, though, it just gives the teams more control and motivation to really own the 'greenness' of their builds.
Bamboo is very chatty so also make sure you have good network connectivity, gigabit ethernet at least. Check the throughput against your source code repos. If you're doing builds based on polling, you'll be hitting them hard.
You'll also need lots of open file descriptors on the server (8192 is a good number but that depends on the number of agents you'll have and how many builds will be executing at any one time)
Two vulnerabilities have been published for Confluence Server and Data Center recently: March 20, 2019 CVE-2019-3395 / CVE-2019-3396 April 17, 2019 CVE-2019-3398 The goal of this article is...
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!
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