Repository navigation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #150
#150
The build log message listed the current revision first:
Last changes from revision 27ad83a (current) to a511a43 (previous) published successfully!
It now reads from the previous revision to the current one:
Last changes from revision a511a43 (previous) to revision 27ad83a (current) published successfully!
Only the message text and argument order change.
Testing done
Updated the existing log assertions in
LastChangesTestandLastChangesPipelineTestto the new wording; these tests run the publisher and check the printed message, so they execute the changed line. Ran them locally:mvn -Dtest='LastChangesTest,LastChangesPipelineTest' test15 tests run, 0 failures (1 skipped by an existing
@Disabled).Submitter checklist