deployer: Problem to build new projects after upgrading to 0.0.44
Before submitting your issue, please make sure that you’ve checked all of the checkboxes below.
- You’re running the latest release version of Deployer.
- Ensure that you’re running at least PHP 5.6.4, you can check this by running
php -v - You’ve ran
composer install --no-devfrom the root of your installation. - You’ve ran
npm install --productionfrom the root of your installation. - You’ve ran
rm -rf bootstrap/cache/*from the root of your installation. - You have restarted the queue listener and node socket server.
To help us better understand your issue, please answer the following.
Expected behaviour
The deployer shoud be able to clone properly the repository on BitBucket and run all “Active new release” commands.
Actual behaviour
Our deployer was at version 0.0.36 (I think, not sure). We had some problems about projects that got “corrupted” after running builds. So we upgraded it to version 0.0.44. We ran all the commands listed on the upgrade section at the Github.
The corrupted projects got back to normal, and we can create buils without any problem.
However, if we create a new project (with ou without specific commands to run), deployer can’t ever download the repository from Bitbucket. It get’s stucked on “Create New Release” as “running”. All the next steps get the status “Cancelled”.
We added multiple times the deployer’s autogenerated SSH key, without any success.
Steps to reproduce
- update deployer to version 0.0.44
- create new project without any command (just clone the repo)
- run a build
Environment info
Operating System: Ubuntu 14.04.4 LTS PHP Version: 5.6.23 Node Version: 0.10.45 Database System: MySQL Database Version: 14.14
Logs (see storage/logs/) or other output that would be helpful
I didn’t found any log by the correct ocurred time
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 1
- Comments: 25 (14 by maintainers)
Ah ha, it is the same issue as this https://github.com/REBELinBLUE/deployer/issues/262
For now, the only solution I have found is to increase the size of the beanstalk queue http://stackoverflow.com/questions/29199302/job-too-big-pheanstalk-what-can-be-done/32449935#32449935
I will close this issue and leave the discussion in the other one; I am still trying to figure out a nicer way to do this without having to increase the beanstalkd limits. I have a couple of ideas
Alright, meanwhile I’ll remove both verbose’s. If you need me to do some test, let me know.
Thanks for your help so far