I guess it depends on what making it official means. If it’s just linking to it when asking to test a patch in a bug report or to point a problem in a patch review, you can of course do that. For more than that, I’m not sure it would be a good idea.
There’s no quality backend behind that page. I didn’t bother learning how to setup, manage and integrate something like concourse or jenkins, I just wanted to write “a little script” to use gerrit’s REST API and maybe make a build. It got out of hand and I’m not a real developer, so you can guess how the code looks. No config file, hardcoded stuff as I needed it, code repetition, no separation of concerns… If you were thinking of integrating it in Haiku infrastructure, I guess it would be simpler to write whatever concourse needs. It would certainly be easier to mantain, and The Right Thing to do.
Work is done in bursts. The script will go idle for a few hours then have a conversation with gerrit and start building stuff if there are new patches. It also won’t rebuild everything when there’s a new release. So a new change may not have feedback for hours, and an existing change affected by a recently merged one may not be updated for days.
There’s also no attempt at following patches’ dependencies. When there are several commits in a branch, two builds are attempted: one rebasing all the branch and another one cherrypicking just the last commit. No check for updated intermediate changes, for example, or any other thing one should look for in a relation chain.
I don’t have alerts or even safe failure code paths. If something fails, the process dies and may leave some stuff in limbo, even with some garbage behind. It will run again a few hours later, triggering the same bug (low disk space would be an easy one for a “self denial of service”) or maybe not, in which case no one would notice until an unlucky soul tries to get the half done build.
If you think all that is just a mild inconvenience and still want to promote it as official, I’m OK with it.
If you still want it to report build status to gerrit, point me to the details and I’ll see what I can do. I guess post review with verified label +1/-1? But please let’s make it only if the score can be manually overridden or disregarded by those who can merge.