Build just keeps running if recipe defined in build.yml is not present in recipes folder
I have run into what seems to be an interesting edge case. I renamed my recipe file, but accidentally didn't include the new file in the commit with the changed entry in build.yml. The build seems to have just stalled in the building custom image phase, with no errors or stopping (been 10 minutes now).
8 Replies
If this should be an issue on github, I'll gladly make one
Okay it failed after 15 minutes because no recipe
Maybe it just takes a while, perhaps a non-issue
That's really weird. Did you not see any kind of error about the file not existing?
you should send your logs
Not until 15 minutes or so
So based on the timestamps, it was performing all the setup before it got to the
bluebuild cli call which actually does the check and failed the build. Might be a good idea to have a check earlier in the action to see if the file existsBased on the length of time it took to get to the actual build, I'm assuming your running this on your own runner
Yep, whatever the default for a normal github account is
I'm really not sure why it took so long, it was rather abnormal