The sanity graphql deploy command would not exit after a successful deploy
Command
sanity graphql deploy --no-playground --force
Could anyone please suggest any solution for the same?
Thank you
Related
I get this error in my Deployment (Acceptance) Stage in the SAP Continuous Integration and Delievery Service.
I have a .pipeline/config.yml file in my project.
When I deploy "normal" with cf deploy in BAS everything works fine, so there is something wrong with the config.yml I guess. Before I also get some buildpack/node error, so I added this to my package.json:
But I don't know what "Staging error" should mean and why it only fails in my pipeline?
Some further errors in my logs:
Approuter in mta.yaml:
My package.json in approuter:
Does anyone have clue?
Kind regards
Sebastian
Kicking off some much overdue TDD with Serverless.
I've installed serverless-mocha-plugin as per https://serverless.com/blog/tdd-serverless/
When I try to sls create test -f I dont get any output
I have tried a few different params to but no results. No test is created. I've tried SLS_DEBUG=true and nothing of interest is shown there either
The output of sls command shows the invoke test and create test functionality is available.
Anyone got any ideas on where start debugging this?
your serveless might be outdated; update it via npm install serverless -g
and your plugin is outdated as well, try installing and adding in your serverless.yml file; jest is from mocha and they're test functionality are the same
plugins:
- serverless-jest-plugin
then install via
sls plugin install --name serverless-jest-plugin
then try the create test again
Trying to deploy a Node app and usually have no issues at all. Now I'm having TypeScript resolution errors that only fail on Heroku but work locally and I have no idea how to test it ON Heroku.
I know I can do heroku run bash but then I'm just in an empty directory without my code.
I'd like to heroku run bash after the failed build and look around and run my commands as Heroku would so I can see why I'm having module resolution errors.
Can't find anything about it on Google whatsoever
I want to deploy django app to heroku via codeship and it generate an error and that is wget -O/dev/null http://something.herokuapp.com
How to fix the problem
Marko from the Codeship team here. Could you paste some more log output, or open a ticket on https://helpdesk.codeship.com?
Judging from the command you pasted above, I'd guess the check if the Heroku app, that you just deployed to, is running fails and this causes the build itself to fail.
Without any additional configuration we check the root URL for your application at http://HEROKU_APP_NAME.herokuapp.com via wget and see if it returns an HTTP/2xx or HTTP/3xx status code.
If it does, the check succeeds, else the build fails.
You can take a look at the script we use to perform the check at https://github.com/codeship/scripts/blob/master/utilities/check_url.sh
So, if I run the command heroku ps:restart event_machine.1 --app app-name I get what I want. However, I'm trying to automate our travis-ci deploy process. What needs to happen is the following:
We have a successful test run.
Next, we deploy the code
If we deploy the code successfully, we need to execute a few rake tasks that tell an external service to rebuild it self.
Once this is fired off, we need to restart the heroku app. In travis, ideally, this would be executed on the heroku machine via a deploy run command. This would be done in much the same way that we run bundle exec db:migrate.
Does anyone have any thoughts on how we we can restart a particular dyno(s) via a command that can be ran via heroku run something as that is what travis is executing in the deploy run.
So, to answer this we had a procfile that is executing a rake command to spin up event machine. We've modified this at the proc file level to first tell the external service to rebuild it self, before starting the event machine. This takes travis completely out of the deployment loop, which is better because it allows Heroku and Travis to each do what they should be responsible for.