Alexander Bayandin 1d5e476c96 CI: use build-tools image from dockerhub (#6795) ...

## Problem

Currently, after updating `Dockerfile.build-tools` in a PR, it requires
a manual action to make it `pinned`, i.e., the default for everyone. It
also makes all opened PRs use such images (even created in the PR and
without such changes).
This PR overhauls the way we build and use `build-tools` image (and uses
the image from Docker Hub).

## Summary of changes
- The `neondatabase/build-tools` image gets tagged with the latest
commit sha for the `Dockerfile.build-tools` file
- Each PR calculates the tag for `neondatabase/build-tools`, tries to
pull it, and rebuilds the image with such tag if it doesn't exist.
- Use `neondatabase/build-tools` as a default image
- When running on `main` branch — create a `pinned` tag and push it to
ECR
- Use `concurrency` to ensure we don't build `build-tools` image for the
same commit in parallel from different PRs

2024-02-28 12:38:11 +00:00

..

actions

CI(release-proxy): fix a couple missed release-proxy branch handling (#6892)

2024-02-23 14:12:09 +00:00

ISSUE_TEMPLATE

Update epic-template.md (#5709)

2023-11-09 15:24:43 +01:00

PULL_REQUEST_TEMPLATE

Migrate links from wiki to notion (#5862)

2023-11-14 15:36:47 +00:00

workflows

CI: use build-tools image from dockerhub (#6795)

2024-02-28 12:38:11 +00:00

actionlint.yml

check-macos-build: switch job to macos-14 (M1) (#6539)

2024-02-02 10:51:20 +00:00

pull_request_template.md

Simplify github PR template (#4241)

2023-05-16 08:13:54 -04:00