stderr: fatal: Couldn't find remote ref $GERRIT_REFSPEC
Before anyone guns me down..I have looked at all the messages that has this error but they seem to manifest from a different problem,I couldn’t get any substantial information. Following are the errors I’m running into in the git polling log…
I don’t have a clue regarding error #1,please provide inputs
- Continuous integration and continuous delivery with git-flow
- Downstream Jenkins project gets wrong upstream run parameter
- TFS 2008/2010 vs Jenkins for Continuous Integration
- How to trigger Jenkins builds remotely and to pass parameters
- Git Plugin parameter for branch and repository urls?
- How to get SHA of commit for Xcode Bot “Run Script” Trigger? Updating status of tests on Github
For this,I read on other questions that $GERRIT_REFSPEC gets filled in dynamically when there is a gerrit trigger but i don’t understand why I keep seeing this in the git poll log. How can I fix this ?
ERROR: Problem fetching from origin / origin – could be unavailable. Continuing anyway
hudson.plugins.git.GitException: Command “/usr/bin/git fetch -t ssh://company.com:29418/platform/vendor/proprietary/mla.git $GERRIT_REFSPEC” returned status code 128:
stderr: fatal: Couldn’t find remote ref $GERRIT_REFSPEC
4 Solutions collect form web for “stderr: fatal: Couldn't find remote ref $GERRIT_REFSPEC”
- Go to the Job’s Configure page and search to check This build is parameterized box.
- Then set Name to GERRIT_REFSPEC
- and Default value to refs/heads/master.
It took me some time to search for how to add this string parameter mentioned in the Gerrit Trigger plugin manual. I use Jenkins 1.567 with Gerrit Trigger 2.11.1.
As of May 2016, this error may be result of fix for SECURITY-170 introduced in Jenkins 2.3 or 1.651.2.
In a May 2016 security advisory, a vulnerability was announced (SECURITY-170 / CVE-2016-3721) whereby attackers could potentially exploit the fact that certain Jenkins plugins allow the definition of arbitrary build parameters — which are in turn injected into the build envirionment.
The fix for this issue — which was first included in Jenkins versions 1.651.2 and Jenkins 2.3 — means that only build parameters that have been explicitly defined in a job’s configuration will be available by default at build time. Any other arbitrary parameters added to a build by plugins will not be available by default.
As there are a number of plugins that rely on the behaviour in older Jenkins versions, upgrading to 1.651.2 or 2.3 means that certain build behaviours may be broken.
One of the affected plugins is the Gerrit Trigger. The issue you should watch for updates is here.
However, please note that the Rado’s solution to definine the
GERRIT_REFSPEC parameter manually in build config can solve this problem temporarily if you build only one branch from Gerrit.
A workaround is available by adding the following JAVA_ARGS to /etc/default/jenkins on ubuntu
You could also add which variables should be allowed
Looks like you ran a Jenkins Gerrit Trigger build manually? The trigger page says,
Using "Build Now" [..] Add a String parameter called GERRIT_REFSPEC with the default value refs/heads/master
After solving this issue if Jenkins is still not pulling the latest code commit(un-merged) then, need to Add Additional Behaviours -> Strategy for choosing what to build -> Gerrit Trigger
Reference: Thanks to Fabian