-
Bug
-
Resolution: Unresolved
-
Blocker
-
None
-
Certification
Development
When I use the parameterized scheduler plugin for the first time, it causes a problem with any SCM plugin option you use (Git, Bitbucket Server, etc.) in that it breaks the ability to connect to the SCM (Bitbucket) using working credentials (as verified in other jobs without the use of the parameterized scheduler plugin). These builds were working fine when using the normal built-in scheduler prior to the switch to parameterized scheduler plugin.
We would like to expand the use of the parameterized scheduler for our builds, but this is a blocker issue for us.
Here's an example of the error (some content sanitized due to sensitivity:
ERROR: Error fetching remote repo 'xxxxxxxxxxxx' hudson.plugins.git.GitException: Failed to fetch from
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:999) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1241) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1305) at com.atlassian.bitbucket.jenkins.internal.scm.BitbucketSCM.checkout(BitbucketSCM.java:187) at hudson.scm.SCM.checkout(SCM.java:540) at hudson.model.AbstractProject.checkout(AbstractProject.java:1248) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:649) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:85) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:521) at hudson.model.Run.execute(Run.java:1895) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:44) at hudson.model.ResourceController.execute(ResourceController.java:101) at hudson.model.Executor.run(Executor.java:442) Caused by: hudson.plugins.git.GitException: Command "/app/git-2.23.0/bin/git fetch --tags --force --progress –
+refs/heads/:refs/remotes/xxxxxxxxx/" returned status code 128: stdout: stderr: /app/.jenkins/workspace/xxxxxxx/xxxxxxxxxxx/xxxxxxxxxxxxxxx/test@tmp/jenkins-gitclient-pass5898312028109201059.sh: line 3: cat: command not found error: unable to read askpass response from '/app/.jenkins/workspace/xxxxxxx/xxxxxxxxxxxxx/test@tmp/jenkins-gitclient-pass5898312028109201059.sh' fatal: could not read Username for '
https://xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
If we turn off the parameterized scheduler plugin within the same job and revert it back to the normal scheduler, the same error persists and appears to have irreversibly damaged the build. We have to recreate the build from scratch with the normal scheduler in order to restore it.
This is on the following:
Jenkins version: 2.426.2
Parameterized Scheduler Plugin ver: 262.v00f3d90585cc