Could not determine any commits to be associated automatically

[jwu-au]

Important Details

How are you running Sentry?

• On-Premise docker [Version xyz]
• Saas (sentry.io)
• Other [briefly describe your environment]

Description

[What happened]
This is similar to bug 11055.
I'm using Github.
It is working for the first repository, but not working for the second repository.
We're currently put it in the same organization, but with two different project.

Steps to Reproduce

Unable to auto associate commits.
Saying no matching revision found.

  INFO    2019-02-25 16:13:35.431328900 +11:00 Resolving HEAD (Org/Project111@HEAD)
  DEBUG   2019-02-25 16:13:35.433325800 +11:00   Got reference URL for repo Org/Project111: https://github.com/Org/Project111
  DEBUG   2019-02-25 16:13:35.434313900 +11:00   Looking for reference URL https://github.com/Org/Project111
  DEBUG   2019-02-25 16:13:35.436314 +11:00   not a match: [email protected]:Org/Project2222.git != https://github.com/Org/Project111
  INFO    2019-02-25 16:13:35.457318800 +11:00   -> no matching revision found
  INFO    2019-02-25 16:13:35.462323700 +11:00 Resolving HEAD (Org/Project2222@HEAD)
  DEBUG   2019-02-25 16:13:35.464315600 +11:00   Got reference URL for repo Org/Project2222: https://github.com/Org/Project2222
  DEBUG   2019-02-25 16:13:35.464315600 +11:00   Looking for reference URL https://github.com/Org/Project2222
  DEBUG   2019-02-25 16:13:35.466316700 +11:00   not a match: [email protected]:Org/Project2222.git != https://github.com/Org/Project2222
  INFO    2019-02-25 16:13:35.488314200 +11:00   -> no matching revision found
  DEBUG   2019-02-25 16:13:35.493327900 +11:00 error: running update nagger
  INFO    2019-02-25 16:13:35.495325800 +11:00 Skipping update nagger update check
error: Could not determine any commits to be associated automatically.
Please provide commits explicitly using --commit | -c.

HINT: Did you add the repo to your organization?
Configure it at https://sentry.io/settings/orgdotcom/repos/
  DEBUG   2019-02-25 16:13:35.501472900 +11:00 client close; no transport to shut down  (from sentry)

Check version:

$ sentry-cli.exe --version
sentry-cli 1.39.1

What you expected to happen

The https should match SSH url.

[imranity]

getting same error

[imranity]

ok i got it working by adding a workaround

sed -ie "s|url =.*|url = https://github.com/myrepo/$CI_PROJECT_NAME|g" .git/config

where CI_PROJECT_NAME is the URL that is set for repository on Sentry.io .
basically the error you show happens git remote URL is different that URL which is set in Sentry.io(and that cannot be changed)

[fp-jcorriveau]

I had this kind of error, somehow an unknown repository has been introduced in Sentry/Settings/Repositories.
Sometimes the pipeline was targeting the good repo and sometimes the unknown repo, creating the error

[cathteng]

Is this still a issue for you?