Let’s fix the Jenkins Error fetching remote repo ‘origin’ in this article. Bobcares, as a part of our Server Management Service offers solutions to every query that comes our way.

Fixing Jenkins Error Fetching Remote Repo ‘Origin’

Sometimes we may experience this error due to poor connectivity as Jenkins, the software we’re using, has a rule that it stops trying to download something after 10 minutes. However, we can easily fix it in the following ways:

Fix 1

1. “Advanced clone behaviours” is an option that appears when we tap the “Add” button on the “Additional Behaviours” tab. Once we do, a list of settings will appear.

2. We should be good to go if we just add the duration of time that we feel comfortable with the internet connection based on the size of the repository.

3. Proceed to the Jenkins directory, which is typically located at C:\Jenkins\Workspace, where the Jenkins jobs are kept. Make a backup of the tasks there before deleting the original.

4. Please rerun the job; this should resolve the issue and prevent it from occurring in the future.

Fix 2

We can resolve any HTTP S details issues by trying this.

1. Instead, use the SSH URL.

2. Make use of the Jenkins SSH login plugin. We may keep the SSH credentials in Jenkins by using this plugin.

Fix 3

Most likely, Jenkins’s config for git is incorrect. Take a look at that once.

1. Access Manage Jenkins.

2. Select Global Tool Config.

3. In the Git / Path to Git executable field, type C:\\git.exe.

4. Select “Save” by clicking.

[Need to know more? We’re available 24/7.]

Conclusion

To sum up, our Tech team went over three ways in which we can fix the Jenkins Error fetching remote repo ‘origin’.