Loading…
This event has ended. View the official site or create your own event → Check it out
This event has ended. Create your own
View analytic
Wednesday, May 14 • 11:50am - 12:30pm
Improving Third Party Testing

Sign up or log in to save this to your schedule and see who's attending!

Prior to the Icehouse cycle there were only a couple third party test accounts. During the Icehouse cycle we added many more. What have we learned about using third party tests and how can we make that information more valuable for openstack?

I don't want this session to be a how to run a third party infrastructure. In fact I don't think we should spend much time if any at all on the third party side of the equation. Instead Openstack should be looking at what it can do to help third party testers and in turn the test results and projects they test.

Things to cover:
* Requirements for third party testers (logs, timestamps, minimal level of testing, etc)
* Should openstack prescribe a testing infrastructure?
* Account management. Can we make this self service?
* Criteria for gaining voting privs, losing voting privs (different rules for stackforge?)
* Most importantly, how can we better present the data to individual projects. I think there is some sense that the Gerrit comment system may not scale to 5 or more CI systems all interacting with a change. Feedback on what reviewers want to see, information they need would be great.

(Session proposed by Clark Boylan)


Wednesday May 14, 2014 11:50am - 12:30pm
B301

Attendees (44)