nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Checking out a Git project does something strange

Bjorn Harvold

Hi,

I am trying to integrate Sentry CLI into my CI/CD workflow.

Once everything builds, I send artifacts to Sentry. Sentry will look at the Git log to see what changed since last release.

The problem is, Sentry complains because it cannot match the remote Git repo. When i run git remote -v inside the plan folder, it shows me a local file directory instead of my remote hosted repo on Bitbucket.

So Sentry complains with:

DEBUG   2019-03-15 16:52:01.492404779 +07:00   not a match: file:///media/user/external/bamboo/xml-data/build-dir/_git-repositories-cache/debbfac5447105f03d2e672cc6b40afd775f0a46 != https://bitbucket.org/uberdevelopment/uber-spa

Accepted answers

Daniel Santos_157bm4

Hi @Bjorn Harvold

This is indeed expected behavior.

Bamboo does use cache repositories for better scalability. Multiple plans can use the same repository, therefore, saving network bandwidth. There are other reasons for this that I would not be the better person to explain.

In the repository advanced configuration, you will see that we can disable caching on remote agents, but this will still not solve your issue. The Bamboo server will still have the cache.

There are some articles written to provide alternatives for users trying to commit and push during a build. You will be able to see in those articles that the remote URL is manually configured:

What I suggest as a workaround for you is manually configuring the remote repository as performed on those articles.

All comments

Daniel Santos_157bm4

Hi @Bjorn Harvold

This is indeed expected behavior.

In the repository advanced configuration, you will see that we can disable caching on remote agents, but this will still not solve your issue. The Bamboo server will still have the cache.

There are some articles written to provide alternatives for users trying to commit and push during a build. You will be able to see in those articles that the remote URL is manually configured:

What I suggest as a workaround for you is manually configuring the remote repository as performed on those articles.

Bjorn Harvold

Hi Daniel,

Thank you for your feedback.

Specifically for my purposes, you are suggesting that I add a remote like so:

<span>git</span> remote add central https://username:<span>${bamboo_bitbucket_password}</span>@bitbucket.org/path/to/reponame.git

Sentry is failing when it tries to verify that the repo is indeed the repo at origin. Will adding another remote fix that?

Cheers

Daniel Santos_157bm4

I don't really know Sentry, what I know is that Sentry seems to expect the local repository to be pointing to the main repository directly. If this is the case, setting the remote should fix the issue or at least move you forward.

Let's give it a try and check what happens.

Bjorn Harvold

Hi Daniel,

I added a remote as I wrote above. It shows up as central, above origin, when I do a "git remote -v".

central https://<hidden>:<hidden>@bitbucket.org/uberdevelopment/uber-spa (fetch)
central https://<hidden>:<hidden>@bitbucket.org/uberdevelopment/uber-spa (push)
origin file:///media/user/external/bamboo/xml-data/build-dir/_git-repositories-cache/c0db605baf9e80f875cbed09008f36a37fe6f6f2 (fetch)
origin file:///media/user/external/bamboo/xml-data/build-dir/_git-repositories-cache/c0db605baf9e80f875cbed09008f36a37fe6f6f2 (push)

But it is not being picked up by Sentry. Sentry logs are still only comparing origin entry.