Make WAR file version dynamic in IQSS_Dataverse_Internal Jenkins job #49
Conversation
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
Added VERSION=$(...) to read the actual version from modules/dataverse-parent/pom.xml. Built WARFILE dynamically from that version. Replaced all dataverse-5.13.war with $WARFILE. Preserved the server details and path you had in the original XML. Left chmod in place
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR updates the IQSS_Dataverse_Internal Jenkins job configuration to dynamically detect the WAR file version from modules/dataverse-parent/pom.xml instead of hardcoding it.
Changes made:
With this change, the Jenkins job will automatically use the correct WAR file for any Dataverse release without additional maintenance.