Alexander Bayandin 207919f5eb Upload test results to DB right after generation (#4967) ...

## Problem

While adding new test results format, I've also changed the way we
upload Allure reports to S3
(https://github.com/neondatabase/neon/pull/4549/commits/722c7956bb932b639759f41f49aadb6115ef2179)
to avoid duplicated results from previous runs. But it broke links at
earlier results (results are still available but on different URLs).

This PR fixes this (by reverting logic in
https://github.com/neondatabase/neon/pull/4549/commits/722c7956bb932b639759f41f49aadb6115ef2179
changes), and moves the logic for storing test results into db to allure
generate step. It allows us to avoid test results duplicates in the db
and saves some time on extra s3 downloads that happened in a different
job before the PR.

Ref https://neondb.slack.com/archives/C059ZC138NR/p1691669522160229

## Summary of changes
- Move test results storing logic from a workflow to
`actions/allure-report-generate`

2023-08-15 15:32:30 +01:00

..

approved-for-ci-run.yml

Make CI more friendly for external contributors (#4663)

2023-07-15 11:58:15 +01:00

benchmarking.yml

Nightly Benchmarks: Increase timeout for pgbench-compare job (#4551)

2023-06-23 12:47:37 +01:00

build_and_test.yml

Upload test results to DB right after generation (#4967)

2023-08-15 15:32:30 +01:00

neon_extra_builds.yml

Make CI more friendly for external contributors (#4663)

2023-07-15 11:58:15 +01:00

pg_clients.yml

GitHub Workflows: use ref_name instead of ref

2023-04-12 15:22:18 +01:00

release.yml

Add tags for releases (#4524)

2023-06-16 14:17:37 +01:00