neon/.github/workflows at 325f3784f9fe46b5152000ba50ae4a01c9fd68a4 - neon

rust/neon

mirror of https://github.com/neondatabase/neon.git synced 2026-08-23 06:28:23 +00:00

Files

T

Alexander Bayandin 325f3784f9 CI(promote-images): simplify & fix the job (#7826 )

## Problem

Currently, `latest` tag is added to the images in several cases: 
```
github.ref_name == 'main' || github.ref_name == 'release' || github.ref_name == 'release-proxy'
```

This leads to a race; the `latest` tag jumps back and forth depending on
the branch that has built images.

## Summary of changes
- Do not push `latest` images to prod ECR (we don't use it)
- Use `docker buildx imagetools` instead of `crane` for tagging images
- Unify `vm-compute-node-image` job with others and use dockerhub as a
first source for images (sync images with ECR)
- Tag images with `latest` only for commits in `main`

2024-05-22 15:02:20 +00:00

actionlint.yml

CI: run check-permissions before all jobs (#6794 )

2024-02-21 20:32:12 +01:00

approved-for-ci-run.yml

CI(build-build-tools-image): Do not cancel concurrent workflows (#7226 )

2024-04-11 15:23:08 +01:00

benchmarking.yml

CI(benchmarking): Add Sharded Tenant for pgbench (#7186 )

2024-04-02 14:39:24 +01:00

build_and_test.yml

CI(promote-images): simplify & fix the job (#7826 )