runbot/.gitignore

# dotfiles
.*
# compiled python files
*.py[co]
# emacs backup files
*~
# runbot work files
runbot/static/build
runbot/static/repo
runbot/static/sources
runbot/static/nginx
runbot/static/databases
runbot/static/docker
runbot/static/docker-registry
bzr import runbot and document_fs 2014-05-26 06:56:21 +07:00			`# dotfiles`
			`.*`
			`# compiled python files`
			`*.py[co]`
			`# emacs backup files`
			`*~`
Add runbot work files to gitignore 2014-06-15 06:32:08 +07:00			`# runbot work files`
			`runbot/static/build`
			`runbot/static/repo`
[IMP] runbot: share sources between builds Multibuild can create generate a lots of checkout, especially for small and fast jobs, which can overload runbot discs since we are trying not to clean build immediatly. (To ease bug fix and allow wake up) This commit proposes to store source on a single place, so that docker can add them as ro volume in the build directory. The checkout is also moved to the installs jobs, so that builds containing only create builds steps won't checkout the sources. This change implies to use --addons-path correctly, since odoo and enterprise addons wont be merged in the same repo anymore. This will allow to test addons a dev will do, with a closer command line. This implies to change the code structure a litle, some changes where made to remove no-so-usefull fields on build, and some hard-coded logic (manifest_names and server_names) are now stored on repo instead. This changes implies that a build CANNOT write in his sources. It shouldn't be the case, but it means that runbot cannot be tested on runbot untill datas are written elsewhere than in static. Other possibilities are possible, like bind mounting the sources in the build directory instead of adding ro volumes in docker. Unfortunately, this needs to give access to mount as sudo for runbot user and changes docjker config to allow mounts in volumes which is not the case by default. A plus of this solution would be to be able to make an overlay mount. 2019-07-08 19:44:32 +07:00			`runbot/static/sources`
[IMP] runbot smaller status bar 2015-01-18 19:51:42 +07:00			`runbot/static/nginx`
[IMP] runbot: update gitignore for static databases 2019-12-17 22:25:54 +07:00			`runbot/static/databases`
[IMP] runbot: build docker image once per loop turn At this moment, the Docker image is built at the beginning of each runbot build. This blocks the _scheduler while the image is built. With this commit, the image is built before calling the _scheduler and is not linked to a runbot build. Also, the necessary dirs are created in the static path before starting the loop. 2020-01-20 21:10:57 +07:00			`runbot/static/docker`
[IMP] drunbot: docker registry The current runbot infrastructure has 100+ machine that will each build all docker images. This is unpractical for multiple reasons: - impotant load on all machine when the build could be done once - possible differences for the same image depending on the moment the base was pulled on the host. An extreme example was the version of python (3.11 or 3.12) when building the noble docker image before it was stabilized. - increase the chance to have a docker build failure in case of network problem. (random) A centralized registry will help with that, and allow future devlopment to generate more docker images. All docker images will be exactly the same, the pull time is faster than build time, only one build per docker image, ... 2023-07-13 15:12:23 +07:00			`runbot/static/docker-registry`