Merge lp:~ricardokirkner/ols-jenkaas/land-approvals-without-container into lp:~ols-jenkaas-admins/ols-jenkaas/trunk
Proposed by
Ricardo Kirkner
Status: | Merged |
---|---|
Approved by: | Ricardo Kirkner |
Approved revision: | 517 |
Merged at revision: | 515 |
Proposed branch: | lp:~ricardokirkner/ols-jenkaas/land-approvals-without-container |
Merge into: | lp:~ols-jenkaas-admins/ols-jenkaas/trunk |
Diff against target: |
178 lines (+98/-19) 4 files modified
README.rst (+3/-1) olsjenkaas/commands.py (+35/-16) olsjenkaas/containers.py (+2/-2) olsjenkaas/tests/test_commands.py (+58/-0) |
To merge this branch: | bzr merge lp:~ricardokirkner/ols-jenkaas/land-approvals-without-container |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Daniel Manrique (community) | Approve | ||
Review via email: mp+330681@code.launchpad.net |
Commit message
support landing approved proposals by running landing tests in host (for docker projects)
if no container is specified, the land approval command will run the command in the host itself
To post a comment you must log in.
Looks OK in principle/spirit. I'm a bit scared about running stuff not-in-a-container, though launching a docker image should be somewhat equivalent.
See a comment below, and also, could you document this magic behavior somewhere?
Example, the README says
All test jobs occur inside an lxd container, only the push to launchpad
occur on the slaves themselves so that the needed credentials are never
exposed to test jobs.
this is potentially no longer accurate.