Document how CI for official package builds is configured
Talking with @rymai we realized that it helps new release managers to understand how we go from tags to omnibus packages.
@marin you know best how everything is configured at the moment. What do you think about documenting it somewhere? I wrote this in Slack but I was going from memory:
omnibus-gitlab is an interesting CI job because it is sort of a meta-build
[11:04] it clones gitlab, gitlab-shell, gitlab-workhorse
[11:05] all from dev so that we can prepare a 'surprise' package in case of a security release
[11:05] we use Chef to put a specific SSH deploy key on the build boxes, and that key was added manually to the projects on dev that the omnibus build needs to clone
Depending on the level of detail this sort of gets into security stuff so I am not sure where to document it. What do you think @sytses ?