Add support for standalone reporting command

[veruu]

Test with commands like sktm -vv --mail-from me --mail-to someone report --assets dir-with-results

where dir-with-results is a directory containing stage results (which are not yet implemented in skt, so you'll need to create your own ones for testing purposes).
Examples of content:
build.log build.report build.result merge.report merge.result
or applied.patch merge.report merge.result s390/ x86/ where s390/ contains build.report build.result config.gz kitty and x86/ contains build.report build.result useless-file

From the examples, useless-file is not referenced in the report text so it's not added, config.gz, applied.patch and kitty are referenced and added as attachments.

I'll add a proper directory structure definition to meta/pull6 so it's less confusing but I wanted to publish the code here before the weekend.

[coveralls]

Pull Request Test Coverage Report for Build 390

• 129 of 175 (73.71%) changed or added relevant lines in 2 files are covered.
• 3 unchanged lines in 1 file lost coverage.
• Overall coverage increased (+8.9%) to 37.976%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
sktm/reporter.py	125	143	87.41%
sktm/executable.py	4	32	12.5%

Files with Coverage Reduction	New Missed Lines	%
sktm/executable.py	3	16.24%

Totals
Change from base Build 382:	8.9%
Covered Lines:	463
Relevant Lines:	1095

---

💛 - Coveralls

[veruu]

This is more or less ready to review.

[dzickusrh]

I think this seems fine in general as it is opt-in and won't cause issues with current pipeline.
I just had some concerns about input. Everything else seems straightforward.

[dzickusrh]

Who sanitizes the input? If I type --header foo --header bar:blah, I think things will go bad? Or is the input files verified?
Not that many non-scripts will touch those cli options, but in case things get fat fingered..

[veruu]

This logic is taken from skt (but can be changed if needed). Missing space as in your second example is not a problem, only missing : is (as per your first example). The format is described in the help string if someone wants to use the command manually. IMHO, things should "go bad" if you pass invalid option. The error thrown should show the line which tries to split the header so it should be obvious what is the problem but if you would feel more comfortable with it, I can add a custom error message saying that the header passed doesn't conform to the required format.

[dzickusrh]

Ok. If this is more-or-less a copy-n-paste of skt, then it is probably fine. Eventually, it would be nice to have some checking going on to avoid silly bugs. I wonder if a simple 'if not value: raise Exception()' works here.

[veruu]

Not really, since the assignment itself will throw the exception. But I added a custom message to it, please check if that's what you meant

[dzickusrh]

Yeah. thanks.

[dzickusrh]

Seems fine to me.

[dzickusrh]

Yeah. thanks.