Confluence is a collaboration and content sharing platform used primarily by customers who are already using Atlassian's Jira project tracking product. The product appeals particularly to IT users.
$6.40
per month per user
CloudBees Continuous Integration
Score 8.9 out of 10
N/A
CloudBees Continuous Integration (formerly the CloudBees Jenkins Platform) is a continuous integration (CI) and continuous delivery (CD) solution that extends Jenkins. Developed for on-premise installations, CloudBees CI offers stable releases with monthly updates, as well as additional proprietary tools and enterprise features to enhance the manageability and security of Jenkins. CloudBees CI helps administrators manage growing installations due to ever-increasing teams, projects and jobs…
N/A
Pricing
Atlassian Confluence
CloudBees Continuous Integration
Editions & Modules
Free
$0
Free for 10 Users
Standard
$6.40
per month per user
Premium
$12.30
per month per user
Data Center
220,000.00
40,001+ Users - Annually
Enterprise
Contact Sales
No answers on this topic
Offerings
Pricing Offerings
Confluence
CloudBees Continuous Integration
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
Optional
Additional Details
Prices shown here reflect prices for deployments with 100 users or less. The prices decrease wien the user base surpasses 100.
—
More Pricing Information
Community Pulse
Atlassian Confluence
CloudBees Continuous Integration
Considered Both Products
Confluence
No answer on this topic
CloudBees Continuous Integration
Verified User
Team Lead
Chose CloudBees Continuous Integration
Easy to lean, use, highly customizable pipelines, works well for version control, etc. Example Digital.ai gives all those features which can be done in Jenkins like builds, deployment, release management, etc. But, it requires universal templates to be created which are …
It is well suited due to the below reasons 1. Easy collaboration between teams 2. Strong integration with other applications 3. Centralized documentation among teams and within the organisation 4. Project planning and report sharing 5. Employee onboarding is easier and maintain HR policies very well. Less appropriate in below scenarios When this is being used as a main tool for communication rather than its purpose of collaboration.
For all continuous integration features like multi branch pipeline, continuous build, and deployment execution, highly customizable groovy scripting, well integration with most of repositories like SVN, GIT, etc. are some of the exceptional features which helps devOps related tasks a treat to work everyday. With some minor changes in agent configuration and handling of their configuration on master instances would reduce a lot of issues. Also, cache of maven handling on agents needs to be improved (though not related to tool but the CI pipelines). But, since this is a very mature and performant tool, we expect some out of the box functionalities to handle all such scenarios. Overall, the tool works wonders because of its highly customizable features.
Cross product linking - If you use other Atlassian products then Atlassian Confluence is a no-brainer for your source of documentation, knowledge management etc. You can show previews of the linked asset natively E.g. showing a preview of a JIRA ticket in a Atlassian Confluence page.
Simple editing - Though the features available may not be super complex right now, this does come with the benefit of making it easy to edit and create documents. Some documentation editors can be overwhelming, Atlassian Confluence is simple and intuitive.
Native marketplace - If you want to install add-ons to your Atlassian Confluence space it's really easy. Admins can explore the Atlassian marketplace natively and install them to your instance in a few clicks. You can customise your Atlassian Confluence instance in many different ways using add-ons.
UI Design is very simplistic and basic could make use of more visually interesting colour choices, layout choices, etc.
Under the 'Content' menu, it defaults to having a landing page for all L1 and L2 category pages. Meaning as long as the broader content category has a sub-category, it still creates a separate landing page. In my team's case, this often creates blank pages, as we only fill out the page at the lowest sub-category (L3).
Hyperlinks are traditionally shown as blue, however, this results into very monotonously blue pages in cases where a lot of information is being linked.
I am confident that Atlassian can come with additional and innovative macros and functions to add value to Confluence. In 6 months, Atlassian transformed a good collaborative tools into a more comprehensive system that can help manage projects and processes, as well as "talk" with other Atlassian products like Jira. We are in fact learning more about Jira to evaluate a possible fit to complement our tool box.
Atlassian Confluence is a great tool for project management, especially for internal documentation. It has a minimum governance requirement to use its full power. Also, it is a little pricy to unlock its full power as well, so it is not recommended for companies with a low budget in my opinion.
We never worked against the tide while using Confluence. Everything loads considerably fast, even media components like videos (hosted on the platform or embed external videos from Youtube, for example). We are not using heavy media components a lot, but in the rare occasion we happen to use one we have no problems whatsoever.
This rating is specifically for Atlassian's self-help documentation on their website. Often times, it is not robust enough to cover a complex usage of one of their features. Frequently, you can find an answer on the web, but not from Atlassian. Instead, it is usually at a power user group elsewhere on the net.
Support seems very unreachable from my experience. They handle cases if developers are facing issues, support seems to be very limited. It's not like other tools in a market where every mail is being taken priority and responses are sent. We see a lack in this particular aspect when it comes to CloudBees Jenkins Platform.
We chose Atlassian Confluence over SharePoint because it's much more user-friendly and intuitive. Atlassian Confluence makes collaboration and knowledge sharing easier with its simpler interface and better search. While SharePoint can be powerful, it often feels clunky and complex, making it harder for our team to actually use it.
CloudBees Jenkins Support is on par with the other enterprise tools we're currently using. It has performed well enough that we've adopted the product and placed it in the critical path of our software delivery pipelines.
We totally rely on this tool since a decade now and despite being so much transition in our company it has served us well in those transitions
Many times, during security audits we are asked to showcase our readiness for various compliance points and confluence helps us a lot in maintaining that
Talking about Confluence in front of clients and customers gives us an upper hand that we are up to date with latest trend and technologies and tools for our RnD planning and management
