We have 2 Jenkins servers with the same configuration, plugins, and GH PAT credentials, and they are executing different jobs from a long time ago.
We plan to use both of them to balance the workload of new jobs, as we must connect to two different GH repositories in the same GH Enterprise org.
We also have the same two new jobs, one per repository, in both servers, and they are working fine in one of the servers, but the other is returning the following for both jobs:
Caused by: hudson.plugins.git.GitException: Command âgit.exe fetch --tags --force --progress â XXXXXXX ¡ GitHub +refs/heads/:refs/remotes/origin/â returned status code 128:
stdout:
stderr: remote: Repository not found.
fatal: repository âXXXXXXX ¡ GitHubâ not found
ERROR: Error fetching remote repo âoriginâ
ERROR: Maximum checkout retry attempts reached, aborting
We can reach the repository from that server through the browser, so it is reachable and there is no connectivity issue.
So it seems some Jenkins issue, but we reviewed everything several times and looks fine.
The only differences we can see between both servers are:
- We can find in the logs that the server that is working fine is cloning the repository right after the line that is showing the credentials in use, but the server that is not working is fetching changes and upstream changes instead, even when both jobs have exactly the same code.
- The Jenkins server that is working fine has the local repository created, as we started to develop jobs and test everything there long time ago, but the new server which is having issues never doesn´t have it. I believe it shouldn´t be an issue, as it should be created when the job is executed.
Any idea about what could be the cause of not reaching the repository?
Thanks in advance.