Unify envr/nevr terminology and handling
ClosedPublic

Authored by mkrizek on May 29 2014, 11:44 AM.

Details

Summary

Fixes T179

Test Plan

Run:

"python runtask.py -i 1:xchat-2.8.8-21.fc20 -t koji_build -a x86_64 task-rpmlint/rpmlint.yml"

and

"python runtask.py -i xchat-1:2.8.8-21.fc20 -t koji_build -a x86_64 task-rpmlint/rpmlint.yml"

Diff Detail

Repository
rLTRN libtaskotron
Lint
Lint Skipped
Unit
Unit Tests Skipped
mkrizek retitled this revision from to Unify envr/nevr terminology and handling.May 29 2014, 11:44 AM
mkrizek updated this object.
mkrizek edited the test plan for this revision. (Show Details)
mkrizek added reviewers: tflink, kparal.
kparal accepted this revision.May 29 2014, 12:30 PM

Seems OK, beside that little terminology point. Shouldn't hopefully break anything.

readme.rst
88

I think you should just say NEVR instead of NEVR(A) here, because the architecture is in the <arch> argument. We only accept -i NVR/NEVR with -t koji_build. Therefore:

To run that task against a koji build with NEVR <nevr> for some arch <arch>

This revision is now accepted and ready to land.May 29 2014, 12:30 PM
tflink added inline comments.May 29 2014, 12:48 PM
docs/source/taskyaml.rst
203

shouldn't this be NEVR as well or are we using the (A) to indicate that the arch can be specified in the koji directive?

mkrizek updated this revision to Diff 322.May 29 2014, 12:52 PM

Fix terminology issue

mkrizek updated this revision to Diff 323.May 29 2014, 1:01 PM

Fix another terminology issue

tflink accepted this revision.May 29 2014, 1:01 PM

Looks good to me

mkrizek closed this revision.May 29 2014, 1:24 PM
mkrizek updated this revision to Diff 324.

Closed by commit rLTRNbee3cf15d98c (authored by @mkrizek).

kparal added inline comments.May 29 2014, 2:03 PM
docs/source/taskyaml.rst
203

Yeah, that's what I understood it implied - that the architecture can be specified in the directive. Not that important, though. Already pushed.