Closed maitredede closed 5 years ago
You can create variants that only have a config file.
You can also use config.local
file.
Also - if you have CI solutions that work for you sharing would be great to help others. Due to loopback devices it can be tricky (the reason I didn't get docker working yet).
I will try and give feedback... If I remeber, I managed to achieve CI building of raspbian image... I will try to get the code, and give feedback :)
Hi,
I saw the new docker build, I love it. But I can't build a CustomPiOS yet.
My env is Gitlab, and the first problem I have is docker : cannot enable tty mode on non tty input
. I will try to fork and do some tests (the first will be removing the t
from docker run -it
).
On local computer, I first build you docker image : I had an issue with the initial build_docker
file, but I ran docker build myself.
Then I made a git repo with CustomPiOS as submodule, a "prepare" task that download the raspbian distro (if not in cache). And I have 2 operating system in this repo. They don't share modules (yet), but they build fine.
Yes, removing the -t
should work. Also if its automated the -i
for interactive should go too.
Closing if no reply
Hi, I am integrating the build process into a gitlab CI,and it is possible to define the "config" file name before calling the
build_custom_os
script, so I can create one config file per target I would like to build. Thanks.