Mirrored_Repos/docker-atlassian-confluence-server
1
0
Fork 0
mirror of https://bitbucket.org/atlassian-docker/docker-atlassian-confluence-server.git synced 2024-08-30 18:22:16 +00:00
Code Issues Packages Projects Releases Wiki Activity

CLIP-1725: Update the func-test docs with instructions for re-dumping DB.

Browse Source
This commit is contained in:
Steve Smith 2022-11-30 11:49:47 +11:00
parent db4021532e
commit 34221bb0df
1 changed files with 24 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
func-tests/README.md
View File

@ -1,5 +1,28 @@
# Test data
The database dump and `confluence.cfg.xml.tmpl` are dumped from a 6.0.1
The database dump and `confluence.cfg.xml.tmpl` are dumped from a 7.11.6
instance.
## Updating the test data
Periodically Confluence will move forward far enough that it is unable to
upgrade databases from older unsupported versions. In this case you will need to
upgrade the database to the oldest supported version and re-dump the DB. Steps
to do this are:
* Generate a local Confluence image of the oldest supported version (see
[Atlassian Support End of Life Policy](https://confluence.atlassian.com/support/atlassian-support-end-of-life-policy-201851003.html).
* Run the func-tests up to the start of the smoke-tests (these won't start by
default if `CONFLUENCE_ADMIN_PWD` is not set.
* Stop the func-tests after the DB upgrade has run, then start the Postgres
instance (`docker-compose up postgres`).
* `exec` into the running postgres container and dump the DB with `pg_dump -U confluence confuence > confluence.sql`
* Copy the dump to `func-tests/postgres` and update the Dockerfile, scripts,
etc.
You may find that Confluence will fail to start with a `500` error after; this
may be due to an incompatible version in
`func-tests/confluence/confluence-home/confluence.cfg.xml.tmpl`. You can
retrieve the correct version from the error-message in the startup logs on the
image and update the file.