[Libreoffice-qa] The garbage into the dev-builds.libreoffice.org

V Stuart Foote VStuart.Foote at utsa.edu
Tue Oct 29 02:22:52 CET 2013

Pedro wrote
> One other request: your Tinderbox is not creating the txt files with the
> build info. Unfortunately this is the only element that allows QA to know
> from which TB each binary came from (before installing, obviously) so it
> is quite important that it is generated with the binary...

Not really a problem... just inconvenient.

Fortunately it is trivial to obtain the build details from the Tinderbox
Status Page -- either the Summary log or the Full log of each build.  To
locate, you only need to adjust from local time stamp to its UTC time stamp
to locate the correct log.

Unfortunately that  currently gives just a 48 hour rolling window showing
just the recent builds.  Once beyond that window and posted to the
corresponding TB directory on
http://dev-builds.libreoffice.org/daily/master/  without the build text for
each msi package, there is no way to know what commit signature to use to
locate the build via cgit query --

And at that point,  it is only when installed that the Dev build is tagged
with the final commit signature--viewable in the Help --> About as the Build
ID.  It might be helpful to extend to sliding window for the TB, maybe out
to  7 days.

Alternatively, it has always seemed unfortunate that the Build ID commit
signature is not exposed within the Windows MSI installer package.  Not sure
how difficult that would be to implement, but it would eliminate dependence
on the external logs and reinforce use of Git resources.

View this message in context: http://nabble.documentfoundation.org/The-garbage-into-the-dev-builds-libreoffice-org-tp4074218p4080247.html
Sent from the QA mailing list archive at Nabble.com.

More information about the Libreoffice-qa mailing list