[PR #221] [MERGED] Github actions config for docker builds #958

Closed
opened 2026-02-04 21:40:49 +03:00 by OVERLORD · 0 comments
Owner

📋 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: masterHead: feature/github_actions_ci


📝 Commits (8)

📊 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 .zip artifacts 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.

## 📋 Pull Request Information **Original PR:** https://github.com/plankanban/planka/pull/221 **Author:** [@ThelonKarrde](https://github.com/ThelonKarrde) **Created:** 4/22/2022 **Status:** ✅ Merged **Merged:** 4/29/2022 **Merged by:** [@meltyshev](https://github.com/meltyshev) **Base:** `master` ← **Head:** `feature/github_actions_ci` --- ### 📝 Commits (8) - [`52f7ff7`](https://github.com/plankanban/planka/commit/52f7ff7a1b8f306c3c3eae02bd240c7c42e1293b) Github actions config for docker - [`b6167d7`](https://github.com/plankanban/planka/commit/b6167d7f99dd0a101c425315e725439cb51aaca4) Add name and multi-arch build - [`f25362a`](https://github.com/plankanban/planka/commit/f25362ab70f5979f4751106d545c6ae4a105bc10) Update pipeline name - [`7d827f5`](https://github.com/plankanban/planka/commit/7d827f560ad55320aec4192fd3473a85790bc084) Delete pvc.yaml - [`474c18c`](https://github.com/plankanban/planka/commit/474c18c515152e3698ef1f4137db46c970889640) fix archs names - [`236bba4`](https://github.com/plankanban/planka/commit/236bba4842b9a321d7ab46bee17fe4a77e528960) docker-build re-work - [`37326e9`](https://github.com/plankanban/planka/commit/37326e989ed110bdd55d26eadf5a3baf85651d35) Rename workflow file - [`c95bf59`](https://github.com/plankanban/planka/commit/c95bf59b9b9200f80c18fa611175750abe2e7936) Remove «v» from tag name, some name fixes ### 📊 Changes **2 files changed** (+43 additions, -1 deletions) <details> <summary>View changed files</summary> ➕ `.github/workflows/build-and-push-docker-image.yml` (+42 -0) 📝 `docker-compose.yml` (+1 -1) </details> ### 📄 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 `.zip` artifacts 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. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
OVERLORD added the pull-request label 2026-02-04 21:40:49 +03:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/planka#958