-
Notifications
You must be signed in to change notification settings - Fork 185
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
One project's deployment is cancelled, and I don't know why ? #365
Comments
up ! |
up again, I tried to create a new project with the same repo and I still have the problem. The other new projects are fine tho. |
Apologises for the delay, I've been out of the country without a computer and I'm still catching up Are you using the HTTP URL for the repository or the SSH URL? If the latter, have you remembered to add the SSH key to the repository? Can you turn on debugging by running |
No problem ! I'm using the SSH url, the configuration is the same for all my projects. Yes I added it ; if not the error will be displayed explicitly anyway so I'm 100% sure it is not the case here. Also, the project has also been deployed successfully multiple times before this problem's first occurence. Here come the log :
There is also a lot a logs for others projects, but I pasted here only the one I got a problem with. |
Hmm, odd Bit of a hack but can you edit
then restart the worker with then try again and then post the log, looks like there is an error occurring which is unexpected but being caught. |
Ok so I got it. We are removing this submodule (it should not have been here in the first time). It will probably fix the error. I'll report the result to you. Anyway, Deployer was not alerting us about the error and I thing it's a feature/fix to work on, someday maybe :) (Here come the error that shows up with your hack:)
|
Yes, it does work now. Thanks for the help ! So feel free to do it if you want to :) Have a nice day ! |
wow, that is very interesting, yeah sounds like there should be some sort of way to report on such errors with git so leave this open and I'll see if I can some up with some ideas |
Before submitting your issue, please make sure that you've checked all of the checkboxes below.
composer install --no-dev
from the root of my installation.npm install --production
from the root of my installation.rm -rf bootstrap/cache/*
from the root of your installation.Expected behaviour
The deployment to be successful (or, at least, get a verbose message of what's going on).
Actual behaviour
So...
I got a setup with like ... 20 different projects.
All of them were working fine but since yesterday : we got one of our projects which doesn't work (by that I mean, cannot be deployed) anymore.
Actually, the process doesn't even start, it only prints "cancelled" in the first step (which is "Create new release"). Image below.
The weird stuff is, I got 2 others projects located on the same server, with the same user and same conf.
Only the bitbucket repositories are different so I don't know how it is possible that I can deploy the 2 projects successfully, but not the 3rd ?
Steps to reproduce
Click on the deploy button :)
Environment info
I tried a lot of things before coming here (also checking other similar issues) but nothing worked.
Thanks for your help :)
The text was updated successfully, but these errors were encountered: