From c76eddd1a26431fa4233d1522d6a373dae363e40 Mon Sep 17 00:00:00 2001 From: ofahimIQSS Date: Tue, 22 Oct 2024 14:55:02 -0400 Subject: [PATCH] Update testing-infrastructure.md After a release, it's important to update the version number in the PR to match the latest release version. Failing to do so can cause the Jenkins build to fail. Ensure that the PR version number aligns with the current Dataverse version to avoid this issue. --- doc/sphinx-guides/source/qa/testing-infrastructure.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/doc/sphinx-guides/source/qa/testing-infrastructure.md b/doc/sphinx-guides/source/qa/testing-infrastructure.md index 6ec26c6da49..2055565289d 100644 --- a/doc/sphinx-guides/source/qa/testing-infrastructure.md +++ b/doc/sphinx-guides/source/qa/testing-infrastructure.md @@ -31,6 +31,8 @@ To build and test a PR, we use a job called `IQSS_Dataverse_Internal` on modules > dataverse-parent > pom.xml`. Look for the version number, typically shown as `6.3`, and ensure it matches the current Dataverse build version. + 1. If that didn't work, you may have run into a Flyway DB script collision error but that should be indicated by the server.log. See {doc}`/developers/sql-upgrade-scripts` in the Developer Guide. In the case of a collision, ask the developer to rename the script. 1. Assuming the above steps worked, and they should 99% of the time, test away! Note: be sure to `tail -F server.log` in a terminal window while you are doing any testing. This way you can spot problems that may not appear in the UI and have easier access to any stack traces for easier reporting.