-
Notifications
You must be signed in to change notification settings - Fork 27
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
Add shared matrix.json for actions #11
Conversation
0bef04a
to
684fcd5
Compare
b1939bb
to
5a09e5b
Compare
5a09e5b
to
e823943
Compare
ee1a40d
to
7aed38a
Compare
7aed38a
to
e823943
Compare
@akuleshov7 @petertrr could you please tell is "matrix" the only way to parametrize the build? |
There is also an option with triggering a workflow manually and providing parameters as inputs: https://docs.github.com/en/actions/learn-github-actions/events-that-trigger-workflows#workflow_dispatch. I haven't tried this approach myself, though. In our projects the only parameter we use is a git tag, and we deduce current version from it. We use matrix only when it's required to execute CI in different environments, like different OS, different JDK version and so on. |
@korifey also there is no mechanism for sharing the os matrix between actions, and I suppose it is done intentionally. In this case you will always understand what you are doing and in which OS. Are you sure that you really need that? |
@akuleshov7 in our build, we have to make same dependency in several places of yml. This piece of code:
|
@petertrr here I misused word "parameter". I mean that we need some constants storage, like .properties in Java for deduplication of exact versions like |
@ladisgin LGTM! |
No description provided.