• Type: Bug
• Resolution: Not A Defect
• Priority: Minor
• Component/s: git-client-plugin, git-plugin
• Labels:

  • git-client
• Environment:

  Hide

  Jenkins 2.11
  Containerized Master Docker Version 1.11.1
  Backed by EFS
  Running on Amazon Linux ami aws-elasticbeanstalk-amzn-2016.03.2.x86_64-ecs-hvm-201606260408
  On demand EC2 agents using the same AMI
  
  Git client version :1.21.0
  Git version: 2.5.3

  Show

  Jenkins 2.11 Containerized Master Docker Version 1.11.1 Backed by EFS Running on Amazon Linux ami aws-elasticbeanstalk-amzn-2016.03.2.x86_64-ecs-hvm-201606260408 On demand EC2 agents using the same AMI Git client version :1.21.0 Git version: 2.5.3

1. jenkins error.log

   2 kB

   2016-08-24 13:38

[JENKINS-37653] Git fetch fails. Returns "Reference directory conflict: refs/heads/" with status code 128

Emmanuel Esparza created issue - 2016-08-24 13:39

Emmanuel Esparza made changes - 2016-08-24 13:55

Environment

Original: Jenkins 2.11 Containerized Master Docker Version 1.11.1 Backed by EFS Running on Amazon Linux ami aws-elasticbeanstalk-amzn-2016.03.2.x86_64-ecs-hvm-201606260408 On demand EC2 agents using the same AMI

New: Jenkins 2.11 Containerized Master Docker Version 1.11.1 Backed by EFS Running on Amazon Linux ami aws-elasticbeanstalk-amzn-2016.03.2.x86_64-ecs-hvm-201606260408 On demand EC2 agents using the same AMI Git client version :

Emmanuel Esparza made changes - 2016-08-24 13:57

Environment

Original: Jenkins 2.11 Containerized Master Docker Version 1.11.1 Backed by EFS Running on Amazon Linux ami aws-elasticbeanstalk-amzn-2016.03.2.x86_64-ecs-hvm-201606260408 On demand EC2 agents using the same AMI Git client version :

New: Jenkins 2.11 Containerized Master Docker Version 1.11.1 Backed by EFS Running on Amazon Linux ami aws-elasticbeanstalk-amzn-2016.03.2.x86_64-ecs-hvm-201606260408 On demand EC2 agents using the same AMI Git client version :1.21.0 Git version: 2.5.3

Mark Waite made changes - 2016-08-24 14:09

Description

Original: I am noticing that the command bellow fails  git -c core.askpass=true fetch --tags --progress https://github.com/myproject.git +refs/heads/*:refs/remotes/origin/* While tracing through the error log, I see that it fails to fetch the repo and then returns a status code of 128. What makes this very confusing is that is prints this out as the reason stderr: fatal: Reference directory conflict: refs/heads/

New: I am noticing that the command bellow fails {{ git -c core.askpass=true fetch --tags --progress https://github.com/myproject.git +refs/heads/*:refs/remotes/origin/*}} While tracing through the error log, I see that it fails to fetch the repo and then returns a status code of 128. What makes this very confusing is that is prints this out as the reason stderr: fatal: Reference directory conflict: refs/heads/

Mark Waite made changes - 2016-08-24 14:09

Description

Original: I am noticing that the command bellow fails {{ git -c core.askpass=true fetch --tags --progress https://github.com/myproject.git +refs/heads/*:refs/remotes/origin/*}} While tracing through the error log, I see that it fails to fetch the repo and then returns a status code of 128. What makes this very confusing is that is prints this out as the reason stderr: fatal: Reference directory conflict: refs/heads/

New: I am noticing that the command bellow fails {{ git -c core.askpass=true fetch --tags --progress https://github.com/myproject.git +refs/heads/*:refs/remotes/origin/* }} While tracing through the error log, I see that it fails to fetch the repo and then returns a status code of 128. What makes this very confusing is that is prints this out as the reason stderr: fatal: Reference directory conflict: refs/heads/

Mark Waite made changes - 2016-08-24 14:09

Description

Original: I am noticing that the command bellow fails {{ git -c core.askpass=true fetch --tags --progress https://github.com/myproject.git +refs/heads/*:refs/remotes/origin/* }} While tracing through the error log, I see that it fails to fetch the repo and then returns a status code of 128. What makes this very confusing is that is prints this out as the reason stderr: fatal: Reference directory conflict: refs/heads/

New: I am noticing that the command bellow fails {code} git -c core.askpass=true fetch --tags --progress https://github.com/myproject.git +refs/heads/*:refs/remotes/origin/* {code} While tracing through the error log, I see that it fails to fetch the repo and then returns a status code of 128. What makes this very confusing is that is prints this out as the reason stderr: fatal: Reference directory conflict: refs/heads/

Mark Waite made changes - 2016-08-24 14:10

Assignee

Original: Mark Waite [ markewaite ]

Mark Waite made changes - 2016-08-24 20:49

Resolution		New: Not A Defect [ 7 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

Mark Waite made changes - 2019-10-23 01:28

Status

Original: Resolved [ 5 ]

New: Closed [ 6 ]