Preparing for Confluence 6.1
This documentation is intended for Confluence developers who want to ensure that their existing plugins and add-ons are compatible with Confluence 6.1.
We plan to release frequent milestones during the development of Confluence 6.1. Watch this page to find out when a new milestone is available and what's changed. We won't be publishing formal release notes over at Development Releases until we release a beta.
Issues with this milestone?
Hit the Feedback button on the Confluence EAP header
or raise an issue to tell us about it.
Release Candidate - 9 March
We're getting close to a final release! This release candidate has the following changes.
- We've reduced the number of properties you need to pass when starting Synchrony standalone for Confluence Data Center. The essentials remain the same, but you no longer need to pass so many properties whose values do not matter. You can find the updated start Synchrony command at Installing Confluence Data Center.
- Bug fixes and improvements to the internal Synchrony proxy.
Try our AWS Cloud Formation Template
Want to take our new Confluence Data Center Cloud Formation Template for a test drive? It currently uses Confluence 6.1.0-beta2, so we don't recommend using it to spin up a production site, but we'd love your feedback if you are keen to try it out. The template uses EFS for the shared home directory, so you'll need to use an AWS region that offers EFS. You'll also need a VPC with at least two subnets and an EC2 Key Pair already set up.
To deploy Confluence Data Center using the Cloud Formation Template:
- In the AWS Console create a new stack.
Use the following Amazon S3 link to the Confluence Data Center Cloud Formation Template.
- Provide the following details:
- Confluence version
- Master password
- Database password
- Your VPC
- Two external and two internal subnets (must be in your VPC and in different availability zones).
- Your EC2 Key Pair.
- Leave the minimum and maximum number of nodes at the default for now - you'll add these later.
Once the create process is finished, grab the URL from the Outputs section and complete the Confluence setup wizard.
Some steps will be automatically completed for you (including the database configuration and clustering steps).Evaluation license...
You'll need a Data Center license to proceed. If you don't have one, you can use this evaluation license, which is good for 72 hours.
Go to > General Configuration > Clustering and confirm you can see one cluster node.
In the AWS Console, choose Update Stack and increase the minimum and maximum number of Confluence cluster nodes to 2. Leave the Synchrony nodes at 0 for now.
In Confluence, go to > General Configuration > Clustering and confirm you now have two cluster nodes.
It can take a minute or two for Confluence to detect the new node and connect to it.
In the AWS Console, Update Stack and increase the minimum and maximum number of Synchrony cluster nodes to 2.
In Confluence, go to > General Configuration > Collaborative Editing and change the Collaborative editing mode to On.
Wait for the Synchrony Status to change to Running. This can take a minute.
That's it! You're good to start editing pages.
We will also be making a Quick Start available with Confluence 6.1, which will automatically create your VPC - just bring yourself and your Key Pair, and it'll do the rest.
Want to know more? Check out the Atlassian Confluence Data Center Quick Start guide (PDF) and Running Confluence Data Center in AWS our EAP documentation.
If you have questions or any feedback, please or raise an issue to tell us about it.
Beta 2 - 17 February
- We have made some changes to ensure the internal Synchrony proxy is available with or without a Confluence context path. This means that it is no longer necessary to add /synchrony-proxy to any reverse proxy config. This improvement did involve a change to the setenv.bat / setenv.sh and server.xml files, so if you have any additional customisations in those files, you'll need to re-add them after upgrade (and not overwrite the files themselves).
- XML HTTP Request (XHR) fallback, which was experimental in Confluence 6.0, is now on by default. XHR fallback is used when a user cannot connect to Confluence via a WebSocket.
- Running Synchrony in Data Center requires some additional properties in order for it to start in Confluence 6.1. Please note that these properties don't have any affect in the Server distribution, so we are working on fixing this so these properties don't have to be supplied for the final release. Please see this page for the updated command to start Synchrony when trying the beta in Data Center.
Check out the full beta release notes.
Milestone 19 - 9 February
You can now start Confluence with all non-system add-ons disabled or with selected add-ons disabled by specifying the add-on key. This can be useful for troubleshooting when Confluence will not start up.Show me...
To temporarily disable all add-ons or specific add-ons on Linux:
To temporarily disable all add-ons or specific add-ons on Windows:
You can disable multiple add-ons using a colon separated list.
These parameters are applied at startup only, they do not persist. These parameters do not work with Confluence Data Center.
- We now bundle the SAML for Atlassian Data Center add-on, which means you can connect Confluence Data Center to a SAML 2.0 identity provider for authentication and single sign-on.
- We've worked with AWS to create a Quick Start for Confluence Data Center 6.1. The Quick Start will help you to get a Data Center cluster running in AWS (complete with database and load balancer) in minutes. The following diagram depicts the architecture.
More info, and an AWS Quick Start Guide, will be provided closer to release.
- Embedded Crowd (user management) upgraded to 2.3.
Milestone 15 - 30 January
- No notable changes in this milestone.