-
Notifications
You must be signed in to change notification settings - Fork 518
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 version
compiles dependencies before outputting value
#2865
Comments
rebar3 version has no command dependencies and does not require compiling before outputting a version. An exception can be made for this specifically for global plugins if they are defined in a global configuration file, because a global project plugin could override the |
Now that I think about it, calling |
Oh, cool. I can live with |
What are we fixing? If you're with'ing "version-file": ".tool-versions" after you _use_ "actions/checkout", it's likely `rebar3` from `setup-beam` is compiling your project just to output its version This commit prevents that as per erlang/rebar3#2865 (comment)
What are we fixing? If you're with'ing "version-file": ".tool-versions" after you _use_ "actions/checkout", it's likely `rebar3` from `setup-beam` is compiling your project just to output its version This commit prevents that as per erlang/rebar3#2865 (comment)
What are we fixing? If you're with'ing "version-file": ".tool-versions" after you _use_ "actions/checkout", it's likely `rebar3` from `setup-beam` is compiling your project just to output its version This commit prevents that as per erlang/rebar3#2865 (comment)
If I recall correctly you can also grab the version from the top of the escript, but it won't be as complete:
The full version gives specific hashes with the OTP version and is more useful. |
What are we fixing? If you're with'ing "version-file": ".tool-versions" after you _use_ "actions/checkout", it's likely `rebar3` from `setup-beam` is compiling your project just to output its version This commit prevents that as per erlang/rebar3#2865 (comment)
Cool, thanks. At the moment I'm running it, though, making sure it's executable, and in the path, is also part of the test 😄 |
What are we fixing? If you're with'ing "version-file": ".tool-versions" after you _use_ "actions/checkout", it's likely `rebar3` from `setup-beam` is compiling your project just to output its version This commit prevents that as per erlang/rebar3#2865 (comment)
What are we fixing? If you're with'ing "version-file": ".tool-versions" after you _use_ "actions/checkout", it's likely `rebar3` from `setup-beam` is compiling your project just to output its version This commit prevents that as per erlang/rebar3#2865 (comment)
What are we fixing? If you're with'ing "version-file": ".tool-versions" after you _use_ "actions/checkout", it's likely `rebar3` from `setup-beam` is compiling your project just to output its version This commit prevents that as per erlang/rebar3#2865 (comment)
Pre-Check
Environment
rebar3
3.22.1Current behaviour
My use case is as follows:
erlef/setup-beam
'sversion-file
(e.g..tool-versions
) build optionactions/checkout
before I useerlef/setup-beam
(because my.tool-versions
is checked in to my project - for CI/local sync. purposes)erlef/setup-beam
the action attempts to output the chosenrebar3
version, for debugging purposes, viarebar3 version
rebar3 version
)My question is: is it absolutely necessary that
rebar3 version
attempts compilation?Expected behaviour
No compilation should be required for
rebar3 version
.The text was updated successfully, but these errors were encountered: