Pipeline WinRunner push issue

[Martin Nicolaides]

The setup runs-on self.hosted and windows.

The pipeline performs a build and also an add | commit | push.

This had been working properly for months, but over this past weekend the machine that hosts the pipeline was restarted.
Now, the pipeline build is still successful, but the add | commit | push fail with the following message:

git commit -m "Committing new build version number."; git push origin $Env:BITBUCKET_BRANCH}
[Develop 2054236] Committing new build version number.
1 file changed, 1 insertion(+), 1 deletion(-)
remote: The requested repository either does not exist or you do not have access. If you believe this repository exists and you have access, make sure you're authenticated.
fatal: unable to access 'https://bitbucket.org/[repo-owner]/[repo-slug]/': The requested URL returned error: 403

I can guess from the https an authenticated user is required. Is this the case?

[Syahrul]

Hey @Martin Nicolaides 

G'day.

I suggest adding the following verbose commands to get a better idea of the issue:

GIT_TRACE_PACKET=1 GIT_TRACE=1 GIT_CURL_VERBOSE=1 <git command_here>

Look for the authentication and if it's using the correct user/username to authenticate.

If not, you may want to check our guide. Push back to your repository and add the git remote set-url using the correct username and App Password to push back.

- git remote set-url origin https://<your username>:${APP_SECRET}@bitbucket.org/${BITBUCKET_REPO_OWNER}/${BITBUCKET_REPO_SLUG}
- git push origin

Cheers,
Syahrul