-
Notifications
You must be signed in to change notification settings - Fork 30
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
Adding proper travis integration #1
Conversation
8f8291d
to
8449765
Compare
8449765
to
e9df1cb
Compare
@VicDeo seriously - did these unit tests ever work? |
|
9a3bd73
to
a8ef207
Compare
@DeepDiver1975 Loooooong time ago. |
sounds reasonable - thx - please keep migration in mind to copy over data from the old table to the new - THX |
If the DB schema still have Should I dump the table into a file inside the preupgrade script and restore the data from this file when the new table is ready? |
why? unit test have to run in a predefined environment.. The migration should rename the existing table - as far as possible with the given dbms |
@VicDeo can we please gain some momentum on this? THX |
0746a52
to
2e168e0
Compare
@DeepDiver1975 yes, sir! |
great - thx 👍 |
Adding proper travis integration
change recipient name if user_ldap is used
basic travis integration is done - ready to merge - failing unit tests have to be fixed by @VicDeo