Skip to content

Merge pull request #863 from arkid15r/code-base-refactoring #29

Merge pull request #863 from arkid15r/code-base-refactoring

Merge pull request #863 from arkid15r/code-base-refactoring #29

Triggered via push August 24, 2024 21:33
Status Failure
Total duration 8m 9s
Artifacts 1

ci_cd.yml

on: push
Run pytest
17s
Run pytest
Test Docker image
6m 55s
Test Docker image
Build package
20s
Build package
Publish Docker image
56s
Publish Docker image
Publish to Test PyPI
25s
Publish to Test PyPI
Publish to PyPI
22s
Publish to PyPI
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 5 warnings
Publish to PyPI
Trusted publishing exchange failure: Token request failed: the server refused the request for the following reasons: * `invalid-publisher`: valid token, but no corresponding publisher (All lookup strategies exhausted) This generally indicates a trusted publisher configuration error, but could also indicate an internal error on GitHub or PyPI's part. The claims rendered below are **for debugging purposes only**. You should **not** use them to configure a trusted publisher unless they already match your expectations. If a claim is not present in the claim set, then it is rendered as `MISSING`. * `sub`: `repo:OWASP/Nettacker:ref:refs/heads/master` * `repository`: `OWASP/Nettacker` * `repository_owner`: `OWASP` * `repository_owner_id`: `155815` * `job_workflow_ref`: `OWASP/Nettacker/.github/workflows/ci_cd.yml@refs/heads/master` * `ref`: `refs/heads/master` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
Publish to Test PyPI
Trusted publishing exchange failure: Token request failed: the server refused the request for the following reasons: * `invalid-publisher`: valid token, but no corresponding publisher (All lookup strategies exhausted) This generally indicates a trusted publisher configuration error, but could also indicate an internal error on GitHub or PyPI's part. The claims rendered below are **for debugging purposes only**. You should **not** use them to configure a trusted publisher unless they already match your expectations. If a claim is not present in the claim set, then it is rendered as `MISSING`. * `sub`: `repo:OWASP/Nettacker:ref:refs/heads/master` * `repository`: `OWASP/Nettacker` * `repository_owner`: `OWASP` * `repository_owner_id`: `155815` * `job_workflow_ref`: `OWASP/Nettacker/.github/workflows/ci_cd.yml@refs/heads/master` * `ref`: `refs/heads/master` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
Run pytest
The following actions use a deprecated Node.js version and will be forced to run on node20: 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/
Build package
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Publish to PyPI
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/download-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Publish to Test PyPI
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/download-artifact@v3. 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: "dist". 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
dist
6.97 MB