CI: Update pre-commit versions #1173
sugetha24pull-request-management.yml
on: pull_request
file-changes
4s
Validate mkdoc links
44s
Run ansible-lint test case
1m 5s
Matrix: Validate code V1 with Molecule
Matrix: Validate Roles for DHCP management
Matrix: Validate code compatibility
Matrix: Validate code V3 with Pytest
Matrix: Run ansible-test validation
Annotations
15 errors and 37 warnings
|
var-naming[pattern]:
tmp/tmp572eh24e_cv_device_v3.py.yaml#L8
Variables names should match ^\[a-z_]\[a-z0-9_]*$ regex. (CVP_DEVICES)
|
|
var-naming[pattern]:
tmp/tmp572eh24e_cv_device_v3.py.yaml#L27
Variables names should match ^\[a-z_]\[a-z0-9_]*$ regex. (CVP_DEVICES)
|
|
var-naming[pattern]:
tmp/tmp572eh24e_cv_device_v3.py.yaml#L48
Variables names should match ^\[a-z_]\[a-z0-9_]*$ regex. (CVP_DEVICES)
|
|
var-naming[pattern]:
tmp/tmp572eh24e_cv_device_v3.py.yaml#L66
Variables names should match ^\[a-z_]\[a-z0-9_]*$ regex. (CVP_DEVICES)
|
|
var-naming[pattern]:
tmp/tmp572eh24e_cv_device_v3.py.yaml#L84
Variables names should match ^\[a-z_]\[a-z0-9_]*$ regex. (CVP_DEVICES)
|
|
var-naming[pattern]:
tmp/tmp572eh24e_cv_device_v3.py.yaml#L100
Variables names should match ^\[a-z_]\[a-z0-9_]*$ regex. (CVP_DEVICES)
|
|
var-naming[pattern]:
tmp/tmp572eh24e_cv_device_v3.py.yaml#L115
Variables names should match ^\[a-z_]\[a-z0-9_]*$ regex. (CVP_DEVICES)
|
|
var-naming[pattern]:
tmp/tmp_rfk7_4k_cv_validate_v3.py.yaml#L8
Variables names should match ^\[a-z_]\[a-z0-9_]*$ regex. (CVP_DEVICES)
|
|
var-naming[pattern]:
tmp/tmp_rfk7_4k_cv_validate_v3.py.yaml#L27
Variables names should match ^\[a-z_]\[a-z0-9_]*$ regex. (CVP_DEVICES)
|
|
var-naming[pattern]:
tmp/tmpkp0gz7at_cv_container.py.yaml#L23
Variables names should match ^\[a-z_]\[a-z0-9_]*$ regex. (CVP_CONTAINERS_RESULT) (register: CVP_CONTAINERS_RESULT)
|
|
Validate code V3 with Pytest (3.9)
Process completed with exit code 2.
|
|
Validate code V3 with Pytest (3.10)
The job was canceled because "_3_9" failed.
|
|
Validate code V3 with Pytest (3.10)
Process completed with exit code 2.
|
|
Validate code V3 with Pytest (3.11)
The job was canceled because "_3_9" failed.
|
|
Validate code V3 with Pytest (3.11)
Process completed with exit code 2.
|
|
file-changes
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, dorny/paths-filter@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Validate mkdoc links
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Run pre-commit validation hooks
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
jinja[spacing]:
examples/cv_change_control_v3/change_control_v3_create_remove.yml#L21
Jinja2 spacing could be improved: Create a change control on {{inventory_hostname}} -> Create a change control on {{ inventory_hostname }}
|
|
jinja[spacing]:
examples/cv_change_control_v3/change_control_v3_create_remove.yml#L27
Jinja2 spacing could be improved: Show a change control on {{inventory_hostname}} using change_id field -> Show a change control on {{ inventory_hostname }} using change_id field
|
|
jinja[spacing]:
examples/cv_change_control_v3/change_control_v3_create_remove.yml#L33
Jinja2 spacing could be improved: Remove a change control on {{inventory_hostname}} using change_id field -> Remove a change control on {{ inventory_hostname }} using change_id field
|
|
jinja[spacing]:
examples/cv_change_control_v3/change_control_v3_create_schedule.yml#L21
Jinja2 spacing could be improved: Create a change control on {{inventory_hostname}} -> Create a change control on {{ inventory_hostname }}
|
|
jinja[spacing]:
examples/cv_change_control_v3/change_control_v3_create_schedule.yml#L27
Jinja2 spacing could be improved: Schedule a change control on {{inventory_hostname}} using change_id field -> Schedule a change control on {{ inventory_hostname }} using change_id field
|
|
jinja[spacing]:
examples/cv_change_control_v3/change_control_v3_create_schedule_and_approve.yml#L37
Jinja2 spacing could be improved: Create a change control on {{inventory_hostname}} -> Create a change control on {{ inventory_hostname }}
|
|
jinja[spacing]:
examples/cv_change_control_v3/change_control_v3_create_schedule_and_approve.yml#L43
Jinja2 spacing could be improved: Schedule and Approve a change control on {{inventory_hostname}} using change_id field -> Schedule and Approve a change control on {{ inventory_hostname }} using change_id field
|
|
jinja[spacing]:
examples/cv_change_control_v3/change_control_v3_create_schedule_approve.yml#L21
Jinja2 spacing could be improved: Create a change control on {{inventory_hostname}} -> Create a change control on {{ inventory_hostname }}
|
|
jinja[spacing]:
examples/cv_change_control_v3/change_control_v3_create_schedule_approve.yml#L27
Jinja2 spacing could be improved: Schedule a change control on {{inventory_hostname}} using change_id field -> Schedule a change control on {{ inventory_hostname }} using change_id field
|
|
jinja[spacing]:
examples/cv_change_control_v3/change_control_v3_create_schedule_approve.yml#L33
Jinja2 spacing could be improved: Approve a change control on {{inventory_hostname}} using change_id field -> Approve a change control on {{ inventory_hostname }} using change_id field
|
|
Validate code compatibility (3.11)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Validate code compatibility (3.9)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Validate code compatibility (3.10)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Validate code V1 with Molecule (ansible-core==2.11.3, cv_device)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/upload-artifact@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Validate code V1 with Molecule (ansible-core==2.11.3, cv_device)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/upload-artifact@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Validate code V1 with Molecule (ansible-core>=2.11.3, cv_device)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/upload-artifact@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Validate code V1 with Molecule (ansible-core>=2.11.3, cv_device)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/upload-artifact@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Validate code V1 with Molecule (ansible-core==2.11.3, cv_configlet_loose)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/upload-artifact@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Validate code V1 with Molecule (ansible-core==2.11.3, cv_configlet_loose)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/upload-artifact@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Validate code V1 with Molecule (ansible-core>=2.11.3, cv_configlet_loose)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/upload-artifact@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Validate code V1 with Molecule (ansible-core>=2.11.3, cv_configlet_loose)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/upload-artifact@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Validate Roles for DHCP management (ansible-core==2.11.3, dhcp_management_offline)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Validate Roles for DHCP management (ansible-core==2.11.3, dhcp_management_mac)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Validate Roles for DHCP management (ansible-core>=2.11.3, dhcp_system_mac)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Validate Roles for DHCP management (ansible-core>=2.11.3, dhcp_management_mac)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Validate code V1 with Molecule (ansible-core>=2.11.3, cv_configlet_strict)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/upload-artifact@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Validate code V1 with Molecule (ansible-core>=2.11.3, cv_configlet_strict)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/upload-artifact@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Validate code V1 with Molecule (ansible-core==2.11.3, cv_configlet_strict)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/upload-artifact@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Validate code V1 with Molecule (ansible-core==2.11.3, cv_configlet_strict)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/upload-artifact@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Validate Roles for DHCP management (ansible-core>=2.11.3, dhcp_management_offline)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Validate Roles for DHCP management (ansible-core==2.11.3, dhcp_system_mac)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Validate code V3 with Pytest (3.9)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Run ansible-test validation (3.9)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "molecule-cv_configlet_loose-artifacts", "molecule-cv_configlet_strict-artifacts", "molecule-cv_device-artifacts".
Please update your workflow to use v4 of the artifact actions.
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
molecule-cv_configlet_loose-artifacts
Expired
|
119 KB |
|
|
molecule-cv_configlet_strict-artifacts
Expired
|
120 KB |
|
|
molecule-cv_device-artifacts
Expired
|
120 KB |
|