Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-40052

Can't start Confluence with atlas-run-standalone

    XMLWordPrintable

Details

    • Bug
    • Resolution: Answered
    • Low
    • None
    • 5.9.1
    • None

    Description

      Hi,

      When running atlas-run-standalone -v 5.9.1 --product confluence, the startup fails and Confluence is locked.

      It's most probably because com.atlassian.confluence.plugins:confluence-plugin-test-resources:zip:5.9.1 is not created properly, if I may guess.

      If so, it's not an AMPS/SDK issue, it's in the Confluence build. The Confluence build is supposed to start Confluence, define an H2 file-based database, perform a few initialization steps (including setting up the developer license), then stop Confluence and zip the target directory into com.atlassian.confluence.plugins:confluence-plugin-test-resources:zip:5.9.1. This is the artifact which is used by the SDK to kick start Confluence with some existing data.

      Context, if you're not familiar with it:
      AMPS loads the by default. It uses the same version as the version of Confluence. It is unzipped by AMPS in the target directory (target/{instanceId}/home, with instanceId=confluence ).

      Not only a good zip saves 10 minutes to all ecosystem developers per build, but also it helps us test various versions of Confluence with atlas-run-standalone. It's important that it works.
      Thank you!

      Attachments

        Activity

          People

            Unassigned Unassigned
            b8479dcaf688 Adrien Ragot 2
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: