Deployment triggers not working properly
deployments not being triggered properly..to fix i've had to add a random file and rename it everytime it fails to trigger...
21 Replies
Project ID:
939b69c6-fcd6-4f23-88ef-9abfc432c00fN/A 939b69c6-fcd6-4f23-88ef-9abfc432c00f
triggers on what? branch changes? cron jobs?
branch changes
can you send a screenshot of the branch’s commit history and indicate where the commits failed to trigger, then show me what changes were made in that commit?
additionally, please show me the branch trigger setting in Railway
as you can see the sequence is off by a commit, thats because I had to add a commit in order to get it to trigger
so for ex #62 and #71 is what failed to trigger
the changes ? substantial in each
there is no "failed" message but I am using the word to describe that there was no trigger
please show me the commits on Github
As well as your branch trigger setting on Raikway
And here's the commit status on one of the failed triggers:
hmm interesting. was hoping we’d see an empty commit there but it’s very full
tagging in the team
Thread has been flagged to Railway team by @Adam.
yea, by chance i got it working with a empty txt file but thats not quite ideal...workable but yea would be great if it worked as well as it did prior
I should note, they MAY have been manual pull requests.. that might give you a direction on what is going on
hi! this is interesting. were you only experiencing the issue on 10/28? can you explain what you mean by you got it working with an empty txt file? if you undo the "fix", are deployments still not being triggered after you commit or merge into main?
@arber.inc ^
pinging for visibility
After failed auto triggers, I had to add a file to the repo in order for it to work.
As for removing the file, I will have to try that the next time it occurs..
ooh okay, I'm following now. if you updated existing files, the deployments would not trigger. but if you added a new file, it worked as expected. I'll create a ticket for us to dig into this.
just one clarifying question - for this service, were auto deployments working as expected and then suddenly stopped? if so, was there anything different/special about the commit(s) that were merged into
main when it stopped?no nothing out of the ordinary, just didn't trigger.. so far since has been okay though
okay thank you for the info, and thanks both for raising! we'll look into it