-
The `logs` command output may be significant in case a workflow has many steps.
It will be useful to allow getting outputs of some particular step, for example:
```
$ reana-client logs -w bsm -…
-
- Refactor workflow restart/rerun using the same workspace as a new run, which will help for future accounting.
- Save workspace path in workflow model, will help for future EOS workspaces.
-
We shall implement https://github.com/reanahub/reana-client/issues/202#issuecomment-441049790 which is the first approach of `reana-client workflow continue` command but in a more simple way, allowing…
-
Once a user has many runs, it is a bit messy as one can see here (`reana-client` version 0.6.0):
```console
$ reana-client list
NAME RUN_NUMBER CREATED STATUS
recastr…
-
The execution of this example currently fails using HTCondor at CERN:
```console
$ more reana_job.6711471.0.out
command to execute: root -b -q code/gendata.C(20000,\"results/data.root\") | tee ge…
-
Currently, `reana-client du` and `reana-client list --verbose` will give information about workspace disk usage. The information is printed in human-friendly way, e.g.
```console
$ reana-client d…
-
Currently, we only allow deletion of workflows in the following states: `created`, `finished`, `stopped`, `failed` (code [here](https://github.com/reanahub/reana-workflow-controller/blob/master/reana_…
-
**Motivation**
It would be nice to enrich the output of `reana-client logs` so that the logs would include important information of interest to the user, such as command to run and the execution en…
-
-
During the coming workshop, we will have around 30~ people using REANA. Potentially, in the afternoon session, each person will have different docker image to run.
This will trigger multiple Docker…