Description:
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. For this PR, we are adding a bullet under the Infrastructure of Testing section of the QA Guide to provide a solution.
Added statement under QA Guide> Infrastructure of Testing> 6. When a Jenkins job fails after a release, it might be due to the version number in the 'pom.xml' file not being updated in the pull request (PR). To Verify this, open the relevant GitHub ticket, navigate to the PR branch, and go to 'dataverse>modules>dataverse-parent>pom.xml'. Look for the version number, typically shown as '6.3', and ensure it matches the current Dataverse build version.
Description: 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. For this PR, we are adding a bullet under the Infrastructure of Testing section of the QA Guide to provide a solution.
Added statement under QA Guide> Infrastructure of Testing> 6. When a Jenkins job fails after a release, it might be due to the version number in the 'pom.xml' file not being updated in the pull request (PR). To Verify this, open the relevant GitHub ticket, navigate to the PR branch, and go to 'dataverse>modules>dataverse-parent>pom.xml'. Look for the version number, typically shown as '6.3 ', and ensure it matches the current Dataverse build version.
Preview at https://dataverse-guide--10951.org.readthedocs.build/en/10951/qa/testing-infrastructure.html