Container environments for Forgejo Actions
https://git.frostfs.info/TrueCloudLab/-/packages/container/env/versions
All checks were successful
/ build-dotnet-8.0 (pull_request) Successful in 58s
/ build-openjdk-11-maven-3.8.6 (pull_request) Successful in 3m39s
/ build-python-3.11 (pull_request) Successful in 49s
/ build-python-3.13 (pull_request) Successful in 3m36s
/ build-dotnet-8.0 (push) Successful in 1m39s
/ build-openjdk-11-maven-3.8.6 (push) Successful in 52s
/ build-python-3.11 (push) Successful in 1m45s
/ build-python-3.13 (push) Successful in 57s
Signed-off-by: Vitaliy Potyarkin <v.potyarkin@yadro.com> |
||
---|---|---|
.forgejo/workflows | ||
dotnet-8.0 | ||
openjdk-11-maven-3.8.6 | ||
python-3.11 | ||
python-3.13 | ||
CODEOWNERS | ||
Makefile | ||
README.md |
Container environments for Forgejo Actions
Many actions developers are targeting GitHub Actions and assume that Node.js is available by default. This is not the case in Forgejo Actions, and we need to add Node.js to community provided images explicitly.
This repo contains Dockerfile for images used by TrueCloudLab.
Images are published to our registry
Modifying container images
Prepare a pull request with a modified or entirely new Dockerfile. The image will get built and published after PR is merged to master.
Requirements
Images for Forgejo Actions must contain:
- Node.js
- Git