Drupalcon Chicago PIFR/PIFT Code Sprint

You are viewing a wiki page. You are welcome to join the group and then edit it. Be bold!

Posted by rfay on March 10, 2011 at 2:22pm
Last updated by rfay on Thu, 2011-03-10 14:42

I'm planning to sprint Friday on PIFR/PIFT (our d.o testing infrastructure) and would love to have everybody involved (or who wants to be involved) in there.

Here are things I think we could do:

Merge boombatower's work on HEAD with the 3.x work done for the Git migration.
Make testing work for the 8.x branch
Create a standard test environment (and an easy one to recreate) so that new changes to the testing framework can be tested. We need an environment with PIFT, PIFR server, and PIFR testbot to do this, and we should be able to do it on one machine (perhaps with 2 mysql servers on that machine).
Solve some outstanding criticals happening right now.
Discuss the future (how does this fit with ci.drupal.org, etc.)
Plan for hardware needs and getting things onto d.o infrastructure

Please add to this as you see fit.

Comments

Outcomes of the sprint

Posted by rfay on March 13, 2011 at 5:42pm

We made great progress in the sprint. fiasco, deekayen, and beejeebus joined in and we did these things:

Moved the drupaltestbot project (debian packages that create provide basic testbot facility) to http://drupal.org/project/drupaltestbot from http://github.com/damz/drupaltestbot (note that I promoted this since the sprint)
Moved the drupaltestbot-puppet project to http://drupal.org/project/drupaltestbot-puppet from http://github.com/damz/drupaltestbot-puppet (promoted since the sprint)
Moved the pifr_setup script (which we hope to get away from) to http://drupal.org/sandbox/rfay/1089432 from http://github.com/scor/pifr_setup.
Updated drupaltestbot-puppet so that it works with Debian Squeeze (and no longer works with Lenny)
Made minor updates/tweaks
Began integrating nbertram's pull request from https://github.com/damz/drupaltestbot-puppet/pull/2 into drupaltestbot-puppet, but had some conflicts that still need to be resolved. It overwrites some key things that have happened since that work was done.

Perhaps one of the most important outcomes of the day was that all four of us got more familiar with the piece parts and deployment process (and needed simplifications)

Next steps:
1. Deploy the existing testbots on squeeze
2. Get to the PIFR critical issues
3. Build a staging environment so we can get PIFT and PIFR deployed with boombatower's HEAD.

Thanks for the wonderful work, and it was a delight working with you!

Drupalcon Chicago PIFR/PIFT Code Sprint

Comments

Outcomes of the sprint

Drupal.org Testing Infrastructure

Group organizers

New groups

Group notifications