job command interpreter should be customizable
Bug #1303955 reported by
Zygmunt Krynicki
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| PlainBox (Toolkit) |
Fix Released
|
Wishlist
|
Zygmunt Krynicki | ||
Bug Description
Currently all jobs run via bash for legacy reasons but this is wasteful and unportable. Ideally each job would specify which interpreter to use (with some sane defaults?). This way we could migrate jobs, one by one, to /bin/sh
Related branches
lp://qastaging/~zyga/checkbox/fix-1303955
- Brendan Donegan (community): Approve
-
Diff: 218 lines (+42/-20)7 files modifiedplainbox/plainbox/abc.py (+8/-0)
plainbox/plainbox/impl/ctrl.py (+6/-6)
plainbox/plainbox/impl/secure/job.py (+9/-0)
plainbox/plainbox/impl/secure/launcher1.py (+2/-2)
plainbox/plainbox/impl/secure/test_job.py (+4/-0)
plainbox/plainbox/impl/secure/test_launcher1.py (+8/-7)
plainbox/plainbox/impl/test_ctrl.py (+5/-5)
| Changed in plainbox: | |
| milestone: | none → future |
| Changed in plainbox: | |
| status: | New → In Progress |
| milestone: | future → 0.6 |
| assignee: | nobody → Zygmunt Krynicki (zkrynicki) |
| importance: | Undecided → Wishlist |
| Changed in plainbox: | |
| status: | In Progress → Fix Committed |
| Changed in plainbox: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
