-
Notifications
You must be signed in to change notification settings - Fork 23
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
rebar3 appup fails - new release overwriting old "previous version apps" #47
Comments
I just tried again, reversing the order: checkout out OLDER version So what I am seeing is that the order of the "rebar3 release" matters - and I'm not sure why. Is this a expected behavior ? |
i haven't yet had time to dig into this, i think the latest release you build is marked as the current one and this is what influences the results you're seeing, but still, i don't have confirmation yet |
@lrascao This is the "previous version" that is being overwritten though, not the current version |
hey, sorry for the lag, did some more digging, found the following using
Issue is |
Environment
-bash-4.2$ rebar3 report
Current behaviour
Attempting to generate an appup from an old release. First, I removed the whole _build directory. Then, on the most up-to-date version, 0.4.1, I ran rebar3 release:
This makes sense - we removed the whole build directory, so there should be no release for "0.4.0". So now build that release:
Here is where the unexpected behaviour comes in - the previous version apps should be 0.4.0, not 0.4.1.
No .appup is generated. It appears that when I run rebar3 release on any newer version, the old version is overwritten. How could this be/how can I prevent this?
Expected behaviour
Expect an appup file to be generated in my _build/default/lib/backend_debug_client/ebin/ directory.
The text was updated successfully, but these errors were encountered: