Atlassian Bamboo vs. JRebel

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Atlassian Bamboo
Score 6.7 out of 10
N/A
Australian company Atlassian offers Bamboo, a continuous integration server.
$1,200
JRebel
Score 8.0 out of 10
N/A
JRebel is a build automation tool developed by Estonian company ZeroTurnaround, acquired by Rogue Wave Software in 2017, and then acquired (and now supported by) Perforce since that company's 2019 acquisition of Rogue Wave. The vendor says users of JRebel saves Java teams a month of coding time per year on average.N/A
Pricing
Atlassian BambooJRebel
Editions & Modules
1 Remote Agent
$1200
5 Remote Agents
$3200
10 Remote Agents
$5840
25 Remote Agents
$11,600
100 Remote Agents
$23,280
250 Remote Agents
$58,160
500 Remote Agents
$87,280
1000 Remote Agents
$133,840
2000 Remote Agents
$187,380
No answers on this topic
Offerings
Pricing Offerings
Atlassian BambooJRebel
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
Atlassian BambooJRebel
Considered Both Products
Atlassian Bamboo
Chose Atlassian Bamboo
We selected Bamboo because its capabilities to integrate with other Atlassian products specially Jira Software, Bitbucket and in some useful scenarios with Confluence. Also, we found these pros important for us: great user interface, easily agent deployment, Docker …
Chose Atlassian Bamboo
Bamboo's ability to integrate with Bitbucket and Jira (the other two key systems we use) pretty much sealed the deal on our decision to choose Bamboo over other alternatives. Being able to map every build result back to the relevant code changes and Jira issues are just too …
Chose Atlassian Bamboo
Jenkins is the only other we had briefly considered for continuous deployment type of products, but being open source could not get the same level of reliability and support offered from Bamboo's product maturity.
Chose Atlassian Bamboo
Bamboo has a friendlier interface than either TeamCity or Jenkins and has better integration with Jira and Bitbucket
Chose Atlassian Bamboo
We looked at Bitbucket and some other providers but they did not have the full requirements that we needed from a customization perspective. We wanted customization while keeping a lot of the configurability intact.
Chose Atlassian Bamboo
In the beginning we had selected Bamboo and were down the path of going all in for all of our projects. However after about a year we decided that Azure DevOps was better suited for our business needs. We are now in the process of migrating everything off of the Bamboo …
Chose Atlassian Bamboo
We used Jenkins before for our projects.
While Jenkins has an extensive plugins list that makes it more flexible to integrate it with other tools, we switched to Bamboo for nicer User Interface but mostly for the seamless integration with Jira and Bitbucket. Also Bamboo has more …
Chose Atlassian Bamboo
Bamboo is great tool when compared to the open-source alternative Jenkins, with mainly the same functionality in both it really shines with its integration of the Atlassian product line. Jenkins works really well with a huge community of users and plenty of plugins that are …
Chose Atlassian Bamboo
We chose Bamboo over Jenkins for 2 reasons - one, for its tight integration amongst all the products in the tool suite. We find explicit value in the traceability from JIRA issues all the way down to the Bamboo build that was triggered by the check in of those issues. The …
Chose Atlassian Bamboo
Bamboo has these advantages while asana does not:
  • Easy to configure
  • Easy to use
  • Clean UI and easy permission controls
Chose Atlassian Bamboo
Jenkins works great, but Bamboo is just fantastic when integrated with other Atlassian tools. Since we were using JIRA and Bitbucket, we went for Bamboo.
Chose Atlassian Bamboo
Bamboo's seamless integration with Bitbucket made it a simple choice, and I couldn't be happier with its ease of use, logging, and reliability.
Chose Atlassian Bamboo
We selected bamboo after a thorough review process, we considered the following aspects:
  • Ease of use, cost, scalability, plugins, setup and maintenance, community and product support
  • Made sure it integrated with JIRA and Confluence
Chose Atlassian Bamboo
I use bamboo because it is mandated as the CI/CD solution to use across the organization that I work for. If I were working on my own project, I would almost certainly use a free solution like Travis CI or just spin up my own build servers using Docker, AWS, or something like …
Chose Atlassian Bamboo
Bamboo won solely based on the fact we were "all-in" with Atlassian. TeamCity is now in the process of taking over as we transition off of Bamboo, and I think TeamCity stacks up nice against Bamboo thus far (too soon to tell).
Chose Atlassian Bamboo
Bamboo integrates directly with our bug system (Jira) and source control system (Bitbucket). It allows us to get what we need to done without worrying about how it works with our other systems.
Chose Atlassian Bamboo
Bamboo is hands-down the best of these options if you rely on other products of Atlassian origin. Bamboo is not just built for teams, but teams-of-teams and teams of many workers. It has the administrative features you need to manage and maintain CI at scale. Enterprise model …
Chose Atlassian Bamboo
I didn't select Bamboo. I mentioned how it compared in other parts of this review, but to summarize:

  • Pros: easier to use and cleaner UI
JRebel
Chose JRebel
Hot code swapping doesn't have many players...it's mainly JRebel. We use JRebel a lot in our backend code development where it minimizes our development cycle (20min down to 30sec). For Android, the competitor is Android Studio's Instant Run which works fairly well now. For …
Best Alternatives
Atlassian BambooJRebel
Small Businesses
GitLab
GitLab
Score 8.7 out of 10
GitLab
GitLab
Score 8.7 out of 10
Medium-sized Companies
GitLab
GitLab
Score 8.7 out of 10
GitLab
GitLab
Score 8.7 out of 10
Enterprises
GitLab
GitLab
Score 8.7 out of 10
GitLab
GitLab
Score 8.7 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Atlassian BambooJRebel
Likelihood to Recommend
6.4
(0 ratings)
10.0
(0 ratings)
Usability
9.3
(0 ratings)
-
(0 ratings)
Performance
-
(0 ratings)
10.0
(0 ratings)
Support Rating
7.3
(0 ratings)
-
(0 ratings)
User Testimonials
Atlassian BambooJRebel
Likelihood to Recommend
Large companies will find it particularly useful, but smaller companies and independent developers will not be able to afford the cost, and will not see many advantages compared to using an open source solution. However, having some software to handle continuous integration build servers as well as deployments, and doing this consistently between products, is absolutely essential.
Read full review
I recommend JRebel for Java developers, it will remove the time needed for redeployment, it will increase the focus on the task at hand (without being distracted by the redeployment) and will make them happier. I recommend JRebel for Java Development Managers, they should purchase this for their teams - it will increase productivity, decrease the product's time to market, and it will save money for the company. The ROI can be calculated upfront and presented to higher level management for approving this, if needed.
Read full review
Pros
  • Continuous Deployment - you can use Bamboo to automatically build and deploy whenever there are changes in the source code.
  • Continuous Integration - by integrating the automated tests and the integration tests before deploying you make sure you know immediately if the latest code fits into the whole scheme of apps.
  • Integration with Jira and Bitbucket.
  • Flexibility with the program language used for builds: Maven, Ant, PowerShell, any command line tools.
Read full review
  • Removes the time needed for redeployments of the source code - improves productivity, time to market, and saves money.
  • Easy to install
  • License renewals - the sales department reaches out to you long before the licenses expire so you can have time to get your approvals.
  • Analytics and reporting - it will show you the time saved by JRebel and even the ROI, if you input the average hourly cost of a developer.
Read full review
Cons
  • Extremely hard barrier to entry for non-backend developers
  • Blackbox makes it hard to customize functionality
  • The inability to add features without breaking core functionality
  • No cloud solution
  • Tasks cannot be put in if/else statements
  • No clear right way to form build plans
Read full review
  • Launch times are where JRebel is slower than Instant Run.
  • Sometimes, it has incompatibilities with how you wrote something and causes compile failures, but Zero turnaround is quick to respond.
Read full review
Usability
Bamboo offers solid usability for teams looking for an integrated, scalable CI/CD solution, especially those using Atlassian tools. Its interface is intuitive for existing Atlassian users, and its focus on deployment automation makes it a strong option for continuous delivery. However, its complexity and cost may pose challenges for small teams or those new to CI/CD. Overall, Bamboo’s usability shines in environments where ease of integration and streamlined workflows are prioritized. Still, it may require more effort for teams unfamiliar with its setup or without dedicated resources.
Read full review
No answers on this topic
Performance
No answers on this topic
The performance of JRebel is great. It is enabling the Java team to do hot re-deployments and it has to be transparent and fast for the user, otherwise the whole purpose of reducing wasted time with re-deployments doesn't make sense. Also the User Interface for License Server management and analytics loads fast and the navigation through pages is quick.
Read full review
Support Rating
Support for Bamboo has started lack a little over the years. Atlassian has been moving more towards Bitbucket Pipelines and away from the on-premise install of Bamboo. While the tool is still great, it may take a little bit of time to get a question answered by official support.
Read full review
No answers on this topic
Alternatives Considered
We chose Bamboo over Jenkins for 2 reasons - one, for its tight integration amongst all the products in the tool suite. We find explicit value in the traceability from JIRA issues all the way down to the Bamboo build that was triggered by the check in of those issues. The second reason was for support - we didn't want the burden of figuring out how to support Jenkins in our production environment, as can be the case with so many open source products.
Read full review
Hot code swapping doesn't have many players...it's mainly JRebel. We use JRebel a lot in our backend code development where it minimizes our development cycle (20min down to 30sec). For Android, the competitor is Android Studio's Instant Run which works fairly well now. For smaller apps, Instant Run is faster deploying but needs more full builds. With JRebel, you hardly ever need to do a full build.
Read full review
Return on Investment
  • Bamboo was neither very positive or negative. Most of our spend was in man hours on research and development
  • We felt it was worth it for larger projects
  • Smaller projects had too much setup and run and caused a negative ROI
Read full review
  • It sped up the developing time, and time is money for the company.
Read full review
ScreenShots