woodpecker/pipeline/rpc/proto
Anbraten d494b6a959
Use forge from db (#1417)
This is the first step towards support for multiple forges (#138). It
inserts a forge using the currently existing env varaibles into db and
uses this forge from db later on in all places of the code.

closes #621

addresses #138 

# TODO
- [x] add forges table
- [x] add id of forge to repo
- [x] use forge of repo
- [x] add forge from env vars to db if not exists
- [x] migrate repo.ForgeID to the newly generated forge
- [x] support cache with forge from repo
- [x] maybe add forge loading cache? (use LRU cache for forges, I expect
users to have less than 10 forges normally)

---------

Co-authored-by: qwerty287 <80460567+qwerty287@users.noreply.github.com>
2024-04-16 08:04:55 +02:00
..
generate.go Fix make in_docker generate (#3616) 2024-04-15 17:46:44 +02:00
version.go Use step uuid instead of name in GRPC status calls (#3143) 2024-01-09 15:39:09 +01:00
woodpecker.pb.go Fix make in_docker generate (#3616) 2024-04-15 17:46:44 +02:00
woodpecker.proto Use step uuid instead of name in GRPC status calls (#3143) 2024-01-09 15:39:09 +01:00
woodpecker_grpc.pb.go Use forge from db (#1417) 2024-04-16 08:04:55 +02:00