On Fri, Feb 22, 2013 at 7:06 PM, Matthew Flaschen mflaschen@wikimedia.orgwrote:
On 02/22/2013 09:38 PM, Chad wrote:
So, I've seen this site tossed around quite a bit recently, and I'm
curious:
is there any plan to start integrating this jenkins and our other
jenkins?
Depends on what you mean by "integrate". Right now the sweet spot for browser tests shown at https://wmf.ci.cloudbees.com/ is to track the deployment schedule over individual code commits and to target integrated institutional test environments like test2wiki and beta cluster, while https://integration.mediawiki.org/ci/ mostly targets unit-type tests run on the Jenkins host itself. There are a lot of builds there right now already.
In the longer term we want to have browser tests targeting more specialized test environments and more granular code commits. There are lots of ways that Jenkins instances can share data, so when that sort of activity comes along we'll figure out the details at that time.
More importantly: is there any chance to get the results of these sorts of
tests in Gerrit? I think it's great that we're expanding test coverage,
but
without feedback on people's patches they're usually unaware that they're breaking things.
As of today browser test status changes are being reported to #wikimedia-dev by a bot named "wmf-jenkins-bot", e.g.:
(09:30:18 AM) wmf-jenkins-bot-: Project _debug-irc build #17: SUCCESS in 90 ms: https://wmf.ci.cloudbees.com/job/_debug-irc/17/
Integration with Gerrit as well as Jenkins is certainly feasible, and as the information provided by these tests becomes more closely tied to the code itself rather than the environments in which the code is deployed, we can put that integration in place as it becomes valuable.