Conversation
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.
pdurbin
reviewed
Oct 22, 2024
Member
pdurbin
left a comment
pdurbin
left a comment
There was a problem hiding this comment.
Overall, looks good. I added a suggestion.
Co-authored-by: Philip Durbin <philip_durbin@harvard.edu>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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