New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Precondition onFail="WARN" doesn't work properly #1389
Labels
DBAll
hacktoberfest
a month-long celebration of open-source software and Developers contribute by completing PRs
ImpactLow
IntegrationAny
Severity3
TypeBug
Comments
ro-rah
added
the
hacktoberfest
a month-long celebration of open-source software and Developers contribute by completing PRs
label
Sep 28, 2020
➤ Pavlo Tytarchuk commented: Moving to 'Ready to Merge'. Verified with version 4.2.0-LB-654-SNAPSHOT #2 on Windows 10. |
This was referenced Nov 16, 2020
This was referenced Nov 16, 2020
This was referenced Dec 7, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
DBAll
hacktoberfest
a month-long celebration of open-source software and Developers contribute by completing PRs
ImpactLow
IntegrationAny
Severity3
TypeBug
Environment
Windows 10, Oracle
Liquibase Version: version 3.10.2-SNAPSHOT #19
Liquibase Integration & Version: CLI
Description
If you add precondition with attribute onFail="WARN" to your changelog and this precondition fails, liquibase doesn't show WARN message.
Steps To Reproduce
[^changelog.xml]
Actual Behavior
Liquibase successfully executes update command without showing any WARN message.
!changelog.png|width=200,height=183!
!cmd_result.png|width=200,height=183!
!properties.png|width=200,height=183!
Expected/Desired Behavior
Liquibase should show WARN message that database on which you run the changelog is different from the database specified in the preconditions.
The text was updated successfully, but these errors were encountered: