We do not have it. The underlying data structure was to parse XML from OBS _results API. When that took 10+ seconds to just fetch data from openSUSE:Factory, we needed different solution. Adrian…
prior to using redis, I wanted to fetch this data via the _results endpoint, but it was terribly slow for projects like Factory. _results is mostly meant to be used for single package results, and…
Just fetch the json output. That's all the data that we have. There's additional data which host it's building on or scheduled on, if it's building or scheduled.
The "dirty" flag in json/xml is…
REDIS data knows nothing about SCMSYNC or project META here. It only knows repository data. It's being fed directly from OBS scheduler, not going through the frontend database.
func LinkToBuildlog(R *common.BuildResult, S *common.PackageBuildStatus) string { |
Above is where the package link is…
This is "OBS" centric... If we want package-centric we'd probably need output like registry.opensuse.org to accommodate all the possibilities. It's definitely possible to do.
func ParseMimeHeader(req *http.Request) *MimeHeader { |
This is the type function.
It's seemed to handle in the go library as alternative that popped in my head was file extensions and that is more messy.. And I've only had one case where someone wanted to use this and they…
What is the usecase to linking to JSON or XML results where you cannot specify accept header?
I'll entertain a patch for this (eg. via GET parameter) if there's an actual, valid use-case…
And not providing the link to last build result when build is blocked is also somewhat stupid
Patches welcome. We added recently last build results on the Redis backend, but that's not…
You are missing the tarball here. Also, please use osc sr Java:packages jameica openSUSE:Factory for Factory submissions.