anudeeplalam can you provide more details, including step by step instructions and specific examples so that others can duplicate the problem you are reporting?

For example, please provide the pipeline script you're using which is not honoring the retry count, a description of how you detect the failure when the retry count is not honored, a detailed description of how you configured the working freestyle job (or a copy of the job configuration file), and the types of failures which cause the job to retry.

markewaite - Thanks for your comment. Here is the scenario.

In Manage Jenkins -> Configure System, I have put the SCM checkout retry count to 5.

Now to test the retry, I have created a free style job to clone a Git repository https://github.com/anudeeplalam/JenkinsTest1.git , which does not exist.

When I build this job, As you can see in the below picture, The retry is happening.(The retry happened 5 times. To keep short I have captured single retry.)

Now, When I try to use this in a Pipeline Job for loading Jenkinsfile using "Pipeline script from scm", it's not working

As you can see in the below picture, The pipeline job exited immediately after the first attempt. Ideally it has to retry "5 Times" just like the Free style Job.

markewaite - Sorry for a very big message. But I thought it would be better to show all the steps I followed so that it will be easy for you to understand what went wrong.

So, now coming to the point. Am I missing something here. Ideally my expectation is SCM checkout retry count should work for both Freestyle and Pipeline Jobs.

This is really a blocker for us. We would really appreciate if someone look into this.

Thanks!

Thanks for the description. That's exactly what is needed.

I don't expect to investigate it further for at least several months due to other, more common use cases which need investigation and fixes. I wanted enough of a description in the bug report that others might be able to investigate if they encounter the same problem.

I don't know if the global SCM retry setting that you are using should be honored in pipeline jobs or not. I'm not sure which layer of the Jenkins code implements that retry mechanism. I suspect it is in some component outside the git plugin, since it mentions "SCM checkout retry count" rather than "Git retry count".