-
Notifications
You must be signed in to change notification settings - Fork 629
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 a directive that allows the fetching of tool version meta information #879
Comments
This may required #540 |
Also this version should be collected to include in the execution report and trace report. As possible extension it should be possible to collect these information using a channel and send to a reporting process (reads MultiQC). |
Brainstormed a bit more with @emi80 about this. Since each task can potentially use a different container or run in a different host with a different env (when container are not used). The proper way to handle this would be to executed the The |
Yes, I guess having it on task level is better. Shouldn’t be too tricky to collapse duplicates for MultiQC etc.. |
This comment has been minimized.
This comment has been minimized.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Bump |
(sorry for the spam! 😄) |
No problem! I'm not bumping all of these, I'm letting the ones I don't care about much die quietly 😅 |
Solved by eval output type #4493 |
The goal of this proposal is to add a process directive that allow the user to specify one-liner command to be executed as very first execution to fetch the tool command version. For example:
The version command should be executed as the specified by the process configuration i.e. using the provided executor/container/module settings.
More than one
versionCmd
should be possible.To avoid to spawn multiple jobs the
versionCmd
command should be prefixed to the real command script execution, only the first time. Moreover the version command should be trigger each time a dynamic container or module configuration is applied.The text was updated successfully, but these errors were encountered: