This is the cantrip in devstack-gate that's collecting the logs into the compat format:
https://github.com/openstack-infra/devstack-gate/blob/3a21366743d6624fb5c51588fcdb26f818fbd8b5/functions.sh#L794-L797 It's also probably worth dumping the whole journal in native format for people to download and query later if they want (I expect that will become more of a thing): https://github.com/openstack-infra/devstack-gate/blob/3a21366743d6624fb5c51588fcdb26f818fbd8b5/functions.sh#L802-L803 If you are using devstack-gate already, this should be happening for you. If things are running differently, those are probably the missing bits you need. -Sean On 05/04/2017 03:09 AM, Guy Rozendorn wrote: > In regards to 3rd party CIs: > Before this change, the screen logs were saved under $LOGDIR and copied > to the log servers, and it was pretty much under the same location for > all the jobs/projects. > > What’s the convention now with switch to systemd? > * should the logs be collected in journal exported format? or dump to > simple text files so they could be viewed in the browser? or in journal > json format? > * is there a utility function in devstack/devstack-gate that takes care > of the log collection so it’ll be the same for all jobs/projects? > > > > On 3 May 2017 at 13:17:14, Sean Dague (s...@dague.net > <mailto:s...@dague.net>) wrote: > >> As a follow up, there are definitely a few edge conditions we've hit >> with some jobs, so the following is provided as information in case you >> have a job that seems to fail in one of these ways. -- Sean Dague http://dague.net __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
