Dedicated beanstalkd queue servers for Drupal.org

q-vip.drupal.bak is ready to be used.

The servers are just a simple beanstalkd service writing its binlog to a drbd block device managed by heartbeat for failover of beanstalkd, drbd and the virtual IP.

Deployed

Could this affect packaging and commit logs on project pages? I have pushed several commits to my project but they don't show up in the commit log (it does show in cgit) and it has not repackaged a new version.

Project page: https://www.drupal.org/project/migrate_yaml
Commit log: https://www.drupal.org/node/2693311/commits

I resynced the migrate_yaml repository to Drupal.org and the commits are all there now. This doesn't seem to be a problem for other projects, I'm not sure what the root cause might have been.

What IP address does git.drupal.org resolve to for you?

Thanks! I think it should package on the next push, right?

This is the IP I see on ping:

$ ping git.drupal.org
Pinging git-vip.drupalcode.org [140.211.10.43] with 32 bytes of data:
Reply from 140.211.10.43: bytes=32 time=308ms TTL=49

That's the correct IP. And yes, packaging should happen 5-10 minutes after pushing, although the queue can be backed up as much as an hour.

Thanks for the update. Yes, I expected those timeframes for packaging but it has not happened since I created the release. I will try and see if it happens now after another push.

Hi @drumm, I am still facing the issue I described in #5. It show commits and package up until when you resynced it but new pushes don't show up and package is not created. I can see the commit at http://cgit.drupalcode.org/migrate_yaml/log/?h=7.x-1.x.

Please let me know if I should create a new issue for this (and if so, where?)

I re-synced the repository again and looked over some logs, I can't spot any problems.

If it happens again, a new issue in this project would make sense. Please include details on how you push, including pasting any command line code and output. Looks like you are successfully pushing to the Migrate Reports project.

Thanks! I'll do that. I use the regular git commands for commit and push (in fact, I use git command from dreditor output on the issue). I will save the command and output next time I run in case it doesn't work.

I found the root cause for migrate_yaml: #2709577: Some projects missing Git hooks

Thank you for the update. I will report back if there is still a problem.