Build and publish dev Docker distributions to Github Container Registry ghcr.io

[TH2-5211] Implemented /download/events REST API call #460

Sign in to view logs

Triggered via push October 31, 2024 07:09

Nikita-Smirnov-Exactpro

TH2-5211-download-events

Status Failure

Total duration 8m 23s

Artifacts 1

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 gRPC distributions / Build Gradle module grpc

Build and publish lw-data-provider-utils / Build Gradle module utils

owasp-scan / owasp-scan-job

Build docker image / docker-push

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

Scan Docker image for vulnerabilities / trivy-scan-job

Annotations

2 errors and 6 warnings

Scan Docker image for vulnerabilities / trivy-scan-job

Process completed with exit code 1.

owasp-scan / owasp-scan-job

Process completed with exit code 1.

Build and publish Java gRPC distributions / Build Gradle module grpc

Could not find any files for grpc/build/test-results/**/*.xml, grpc/build/test-results/**/*.trx, grpc/build/test-results/**/*.json

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/

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

The following actions use a deprecated Node.js version and will be forced to run on node20: MerthinTechnologies/edit-json-action@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

attestations input ignored

The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.

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

Create a Trusted Publisher

A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):

Artifacts

Produced during runtime

Name	Size
th2-net~th2-lw-data-provider~TGZLRD.dockerbuild	23.6 KB