Skip to content

Pin python and ansible-lint versions #2626

Pin python and ansible-lint versions

Pin python and ansible-lint versions #2626

Triggered via push February 13, 2025 14:28
Status Success
Total duration 1m 11s
Artifacts

main.yml

on: push
Operator Linting
52s
Operator Linting
stf-run-ci Linting
52s
stf-run-ci Linting
Check if generating the bundle would result in local changes
7s
Check if generating the bundle would result in local changes
Build Operator check
44s
Build Operator check
Build bundle check
45s
Build bundle check
Validate the generated bundle and perform scorecard checks
1m 1s
Validate the generated bundle and perform scorecard checks
Fit to window
Zoom out
Zoom in

Annotations

20 warnings
yaml[new-line-at-end-of-file]: build/stf-run-ci/handlers/main.yml#L2
No new line character at the end of file
name[template]: build/stf-run-ci/tasks/clone_repos.yml#L7
Jinja templates should only be at the end of 'name'
name[template]: build/stf-run-ci/tasks/clone_repos.yml#L21
Jinja templates should only be at the end of 'name'
name[template]: build/stf-run-ci/tasks/clone_repos.yml#L27
Jinja templates should only be at the end of 'name'
name[template]: build/stf-run-ci/tasks/clone_repos.yml#L41
Jinja templates should only be at the end of 'name'
name[template]: build/stf-run-ci/tasks/clone_repos.yml#L47
Jinja templates should only be at the end of 'name'
name[template]: build/stf-run-ci/tasks/clone_repos.yml#L61
Jinja templates should only be at the end of 'name'
name[template]: build/stf-run-ci/tasks/clone_repos.yml#L67
Jinja templates should only be at the end of 'name'
name[template]: build/stf-run-ci/tasks/clone_repos.yml#L81
Jinja templates should only be at the end of 'name'
yaml[empty-lines]: build/stf-run-ci/tasks/clone_repos.yml#L86
Too many blank lines (1 > 0)
var-naming[no-role-prefix]: roles/servicetelemetry/defaults/main.yml#L5
Variables names from within roles should use servicetelemetry_ as a prefix. (vars: clouds_remove_on_missing)
var-naming[no-role-prefix]: roles/servicetelemetry/defaults/main.yml#L6
Variables names from within roles should use servicetelemetry_ as a prefix. (vars: observability_strategy)
var-naming[no-role-prefix]: roles/servicetelemetry/defaults/main.yml#L9
Variables names from within roles should use servicetelemetry_ as a prefix. (vars: prometheus_operator_api_string)
var-naming[no-role-prefix]: roles/servicetelemetry/defaults/main.yml#L10
Variables names from within roles should use servicetelemetry_ as a prefix. (vars: prometheus_operator_label)
var-naming[no-role-prefix]: roles/servicetelemetry/defaults/main.yml#L143
Variables names from within roles should use servicetelemetry_ as a prefix. (vars: is_k8s)
var-naming[no-role-prefix]: roles/servicetelemetry/defaults/main.yml#L144
Variables names from within roles should use servicetelemetry_ as a prefix. (vars: is_openshift)
var-naming[no-role-prefix]: roles/servicetelemetry/defaults/main.yml#L146
Variables names from within roles should use servicetelemetry_ as a prefix. (vars: _ephemeral_storage_enabled)
var-naming[no-role-prefix]: roles/servicetelemetry/defaults/main.yml#L149
Variables names from within roles should use servicetelemetry_ as a prefix. (vars: smartgateway_deployment_size)
schema[meta]: roles/servicetelemetry/meta/main.yml#L1
$.galaxy_info.min_ansible_version 2.9 is not of type 'string'. See https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_reuse_roles.html#using-role-dependencies
fqcn[action-core]: roles/servicetelemetry/tasks/base_smartgateway.yml#L1
Use FQCN for builtin module actions (set_fact).