Closed Sobuno closed 4 months ago
Thanks for the bug report! I can take a look this weekend.
It looks like the build failed here:
Is there a reason that the build process is hosted on CircleCI instead of as GitHub Workflows (like the CI pipelines)?
The CI pipelines are hosted on CircleCI as well.
Re-run was successful here https://app.circleci.com/pipelines/github/julianpoy/RecipeSage/3054/workflows/1ea4bcff-0e4f-4848-bab9-27ba67cb154a/jobs/5558
Looks like external dependency was down at the time of the original build.
The tag is on Docker hub here: https://hub.docker.com/layers/julianpoy/recipesage-selfhost/api-v2.13.7/images/sha256-dce1b8b7544e5ce579472d8a804192bdff7e4fd6b34a1401f95e9e2ec725f7f9?context=explore
Thanks :)
Yeah, I misremembered regarding the pipelines, seems it's only some deploy pipes on Github Workflows
No problem!
Yep, just a couple of simple scripts I have setup with Github Workflows. CircleCI didn't (still doesn't?) have a way to trigger workflows manually so that's why I set those up with Github Workflows.
Describe the bug The Docker image for julianpoy/recipesage-selfhost:api-v2.13.7 is not available. It seems the api images in general haven't been published for some months while the static images have
What page/area is the bug in? Infrastructure, I assume the CircleCi flows either failed or weren't run
To Reproduce
Docker pull julianpoy/recipesage-selfhost:api-v2.13.7
and watch it failExpected behavior Pulling should succeed
Screenshots Not applicable]
Additional context Wasn't sure whether to post it here or in the selfhosted repo. Decided to post here since the CircleCi files are in this repo.