a month ago
Details:
- Service: Anna.I-OS
- Project ID: 5a1788b4-0e47-422d-bcd9-fbc6305181c5
- Affected deployments: eb7572ae, 579b4c92, 9e678fa9, 646dcf5a, 7e5f08fb, e1cb4937
Problem: The PRE_DEPLOY_COMMAND deployment stage executes and fails with "Pre-deploy command failed" error even though:
- preDeployCommand is null in service config
- preDeployCommand is empty string in service config
- preDeployCommand field is omitted from deploy config entirely
The stage produces zero logs and causes builds to hang when set to empty string.
Build itself works perfectly every time (all three build stages complete successfully).
Request: Is there a platform-level setting, cache, or bug preventing the PRE_DEPLOY_COMMAND stage from being skipped?
1 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 month ago
a month ago
Hi,
I'm running into what looks like a platform issue with deployments.
Service: Anna.I-OS
Project ID: 5a1788b4-0e47-422d-bcd9-fbc6305181c5
Affected deployments:
- eb7572ae
- 579b4c92
- 9e678fa9
- 646dcf5a
- 7e5f08fb
- e1cb4937
I've tried setting preDeployCommand to null, an empty string, and removing the field completely. Despite that, every deployment still creates and runs the PRE_DEPLOY_COMMAND stage.
The stage doesn't generate any logs. When the value is empty, it hangs before eventually failing with "Pre-deploy command failed."
The build itself works perfectly and all build stages complete successfully. The only failing part is the PRE_DEPLOY_COMMAND stage.
Could someone please confirm whether this is a cached configuration or a platform bug that's causing the pre-deploy step to run even when no command is configured?
Thanks in advance!