mirror of
https://github.com/plankanban/planka.git
synced 2026-02-24 19:08:59 +03:00
[PR #221] [MERGED] Github actions config for docker builds #958
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/plankanban/planka/pull/221
Author: @ThelonKarrde
Created: 4/22/2022
Status: ✅ Merged
Merged: 4/29/2022
Merged by: @meltyshev
Base:
master← Head:feature/github_actions_ci📝 Commits (8)
52f7ff7Github actions config for dockerb6167d7Add name and multi-arch buildf25362aUpdate pipeline name7d827f5Delete pvc.yaml474c18cfix archs names236bba4docker-build re-work37326e9Rename workflow filec95bf59Remove «v» from tag name, some name fixes📊 Changes
2 files changed (+43 additions, -1 deletions)
View changed files
➕
.github/workflows/build-and-push-docker-image.yml(+42 -0)📝
docker-compose.yml(+1 -1)📄 Description
To be honest, not sure if it's needed, but would like to propose a standardized way of automating building docker images.
The benefits: all in one place aka github. Unlimited storage and retention of packages for open-source projects. Easy to manage access for the owner of the code. Probably later also you can add builds of the app into a
.zipartifacts if necessary and of course automation of builds as at the moment I can't see any CI configured.Also would allow to sync docker versions with image version and helm charts in the future.
The downside: loose number of image pulls on the docker hub.
p.s. It's configured to build images at the moment only on new releases of that repo.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.