Overhaul Galaxy job config handling.#1506
Conversation
jmchilton
commented
Mar 26, 2025
- More options from the command-line - multiple runners, TPV shared database, singularity, etc...
- Switch from job conf via XML to job conf via YAML.
- Bring in dependency on galaxy-job-config-init to handle a lot of that logic.
- Commands to assign binding a job config to a created Planemo profile.
- More options from the command-line - multiple runners, TPV shared database, singularity, etc... - Switch from job conf via XML to job conf via YAML. - Bring in dependency on galaxy-job-config-init to handle a lot of that logic. - Commands to assign binding a job config to a created Planemo profile.
|
Could we also default to |
@mvdbeek you want to resulting job_config to look like this by default? ...
execution:
...
environments:
local:
runner: local
tmp_dir: true
... |
|
yes |
I have made a pull-request against galaxy-job-config-init that will add tmp_dir option (#1). Will update the code here when the updates are merged. |
|
It would be great if someone could upload a new release of galaxy-job-config-init to PyPI. After that, we could look into merging, which would enable me to start updating my instructions for running Planemo with a SLURM cluster |
|
@jmchilton just published a new release |
|
@mvdbeek could we trigger the test again? I guess we should be able to merge this pull-request now when @jmchilton has published a new version of galaxy-job-config-init? |