Custom output directory of MashDirective
ClosedPublic

Authored by lbrabec on Jun 26 2014, 10:22 AM.

Details

Summary

Method do_mash() of MashDirective now accepts outdir as its argument -- path to directory where repo is created, if not specified rpmdir is used as before.

Test Plan

$ py.test -F (with the new tests)

Diff Detail

Repository
rLTRN libtaskotron
Branch
feature/T162
Lint
No Linters Available
Unit
No Unit Test Coverage
lbrabec retitled this revision from to Custom output direcotry of MashDirective.Jun 26 2014, 10:22 AM
lbrabec updated this object.
lbrabec edited the test plan for this revision. (Show Details)
lbrabec added a reviewer: mkrizek.
lbrabec retitled this revision from Custom output direcotry of MashDirective to Custom output directory of MashDirective.Jun 26 2014, 11:33 AM
jskladan requested changes to this revision.Jun 26 2014, 12:45 PM

Other than the comments, it looks OK. I'd try to clean-up after the tests, but I'm not sure whether it is really necessary.

libtaskotron/directives/mash_directive.py
83

Please change the logic here, so the rpm files are not copied, but create symlinks instead. We already strive with disk space on the test slaves, so having two copies of the same files does not really make sense. I'm not sure, though, whether mash will work on just symlinks.

96

It might make more sense to return the "actuall" outdir ( (rpmdir if not outdir else outdir) ) here. And also then return it as a result of the process() method.

111

I know that dict.get() returns None on non-existing key, but I'd rather have it explicit: outdir = input_data.get('outdir', None)

This revision now requires changes to proceed.Jun 26 2014, 12:45 PM
lbrabec updated this revision to Diff 477.Jun 26 2014, 1:00 PM
  • custom output directory of mash directive (polished)
This revision is now accepted and ready to land.Jun 26 2014, 1:25 PM
lbrabec closed this revision.Jun 27 2014, 8:44 AM

Closed by commit 65b8128 (authored by @lbrabec).