A job being started twice for the same commit might be an indication that the repository is using both notifyCommit and web hooks. It might be an indication that the repository is being polled in less time than the build requires to complete.

Please provide precise steps that will allow others to duplicate the problem you're reporting. Precise steps include:

• Type of Jenkins job with the config.xml of the job
• Type of SCM system used and whether the repository is public or private
• Type of status notification system configured for the repository (web hooks, notifyCommit, polling, etc.)
• Contents of a Jenkins support bundle from the support core plugin so that plugin versions are noted and Jenkins configuration is provided
• Numbered list of steps the user performs which will show the problem on a newly installed Jenkins

Hi Mark, 

We are using Jenkins Version 1.609.3, and please find the git plugin versions info in attached screen shot. Can you help me with the steps to proceed to resolve that issue

No, Anvesh Ramaswamy, I cannot help you with any steps to proceed to resolve the issue. I requested 5 items and you provided far less than 1 of the items I requested.

I help Jenkins users on my personal time. When you fail to provide all the information I request, it tells me that you're really not committed to receiving my help.

Since you're running a Jenkins version that is many years old and a git plugin that is many years old, you should expect to do significant work of your own before I or anyone else will be willing to assist.

The information you provide in the issue report needs to be sufficiently detailed that it persuades me that you are investing enough of your time to justify that I should invest some of my time. You've not shown that. I will not engage in a long series of questions and answers about the issue unless you persuade me that the issue is very interesting to me.

If you decide that it is not worth enough of your time to provide that information, then let's agree that we'll close this issue as "cannot reproduce".

Hi Mark, could you please help me in detail, what are the thing you require to investigate the issue. Kindly help me on this please

I listed the items you'll need to provide Anvesh Ramaswamy in my earlier comment. Based on the information you've provided since then, you'll also need to describe the following items:

• Numbered list of steps the user performs which will show the problem on a newly installed Jenkins (not provided yet)
• Type of Jenkins job with the config.xml of the job (not provided yet)
• Type of SCM system used and whether the repository is public or private (not provided yet)
• Type of status notification system configured for the repository (web hooks, notifyCommit, polling, etc.) (not provided yet)
• Contents of a Jenkins support bundle from the support core plugin so that plugin versions are noted and Jenkins configuration is provided (not provided yet, may not be possible with that ancient Jenkins version, then will need to provide the same information without using the support core plugin)
• Can you see the same problem on a current Jenkins version (2.222.1) with current plugins (git plugin 4.2.2, git client plugin 3.2.1) (not provided yet)

I won't investigate issues on Jenkins 1.6xx or on git plugin 2.x. Too old.