Closed (fixed)
Project:
drupaltestbot-puppet
Component:
Miscellaneous
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
26 May 2013 at 19:25 UTC
Updated:
9 Dec 2013 at 20:10 UTC
Jump to comment: Most recent
Debian Wheezy has been released. It defaults to php 5.4 though...
At some point we'll need to do wheezy testbots. Not sure what will push us to do it. It shouldn't be dramatically hard.
Comments
Comment #1
jthorson commentedThere are no PHP 5.5 packages for Debian squeeze, so I can't even do a temporary 5.5 test while we're on Squeeze ... despite a heavy push from the core dev community to at least occasionally test on both 5.4 and 5.5. Given that, we should probably look at developing up a updated build that will work on other versions ... would it be difficult within puppet to manage two builds, depending on the version that is calling home to the puppet master?
Comment #2
rfayNot entirely sure why we shouldn't just move everything to wheezy. And yes, we could have two builds, easily. Not sure what the impact of that on the whole php project is.
I'm sure it would not be too hard to get us onto ubuntu as well.
Actually the only serious work here is getting the packages built for wheezy.
Comment #3
niko- commentedToday CodeSprint CIS admin team work on drupaltest bot migrating to debian Wheezy
I create sendbox project to https://drupal.org/sandbox/niko-/2062067 to push our work results for review
key features:
1. Puppet master successfully runed on Debian 7 (standard wheezy repo used)
2. bootstrap_testbot.sh from https://drupal.org/node/1748618 was rewrited to support Debian 6/7 and CentOS 6 OSes
3. Asure support was added becouse CodeSprint runned on Microsoft Asure instances
4. Standalone server support was added
5. We work on puppet config update and at this momment step by step bash scripts to run on debian 7 and CentOS 6 added into project Puppet config was not modified becouse time
Done:
1. Debian 6 instance will install with new script as usual
2. Debian 6 instance runs fine selftest, Quick core test and stoped while full core test run becouse instance performance (need test)
3. Script running on Debian 7 and CentOS do it prepear steps fine (except puppet config run)
4. On debian 7 mariadb 5.5 php 5.3.27 from dotdeb used, rest packages from debian Wheezy repo
5. On CentOS we using mariadb 5.5
Known problems:
1.We use php 5.3.27 from dotdeb. During install, Testbot upgraded php version to 5.4.4-14+deb7u3 (need package rependences check)
2. Need help for seaching php 5.3 repository for CendOS 6 (all CentOS 6 repo that we found used php 5.4 already)
Great thanks my team (Bober for coding, Softovick for coding and tesing)
Comment #4
rfayDid you actually commit everything to the sandbox? I found only a couple of partially done scripts for CentOS and Debian7. The CentOS6.sh one isn't even a valid shell script; I found no changes at all to the puppet script.
Comment #5
rfayI'm testing a Debian Wheezy upgrade. I haven't done any other distro, and probably don't intend to. I didn't find anything in the sandbox mentioned above that actually seemed to do anything, so just abandoning that. (And no response above). It's possible that something important wasn't pushed to the sandbox.
Comment #6
rfayAll the testbots 958 and higher (except the one-off 1828/1833, which I can do when jthorson approves) have been updated to wheezy tonight. These are using directly-applied 20131121_debian_wheezy branch of drupaltestbot-puppet.
puppetd + puppetmaster seems not to be working at least for these, I'll have to return to that.
I went ahead and used php 5.3.27 on the upgraded testbots, so that's in the equation as well.
I saw an 8.x build that had a single test fail. "Drupal\node\Tests\Views\FilterUidRevisionTest": Make sure that the view only returns nodes which match either the node or the revision author. Other FilterUidRevisionTest.php 61 Drupal\node\Tests\Views\FilterUidRevisionTest->testFilter()The upgrade broke 8.x apparently because of php 5.3.27, but the issue had been known earlier. #2143097: Figure out the FilterUidRevisionTest failutre - It's now fixed.
We did have a couple of testbots that had to be disabled because they were out of space.
Comment #7
rfayActive testbots have been upgraded.
drupaltesbot-puppet config pushed in http://drupalcode.org/project/drupaltestbot-puppet.git/commitdiff/ec9297b
* puppetmaster still has to be verified
* docs need to be updated
* AWS spinup needs to be verified
Comment #8
rfayI updated the doc, got puppetmaster to work, and am trying a 2-testbot AWS spinup.