-
-
Notifications
You must be signed in to change notification settings - Fork 222
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
releases set-commits <commit> --auto --ignore-missing
fails with error: could not find repository at '.'; class=Repository (6); code=NotFound (-3)
#2157
Comments
Hi, the |
@lforst I'm pretty sure we're just printing the error generated by the library here. We can likely format it better |
This used to work in the context of a docker build and suddenly stopped working after we renamed the repository. See https://github.com/kentcdodds/kentcdodds.com/blob/34014471facce523e1401299431ac4a5d0bd1943/Dockerfile#L57 for an open source example of a very similar setup. We also tried setting auto to false and manually specifying the commit but it also fails with the same error. |
@felangel I don't entirely see how the kentcdodds repo is similar. They're not collecting commit data for Sentry as far as I can see. My guess is that you used to copy your |
They’re also using the vite plugin and specifying setCommits to auto: https://github.com/kentcdodds/kentcdodds.com/blob/34014471facce523e1401299431ac4a5d0bd1943/vite.config.ts#L49 Our Dockerfile hasn’t changed unfortunately but I’ll take a closer look at the container in a few minutes. I can also try to make a minimal reproduction sample later today, thanks! |
@lforst the likely culprit seems to be the fact that we moved to a monorepo with multiple apps which means the directory we build from no longer contains a |
@felangel The vite plugin needs to run inside a git folder to be able to associate commits. It is an abstraction around Sentry CLI. You can work around this restriction by using Sentry CLI and associating the commits after the fact: https://docs.sentry.io/product/releases/associate-commits/ |
CLI Version
2.36.1
Operating System and Architecture
Operating System Version
debian:12
Link to reproduction repository
No response
CLI Command
sentry-cli releases set-commits --auto --ignore-missing
Exact Reproduction Steps
apps/my-app
)npx @sentry/wizard@latest -i remix --url https://sentry.io
Dockerfile
.sentry_auth.txt
docker build --build-arg COMMIT_SHA=<COMMIT> --secret id=SENTRY_AUTH_TOKEN,src=.sentry_auth.txt .
Additional Context
vite.config.ts
package.json
Expected Results
I expect the build to succeed and successfully upload source maps and commit information to sentry.
Actual Results
Build fails with error:
Additional Context
The build succeeds if we remove
setCommits
from the build step:Logs
The text was updated successfully, but these errors were encountered: