Confluence 7.13 Long Term Support release EAP available now

[NathanMudaliar]

Hi everyone,

The first Confluence 7.13 EAP milestone is available now! EAP releases provide a snapshot of our work-in-progress and give you an opportunity to test and fix your apps before the final release.

Confluence 7.13 is a Long Term Support release, so we’re not including any new features or significant changes. This release is focused on bug fixes to support our largest customers.

We will continue our regular cadence of weekly milestones and betas during the development of Confluence 7.13. Head to Preparing for Confluence 7.13 to find out what’s changed.

Get the latest EAP

If you have any problems with an EAP release, please raise an issue to let us know. The earlier we know about problems, the more time we’ll have to fix them before the final release.

Enjoy!

[TureHoefner]

Hello @NathanMudaliar,

I don’t see the image for 7.13 EAP in your docker hub: Docker

Also, when it is there can it please be tagged under the label “eap” so that we can automatically update our EAP servers by pulling the latest image with the eap tag. That’s how we did Confluence 7.12 EAP. The ‘eap’ tag currently has Confluence 7.12 beta 1 in it. Docker

See the announcement for a previous EAP, we worked through this issue there:

Confluence Server 7.9 beta is available now

Thank you @NathanMudaliar. I verified that 7.9.0-m41 is the most recent release tagged ‘eap’ in your docker repo. That is not this “7.9 beta 1” you are talking about is it? Now that Atlassian is using the ‘eap’ label in docker hub it is easy for us to upgrade our EAP/beta server. Just need to restart the docker container: Docker, but we can’t upgrade to 7.9-beta1 if it isn’t tagged in docker hub. Our docker-compose.yml contains the ‘eap’ tag like this: confluence: image: atlassian…

Also here: Confluence Server 7.8 beta is available now - #3 by TureHoefner

Thanks!

[NathanMudaliar]

Thanks @TureHoefner, we refactored the tooling for running builds and forgot to include the flag for building the Confluence EAP. We’re adding the flag to the pipelines configuration – the PR has been merged.

[TureHoefner]

Thanks for the quick response @NathanMudaliar! The new EAP was quickly available in the docker hub after you addressed this.

For the developers/testers out there who aren’t using docker for their EAP servers or are using docker but aren’t using the ‘eap’ label, I highly recommend it:

From my docker-compose.yml:

...
...
... 
   confluence:
        image: atlassian/confluence-server:eap
...
...
...

So I don’t edit my docker file to change the image when a new EAP is released. I just stop the server, pull the new image that is at the eap label, and start it.

I have a feeling that not many of you are using the eap label because I’ve been the only one complaining when it has been broken for the past few EAP releases. It’s something everyone should probably be using (imo)