ansible-lint requires that variables for roles are prefixed with the
name of the role. This commit prefixes the variables for the
rabbit/user role with user_ as required by ansible-lint
Signed-off-by: Ryan Lerch <rlerch@redhat.com>
ansible-lint requires that variables for roles are prefixed with the
name of the role. This commit prefixes the variables for the
openshift/rollout role with rollout_ as required by ansible-lint
Signed-off-by: Ryan Lerch <rlerch@redhat.com>
ansible-lint requires that variables for roles are prefixed with the
name of the role. This commit prefixes the variables for the
openshift/route role with route_ as required by ansible-lint
Signed-off-by: Ryan Lerch <rlerch@redhat.com>
ansible-lint requires that variables for roles are prefixed with the
name of the role. This commit prefixes the variables for the
openshift/object role with object_ as required by ansible-lint
Signed-off-by: Ryan Lerch <rlerch@redhat.com>
ansible-lint requires that variables for roles are prefixed with the
name of the role. This commit prefixes the rvariables for the
openshift/project role with project_ as required by ansible-lint
Signed-off-by: Ryan Lerch <rlerch@redhat.com>
It's renamed to kiwi_build, but we can't gate on the new name
yet as not all updates will have it. We'll have to wait for a
while.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
It looks like these #jinja2 comments don't work with a space
between the # and the jinja2, or something. I'm getting errors
on this template when trying to run an openshift playbook ATM.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
It's named differently now (kiwi_build, not live_build). We don't
really need the build test in the gating config anyway as the
other two tests depend on it. We could add kiwi_build back in a
few months if we really want to, though.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This uses the release number templates for the product_versions
blocks in the gating config, instead of hardcoding them. I tried
to include some flexibility so we can easily manually flip gating
on or off for Rawhide or Branched - for specific rules, or the
whole file - around branch time, if we need to (sometimes we do,
as we can get in catch-22 situations and stuff during branching).
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Otherwise we risk a conflict with other automatically allocated users,
right now it is:
fatal: [copr-keygen-dev.aws.fedoraproject.org]: FAILED! => {"changed": false, "msg": "useradd: UID 992 is not unique\n", "name": "copr-signer", "rc": 4}
