Failing to start Confluence 5.5.7 with atlas-run

1

I’m trying to test my plugin against an older version of Confluence. According to the Atlassian SDK docu, I should be able to do so by running atlas-run --version 5.5.7. However, when I do that, Confluence starts version 5.10.9. Can anybody point me towards what I’m doing wrong here?

2

Hm, if you are familiar with Docker (compose,) use this image and a postgres db

https://hub.docker.com/r/cptactionhank/atlassian-confluence/tags?page=1&name=5.5.7

The docker-compose.yml may look something like this:

version: "3.7"
services:
    confluence-5-5-postgresql:
        image: postgres:9.3.25
        container_name: confluence-5-5-db
        restart: "no"
        environment:
            POSTGRES_USER: root
            POSTGRES_PASSWORD: 12345
        ports:
            - 5432:5432
        volumes:
            - /var/lib/postgresql/data

    confluence-5-5-confluence:
        image: cptactionhank/atlassian-confluence:5.5.7
        container_name: confluence-5-5
        ports:
            - 1990:1990
            - 8091:8091
            - 5005:5005
        environment:
            - "X_PATH=/confluence"
            - "X_PROXY_PORT=1990"
            - "JAVA_OPTS=-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=5005"
            - "orchestra.sync.job_cron_expression.default_value=* * * ? * * *"
            - "orchestra.sync.job_max_tries.default_value=999"
        volumes:
            - ./.docker/confluence-home:/var/atlassian/confluence
3

Thanks for offering the alternative. Good to know there’s a workaround available.

But my question was merely whether I’m doing something wrong, or whether I’m lacking some understanding how atlas-run is supposed to work. Shouldn’t running atlas-run --version 5.5.7 start the proper Confluence version? If so and it doesn’t do the trick for me, am I running into a bug with the plugin SDK?

4

You may try an older version of AMP, maybe the newer version is just not working with this “ancient” Confluence.

5

Good point. Might give it a try the next time I need to test against ancient product versions. I also raised a bugreport for this issue now, as it surely looks like a bug from a user’s point of view: [ATLASSDK-207] - Ecosystem Jira