bigaston.me
A set of Docker Container usefull to automate build of Godot games with Woodpecker CI.
Basic documentation
+29
+9
LICENSE
+9
LICENSE
···
1
+
MIT License
2
+
3
+
Copyright (c) 2025 Bigaston
4
+
5
+
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
6
+
7
+
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
8
+
9
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+20
README.md
+20
README.md
···
1
+
# GodotCI
2
+
3
+
A set of Docker Container usefull to automate build of Godot games with Woodpecker CI.
4
+
I think it can be usefull for a lot of people so I publish them here. If you find these Docker usefull, feel free to ping me on [BlueSky](https://bsky.app/profile/bigaston.me), [check my website](https://bigaston.me) or [support me on Ko-Fi](https://ko-fi.com/bigaston).
5
+
6
+
## What is CI/CD?
7
+
CI and CD respectively mean Continuous Integration and Continuous Deployment. It's a way to execute a set of actions everytime an action occures. Like every day at 10AM, at every commit on main branch, on each tags... It's used in a lot of big game studio to create games build, execute tests, deploy server... It's removing all the pain of building the game and discover that you can't because reason. And combined with [Itch.io butler](https://itch.io/docs/butler/) and [Steam Cmd](https://developer.valvesoftware.com/wiki/SteamCMD) you can even push your game on Steam and Itch.io.
8
+
9
+
This set of container is aimed to be used with [Woodpecker CI](https://woodpecker-ci.org/), a lightway CI system that's work with Docker. You may have some basic Docker Container where you execute a list of commands, or a Docker that run a custom binarie and do a specific task (like the Discord Notification).
10
+
11
+
## How to use?
12
+
On each folder, you will find an other Docker image. You can create a new repository, copy the code, including the *.woodpecker* folder that will create automate the Image creation for you on your private Docker Repository. That's how I use it with Forgejo!
13
+
14
+
But to ease your process, I've published every Docker Container on Github (maybe on Codeberg to if I can have the authorization), so you will have some link to use that to. But it's better to host it yourself. You know, avoid private owned service...
15
+
16
+
## More documentation
17
+
Here some links to documentation that I use when I need to create some new CI for my Godot games.
18
+
- [Itch.io butler](https://itch.io/docs/butler/)
19
+
- [GameCI's Steam Deploy](https://github.com/game-ci/steam-deploy): I use this as an inspiration to understand how to use SteamCMD in CI
20
+
- [Godot CLI](https://docs.godotengine.org/en/stable/tutorials/editor/command_line_tutorial.html)