I have installed and configured Deploy exactly as described at Installing Deploy.
When I try to push a "Basic Page" to my endpoint, nothing happens after running cron, and the deployment plan still says "processing." I am using the latest dev versions of deploy, services, uuid.
Here's the output from Drush:

drush -v dp sync_to_production
Initialized Drupal 7.12 root directory at /srv/www/dev.mysite.me/html [notice]
Initialized Drupal site default at sites/default [notice]
WD deploy: Deployment of sync_to_production started. [info]
WD deploy: Deployment 582f4e4d-3898-2ea4-ad11-234964ca16b9 is processing. [info]
WD deploy: Deployment 582f4e4d-3898-2ea4-ad11-234964ca16b9 is processing. [info]
Command dispatch complete [notice]
[root@pluto html]# drush -v core-cron
Initialized Drupal 7.12 root directory at /srv/www/dev.mysite.me/html [notice]
Initialized Drupal site default at sites/default [notice]
WD cron: Cron run completed. [notice]
Cron run successfully. [success]
Command dispatch complete [notice]

There's no messages in watchdog except for the initial Deployment message below:

Type deploy
Date Tuesday, April 3, 2012 - 21:32
User Anonymous (not verified)
Location http://dev.mysite.me/index.php
Referrer
Message Deployment 582f4e4d-3898-2ea4-ad11-234964ca16b9 is processing.
Severity info
Hostname 127.0.0.1

The endpoint site has nothing at all in watchdog from deploy and shows no attempts to login.
I have no idea what I am missing.

Comments

aspilicious’s picture

aspilicious commented

You should run cron afterwards if you chose the queue processor.
With the memory processor it will be transfered imediatly.

If you want to change processors, remove the old plan first, just to be sure everything will be ok.

stongo’s picture

stongo commented

I added a plan using the "memory processor" and the plan deploys fine from the source at least.
I re-created another plan using "queue api" and it never moves past "processing" after running cron several times, so it seems like deploy isn't being added correctly to the cron queue.
I also found a missing step in the documentation Installing Deploy. It should mention that while editing the destination's rest server resources, enabling the user actions "login" and "logout" are mandatory when using session authentication as instructed in previous steps.
Should I create a separate ticket for this?

aspilicious’s picture

aspilicious commented

Stongo it's a wiki page you can edit the page yourself. Don't be afraid to screw things, it has version control so I can revert if needed.

aspilicious’s picture

aspilicious commented
Status: Active » Fixed

Marking this fixed

Status: Fixed » Closed (fixed)

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

tushar.behera’s picture

tushar.behera commented

Deployment module is not working. This is only showing "processing" at time of deployment. I tried lot using stage and live but there is no out come. Please give the solution to over come this problem in drupal 7.

boobaa’s picture

boobaa
he/him
commented
Status: Closed (fixed) » Active

I am running into the same problem, but having some more information: I can deploy some of the content types from a site to another, but I can't deploy a specific one from the same source site to the same target site. No errors anywhere, and the target site does not even log a login request when this happens. Tried the latest -dev version with whatever settings, without luck. Will report back with my findings once I get them.