Skip to content

Add scenarios

Add scenarios #57

Triggered via pull request August 12, 2024 08:45
@rpelisserpelisse
synchronize #8
add_scenarios
Status Success
Total duration 2m 51s
Artifacts

ci.yml

on: pull_request
Matrix: ci / linter
Matrix: ci / molecule
Matrix: ci / sanity
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
schema[meta]: roles/quarkus/meta/main.yml#L1
$.galaxy_info.platforms[0].versions[0] 8 is not one of ['6.1', '7.1', '7.2', 'all']. See https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_reuse_roles.html#using-role-dependencies
name[template]: roles/quarkus/tasks/build.yml#L13
Jinja templates should only be at the end of 'name'
name[template]: roles/quarkus/tasks/build.yml#L46
Jinja templates should only be at the end of 'name'
key-order[task]: roles/quarkus/tasks/deploy/firewalld.yml#L2
You can improve the task key order to: become, block
name[missing]: roles/quarkus/tasks/deploy/firewalld.yml#L2
All tasks should be named.
name[template]: roles/quarkus/tasks/deploy/firewalld.yml#L8
Jinja templates should only be at the end of 'name'
name[template]: roles/quarkus/tasks/java.yml#L2
Jinja templates should only be at the end of 'name'
name[template]: roles/quarkus/tasks/java.yml#L11
Jinja templates should only be at the end of 'name'
name[template]: roles/quarkus/tasks/mvn.yml#L35
Jinja templates should only be at the end of 'name'
name[template]: roles/quarkus/tasks/path_exists.yml#L14
Jinja templates should only be at the end of 'name'