I am working on a static site that I update on Kinsta via automatic deployment on Github commit. This has worked well since I started about a month ago, until the last few days. Now, I am consistently getting “Build and rollout failed”.
The trouble is that no reason is provided for the failure of build and rollout. My site is well under the storage size limit of 1 GB, but I did increase the number of static pages in the project in recent commits. The project has 34796 files at the moment. It works fine locally.
The Kinsta deployment messages look like this:
Cloning into ‘.’ …
…
Updating files: 100% (34796/34796), done.
HEAD is now at [git commit] [commit message]
I really hope anyone has some pointers as to how to fix this. Not sure if it is something I can fix or if this is an issue on Kinsta’s side.
I’m sorry to hear you are having difficulty with deploying your static site! I understand the impact this can cause, and the importance of resolving this issue as soon as possible!
I understand that your site is under the 1GB static site size limit, so this should not be causing the issue. I would like to review the logs to see what could be causing this issue to occur. If you could please send me a private/direct message with the domain name of your static site. This will allow us to locate your site on our backend and review the logs for more details.
Thanks for following up with me in the DM. We have reviewed your site configuration, and noticed it appears a build command was not set. Have you used a build command previously when deploying the site? If so, please do make sure that it is set under the “Settings” >> “Basic details” page of the static site’s MyKintsa page.
However, if you haven’t used a build command previously please let us know.
Please let us know if setting a build command if one was used previously resolves the issue. Or, if you haven’t had to set a build command previously.
I do apologize about our delay in reply. We are continuing to investigate internally into this issue and determine the root cause of the problem. I do see it appears that you were able to have one successful deployment recently. However, I see the latest deployment attempt also had an error.
We will provide another update as soon as possible once we have more details to share. In the. meantime, please don’t hesitate to reply if you have additional details you would like to share or have any questions.
It started to happen to me too. There was a change of build configuration on Kinsta side around July 10th. It seems that Kinsta is automatically trying to install it instead of relying on the build command.
See, the log of the first build that started to fail, It adds the npm install command. In my case that makes the build fail, since the command should be npm install --prefix landing since the static site is not in the root of the GitHub repo.
I’m sorry to hear you are also experiencing an issue with deploying your static site. I understand an error like this can be frustrating, and we want to help get you going in the right direction towards a solution.
As I understand you previously were able to deploy your site. However, now you are experiencing an issue due to the “npm install” install command being set by default without the --prefix option. This appears to be run first before your build command resulting in the issue as the files are not located within the root of your GitHub repository.
I am checking into this further with our team to see if there is a way to modify this behavior so that you can deploy your static site successfully. As our development team works normal business hours Monday - Friday we may not have an update over the weekend. However, we will provide an update by Monday with more details.
We appreciate your patience while we look into this further. In the meantime, if you do have any questions or have any additional details you’d like to add please don’t hesitate to reply.
I wanted to update you that our development team is actively looking into your case. We understand how important this is to you, which is why we are working diligently to resolve the matter as quickly as possible.
We will keep you informed of any progress and appreciate your understanding during this time. If you have any additional information or questions, please don’t hesitate to reach out.
Thank you for your continued patience and support.
Thanks for the update. Although I need to push an important update tomorrow. If I’m still not able to build it I might need to change the provider, at least temporarily. I’m just surprised that this change happened without notice.
Hi @marcelpinto, I’m afraid that we don’t have a specific ETA for this. We understand your need to temporarily change provider, we’ll update this thread as soon as the matter is resolved.