Build and publish dev build for read db project

python version naming fix #87

Sign in to view logs

Re-run triggered September 11, 2023 08:22

lumber1000

TH2-4953

Status Failure

Total duration 1m 26s

Artifacts –

dev-build.yml

on: push

Collect app version / Pre-build steps for project app

Collect grpc version / Pre-build steps for project grpc

Build and publish Java core distributions / Build Gradle module core

Build and publish Java gRPC distributions / Build Gradle module grpc

Build docker image / docker-push

Build and publish Python distributions to PyPI / Build and publish Python distributions to PyPI

owasp-scan / owasp-scan-job

Scan Docker image for vulnerabilities / trivy-scan-job

Annotations

2 errors, 2 warnings, and 1 notice

Build docker image / docker-push

Process completed with exit code 1.

Build and publish Java core distributions / Build Gradle module core

Process completed with exit code 1.

Build and publish Python distributions to PyPI / Build and publish Python distributions to PyPI

The following actions uses node12 which is deprecated and will be forced to run on node16: MerthinTechnologies/edit-json-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Upgrade to Trusted Publishing

Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers

Build and publish Python distributions to PyPI / Build and publish Python distributions to PyPI

Using a user-provided API token for authentication against https://upload.pypi.org/legacy/