[Feature] Self hosted builders with ephemeral build environments #35

New Issue

GiteaMirror · 2025-10-31T15:00:19-05:00

GiteaMirror commented

2025-10-31 15:00:19 -05:00

Originally created by @C0untZero on GitHub (Aug 30, 2024).

At the moment, if we designate a local server as a builder, the repo build expects the build tools to already be available.
It would be nice if there was a way to:

somehow define the needed build tools in the repo configuration itself
make the build environment ephemeral
Point 2 is there because builders can also double as deployment servers and I imagine we'd want to keep the deploy environments clean of any needed build dependencies.

This could potentially be solved by utilizing docker itself - a repo configuration could define an image where the repo would be cloned and built.
As per our Discord discussion, this could be done by Komodo building a temporary Dockerfile in the repo and filling it with the configured FROM and RUN <onclone cmd / onpull cmd>.
Alternatively it may be possible to use docker attach, where Komodo would spin up a container from the defined image, perform docker attach on it, and then execute all further commands directly there.

Originally created by @C0untZero on GitHub (Aug 30, 2024). At the moment, if we designate a local server as a builder, the repo build expects the build tools to already be available. It would be nice if there was a way to: 1. somehow define the needed build tools in the repo configuration itself 2. make the build environment ephemeral Point 2 is there because builders can also double as deployment servers and I imagine we'd want to keep the deploy environments clean of any needed build dependencies. This could potentially be solved by utilizing docker itself - a repo configuration could define an image where the repo would be cloned and built. As per our Discord discussion, this could be done by Komodo building a temporary Dockerfile in the repo and filling it with the configured FROM <image> and RUN <onclone cmd / onpull cmd>. Alternatively it may be possible to use docker attach, where Komodo would spin up a container from the defined image, perform docker attach on it, and then execute all further commands directly there.

GiteaMirror added the enhancement label 2025-10-31 15:00:19 -05:00

GiteaMirror commented

2025-10-31 15:00:19 -05:00

@FoxxMD commented on GitHub (Oct 31, 2024):

This could also be achieved, somewhat, by using act to run github action workflows. It follows the behavior you described (isolated build environment in container). Advantage being github workflows already exist and are well supported with the obv disadvantage being the workflows are not agnostic.

@FoxxMD commented on GitHub (Oct 31, 2024): This could also be achieved, somewhat, by using [act](https://nektosact.com/) to run github action workflows. It follows the behavior you described (isolated build environment in container). Advantage being github workflows already exist and are well supported with the obv disadvantage being the workflows are not agnostic.

GiteaMirror referenced this issue

2025-10-31 15:17:48 -05:00

[PR #35] [MERGED] 1.13.2 #670

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/komodo#35