-
Bug
-
Resolution: Not A Defect
-
Major
-
None
Upgraded a bunch of plugins today. A job that uses the github branch source for scm started failing. From comparing build history from the new and the old builds the old one ran
git fetch --tags --progress <REDACTED> +refs/heads/:refs/remotes/origin/
git fetch --no-tags --progress <REDACTED> +refs/heads/BRANCH:refs/remotes/origin/BRANCH
We have no "behaviors" specified under the GitHub branches source. Seems like the "no tags" and "ref spec" settings changed- was this intended?
For context, our failure ocurred because we have a shell script that runs `git rev-parse origin/master` in our build. We were able to get our build passing again by adding `+refs/heads/:refs/remotes/@{remote}/` to the Specify ref specs under Additional behaviors.