Comments

jthorson’s picture

rfay’s picture

Project: Drupal.org Testbots » drupaltestbot-puppet
rfay’s picture

Committed and deployed in d4f28b7bf and e3fceab. I'm doing followup tests on a temporary testbot, but I think the next step should be to upgrade (puppetd --test) one of the working testbots.

rfay’s picture

Status: Active » Fixed
rfay’s picture

Process was:

  1. Updated the minor changes to the puppet script
  2. Got packages from archives.dotdeb.org, wget -P . -r -l0 -A.deb http://archives.dotdeb.org/dists/squeeze/php5/5.3.10/binary-amd64/ (but this actually got the whole directory tree, not what we wanted). I manually mv'd the deb files into var/www/packages/pool/main/ and then deleted the archives.dotdeb.org directory
  3. Ran the updater script /var/local/apt-repository/repository_update.sh
jthorson’s picture

Let's wait until after feature freeze to deploy live. ;)

And welcome back (I think!)

rfay’s picture

Project: drupaltestbot-puppet » Drupal.org Testbots

This is now deployed on 654. Moving back to testbot queue for visibility.

Upgrade is just
puppetd --test

chx’s picture

So... are all bots upgraded now?

jthorson’s picture

They are all ready to be upgraded ... only 664 has actually been deployed. I had hoped to try and squeeze the D8 verbose assertion issue into a new release and update them all once that was complete, but was not able to get back to it last weekend.

I was going to wait until I knew I would be around for an hour or two before upgrading the rest, in case of any unforeseen issues which popped up ... but given that there is no backlog of patches in the system right now, I can try and fit them in before my next meeting this afternoon.

jthorson’s picture

Everything except for 813, 953, and 978 have been updated ... these three were running tests at the time, so will have to be caught up once the current tests are cleared.

jthorson’s picture

Status: Fixed » Active
jthorson’s picture

Status: Active » Fixed

Remaining bots have been updated.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.