On 07/11/2016 06:53 AM, Lori Jakab wrote: > Are you planning to publish logs/reports in case of failure so that > patch writer will be able to analyze the failure? > > > We will decide this based on the tests themselves, once we have them. > The test infra is behind firewall, so there won't be a web page with > extra info on the failure. As a result, at least some indication of what > went wrong should be in the failure comment. We will experiment with > different approaches.
If you haven't seen our new logs hosting [0] now would be a good time to
consider it ;) It's actually hosted out of Nexus [1] but has an Apache
front end on it to so we can give it a shorter name, and also to have it
handle the .gz pre-compressed files properly.
Our hosting URI format is:
${SILO}/${HOST}/${JOB_NAME}/${BUILD_NUMBER}
So, since we have a very well defined setup, we could work with you to
setup a user that has rights to push to locations located at
${SILO}/${HOST}/ for storing logs.
We don't presently have a job in place to clean things up, but the
intent is to host a maximum of 6 months which is definitely a lot longer
than the 40 jobs or 30 days we presently do directly in Jenkins. Since
we're not near that 6 month mark yet, as it only went into service a
couple of weeks ago, we've got time to get the clean-up script in place ;)
-Andy-
[0] https://logs.opendaylight.org
[1] https://nexus.opendaylight.org/content/sites/logs/
--
Andrew J Grimberg
Systems Administrator
Release Engineering Team Lead
The Linux Foundation
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Discuss mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/discuss
