You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happens here is that we prime a remote-cache (local directory) with a database migration. Then we checkout another branch where said migration has been renamed and we delete target directories to simulate another developer. We then pull from the cache, compile and run flyway. This fails, because somehow two migration resources end up in a target directory, which isn't going to work.
Expectation
I think this is an unexpected outcome. It's certainly extremely detrimental to our use case, which is speeding up CI. The use of caching ends up destroying pipelines and requires manual intervention from us.
I think that I expect compile output to always be identical whether a cache is used or not, provided that 1) compiling is deterministic and 2) I trust the cache. Now, I know Scala compilation isn't entirely deterministic, but that's beyond the point here. I still expect the compile output to the correct / working, but not necessarily identical.
Notes
OS: Arch Linux
Sbt version: 1.4.6
Java version: openjdk 11
The text was updated successfully, but these errors were encountered:
Steps
.. then run the command described in the readme and watch Flyway fail.
Problem
What happens here is that we prime a remote-cache (local directory) with a database migration. Then we checkout another branch where said migration has been renamed and we delete target directories to simulate another developer. We then pull from the cache, compile and run flyway. This fails, because somehow two migration resources end up in a target directory, which isn't going to work.
Expectation
I think this is an unexpected outcome. It's certainly extremely detrimental to our use case, which is speeding up CI. The use of caching ends up destroying pipelines and requires manual intervention from us.
I think that I expect compile output to always be identical whether a cache is used or not, provided that 1) compiling is deterministic and 2) I trust the cache. Now, I know Scala compilation isn't entirely deterministic, but that's beyond the point here. I still expect the compile output to the correct / working, but not necessarily identical.
Notes
The text was updated successfully, but these errors were encountered: