Drupal.org Testing Infrastructure

A brief outline of the current status and To-Do's for this DrupalCI component can be found within the Google Document link below:

https://docs.google.com/document/d/1QM7AIW6Qjh413mecCgEv55QEbMA-ryf5HGiP...

Summarized version: We have a simple form which will allows us to trigger Jenkins jobs, but still need to build out the automated triggering, configuration pages, on-demand job triggering capabilities, and all of the associated User Interface designs for deployment on drupal.org.

Overview

DrupalCI will start posting weekly updates to keep the community informed on the progress of the initiative. This is the first, welcome!

The most notable items from this weeks meeting are:

• Jeremy has an initial implementation of the "Simpletest" build step in the Job Runner.
• Nick has some mockups for a minimal viable product of the Results site.

Attendees

• Nick Schuch (nick_schuch)
• Jeremy Thorson (jthorson)

Background:

"Modernizing Testbot" is a Drupal community initiative with the goal of rebuilding Drupal.org's Automated Testing / Continuous Integration infrastructure, leveraging modern practices and tools in order to enhance the capabilities and functionality provided by the platform and better meet the changing needs of the Drupal community. The initiative first took root with the vetting of a potential design and architecture during the DevOps Summit at BADCamp 2013, which then led to the development of a functional Proof of Concept during DevDays Szeged. DrupalCon Austin saw a number of further refinements to the model, and launch of the official project pages/repositories on Drupal.org. This post is intended to provide a snapshot of what was accomplished.

A couple months ago, at the BADCamp devops summit, we held a workshop to discuss the architecture and operation of the current Drupal.org Automated Testing infrastructure, as well as to review a proposed future state architecture for the platform.

This post is an attempt to summarize the discussion, outline the proposed architecture as presented, and discuss some next steps.

On October 18th, 2007, Chad Phillips (hummonk) made an initial commit to the ‘Project Issue File Test’ module, with the description “initial commit of an integrated file testing platform for project issue module”. This kicked off the pursuit of automated testing integration between drupal.org and qa.d.o (then referred to as testing.drupal.org). In 2009, Jimmy Berry (boombatower) performed a significant overhaul and redesign of the system with the release of PIFT/PIFR 2.0, introducing a number of structural and architectural changes and improvements.

Looks like you can attach to the docker container's streams and then echo them back out so Jenkins can record them. An example can be found at https://github.com/salsita/jenkins-docker-skeleton. Alternatively you can run docker logs or -- I think -- docker run -a to attach the stdout / stderr streams. Also some information on looking at the logs at http://0x74696d.com/posts/docker-logging/.

Note: This is a copy of a blog post original posted on March 20th, 2012; with the original located at http://jthorson.doesdrupal.com/thoughts-on-testbot-evolution ... it is being reposted here in the interest of consolidating the information on Drupal.org infrastructure, and to improve discoverability by any potentially interested parties.

Having spent the better half of the last year within the PIFT/PIFR issue queues, chasing the holy grail of sustained testbot stability, I find myself reaching a bit of a crossroads.