Emmanuel, On 4 February 2016 at 21:53, Emmanuel Kasper <[email protected]> wrote: > Yes Steve from the cd team agreed about the idea but nothing has been > done yet (everyone is busy, that's life) I am also considering looking > for a sponsor for a build server inside this list: > https://wiki.debian.org/ServicesHosting#Outside_the_Debian_infrastructure
Looking though "debian-cd" archives, I've found a thread[1] where you talked with Steve McIntyre about this. Digging though the messages, there is no mention of how this would be done. Have you guys talked about the technical side of the proposal? For a simple start, I thought about a script that its input is how the image can be built (e.g. go to this directory and run this command). At the end of the process, it would save a fila containing all the relevant build information (e.g. has it failed? What packages have been installed? When it started and when it finished?). Then, in the following runs, it will use this information to decide if the image should be built again or not (e.g. has it failed in the last run? the last image was built over a week ago?). We could even use the Debian Security Announce RSS[2] to find out if a previously built image is vulnerable, comparing its package list with recent advisories. [1]: https://lists.debian.org/debian-cd/2015/10/msg00051.html [2]: https://www.debian.org/security/dsa -- Tiago "Myhro" Ilieve Blog: https://blog.myhro.info/ GitHub: https://github.com/myhro LinkedIn: https://br.linkedin.com/in/myhro Montes Claros - MG, Brasil
