-
Notifications
You must be signed in to change notification settings - Fork 63
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
Can not run maven flyway in Kitodo-DataManagement module #6153
Comments
I tried it on a clean git master with reverted commit 144b93f and get a different error:
|
|
Other Maven commands (for example |
I did not get your error - instead the flyway validation / migration did work from the Kitodo-DataManagement module:
The mentioned errors here are excepted as my local database was not already migrated.
Not for me:
Running the flyway migration from the source root directory did not work in the past and there was no changes which made running from the source root directory working. |
No, this did not help. I got with this a similar error message like running on the source root directory:
Only working way for me is to revert the changes of PR #6127. |
Isn't flyway migration (started from the source root directory) part of the normal GitHub CI action? See latest build protocol. |
It looks like you have different configurations for the database, and only the first one works:
|
Interesting to know that this could even work from source root directory but this did not work on my local setup.
Because I have many databases with many different migration states? Even with the first mentioned entry |
Yes, but the log which you provided for the source root case failed because it used a different database. The |
Okay, here is the log
No difference. |
I tried all 4 variations: with and without PR #6127 and starting the validation / migration from source root or from Kitodo-DataManagement directory. |
This plugin is required for the Maven CI friendly multi module setup, see https://maven.apache.org/maven-ci-friendly.html#install-deploy. Fixes: 144b93f ("Use special property `revision` to set the version only once") Signed-off-by: Stefan Weil <[email protected]>
This plugin is required for the Maven CI friendly multi module setup, see https://maven.apache.org/maven-ci-friendly.html#install-deploy. Fixes: 144b93f ("Use special property `revision` to set the version only once") Signed-off-by: Stefan Weil <[email protected]>
There exist now two pull requests which fix this issue:
Only the 2nd alternative allows new use cases like having several builds in the same source tree by using |
This plugin is required for the Maven CI friendly multi module setup, see https://maven.apache.org/maven-ci-friendly.html#install-deploy. Fixes: 144b93f ("Use special property `revision` to set the version only once") Signed-off-by: Stefan Weil <[email protected]>
This plugin is required for the Maven CI friendly multi module setup, see https://maven.apache.org/maven-ci-friendly.html#install-deploy. Fixes: 144b93f ("Use special property `revision` to set the version only once") Signed-off-by: Stefan Weil <[email protected]>
This plugin is required for the Maven CI friendly multi module setup, see https://maven.apache.org/maven-ci-friendly.html#install-deploy. Fixes: 144b93f ("Use special property `revision` to set the version only once") Signed-off-by: Stefan Weil <[email protected]>
This plugin is required for the Maven CI friendly multi module setup, see https://maven.apache.org/maven-ci-friendly.html#install-deploy. Fixes: 144b93f ("Use special property `revision` to set the version only once") Signed-off-by: Stefan Weil <[email protected]>
This plugin is required for the Maven CI friendly multi module setup, see https://maven.apache.org/maven-ci-friendly.html#install-deploy. Fixes: 144b93f ("Use special property `revision` to set the version only once") Signed-off-by: Stefan Weil <[email protected]>
This plugin is required for the Maven CI friendly multi module setup, see https://maven.apache.org/maven-ci-friendly.html#install-deploy. Fixes: 144b93f ("Use special property `revision` to set the version only once") Signed-off-by: Stefan Weil <[email protected]>
This plugin is required for the Maven CI friendly multi module setup, see https://maven.apache.org/maven-ci-friendly.html#install-deploy. Fixes: 144b93f ("Use special property `revision` to set the version only once") Signed-off-by: Stefan Weil <[email protected]>
This plugin is required for the Maven CI friendly multi module setup, see https://maven.apache.org/maven-ci-friendly.html#install-deploy. Fixes: 144b93f ("Use special property `revision` to set the version only once") Signed-off-by: Stefan Weil <[email protected]>
This plugin is required for the Maven CI friendly multi module setup, see https://maven.apache.org/maven-ci-friendly.html#install-deploy. Fixes: 144b93f ("Use special property `revision` to set the version only once") Signed-off-by: Stefan Weil <[email protected]>
This plugin is required for the Maven CI friendly multi module setup, see https://maven.apache.org/maven-ci-friendly.html#install-deploy. Fixes: 144b93f ("Use special property `revision` to set the version only once") Signed-off-by: Stefan Weil <[email protected]>
This plugin is required for the Maven CI friendly multi module setup, see https://maven.apache.org/maven-ci-friendly.html#install-deploy. Fixes: 144b93f ("Use special property `revision` to set the version only once") Signed-off-by: Stefan Weil <[email protected]>
This plugin is required for the Maven CI friendly multi module setup, see https://maven.apache.org/maven-ci-friendly.html#install-deploy. Fixes: 144b93f ("Use special property `revision` to set the version only once") Signed-off-by: Stefan Weil <[email protected]>
Describe the bug
Running the validation or migration of FlyWay through
mvn flyway:validate -Pflyway
in the Kitodo-DataManagement module results in the errorThe error message points to wrong artifact descriptor
${revision}
which is not available. This was introduced by PR #6127To Reproduce
mvn flyway:validate -Pflyway
ormvn flyway:migrate -Pflyway
Expected behavior
Running the maven flyway for validation or migration in the Kitodo-DataManagement module should always be possible
Release
master branch (sha ee97b68)
The text was updated successfully, but these errors were encountered: