4
75%
master: 75%

Ran 02 Sep 2020 05:48PM UTC

Files 8

Run time 2s

Badge

Embed ▾

Committed 02 Sep 2020 05:46PM UTC coverage: 57.979%. Remained the same

Job # 379.4

Build Type

push

travis-ci-com

Committed by

mergify[bot]

Commit Message

release: document default behavior for state_machine_rule_set

This parameter behaves a little differently than other parameters when
a playbook author omits it. Document what happens when omitting it.

Other parameters do not override values when unspecified, so this
behavior is a little surprising. See default_docs_reviewer in
errata_tool_product.py for an example of a parameter that behaves in the
opposite way.

I'm preserving this behavior and documenting it instead of changing this
now. My reason is that I want to be able to set rules back to "null" on
releases. Generally speaking, it adds a lot of complexity to have
per-release rules that override per-product rules. I'm thinking we
should steer playbook authors toward simplifying their configurations
instead of making them more complex.

Maybe in the future we can revisit this decision. The web UI HTML form
has a dropdown with a string "(unset)" to represent a "null" value, and
maybe we could do that in Ansible here. That does add complexity though,
and I'm not sure if it's worth it.

Run Details

545 of 940 relevant lines covered (57.98%)

0.58 hits per line

ktdreyer / errata-tool-ansible / 379 / 4
75%
master: 75%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 379.4

ktdreyer / errata-tool-ansible / 379 / 4 75% master: 75%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 379.4

ktdreyer / errata-tool-ansible / 379 / 4
75%
master: 75%

README BADGES
x