java.lang.IllegalArgumentException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • I understand that the git plugin is now using git-client? I can't get my upgraded Jenkins instance to clone a repository at all. I've tried adding -Dorg.jenkinsci.plugins.gitclient.Git.useCLI=true -Dhudson.util.ProcessTree.disable=true I've also tried setting environment variables (GIT_HOME and HOME) in Jenkins as per the details on this page. https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin I've set the tool location of Git (gitk.cmd) . GitInstallations no longer works (I assume because of the use of Git-Client now) Log output from job looks like this: Checkout:workspace / C:\Jenkins\jobs\Maintenance_CollectArtefactVersions\workspace - hudson.remoting.LocalChannel@2b498ab1 Using strategy: Default Cloning the remote Git repository Cloning repository ssh://git@server.com:7999/Repos/deployscripts.git git --version Process leaked file descriptors. See http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for more information Fetching upstream changes from origin FATAL: Invalid id: Process leaked file descriptors. See http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for more information java.lang.IllegalArgumentException: Invalid id: Process leaked file descriptors. See http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for more information at org.eclipse.jgit.lib.ObjectId.fromString(ObjectId.java:232) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.revParse(CliGitAPIImpl.java:264) at hudson.plugins.git.GitAPI.revParse(GitAPI.java:252) I'm still kind of assuming I'm doing something wrong now that git is using git-client, or need to remove something given how much use of Jenkins+Git I've had in the past (3+years on ~50 build servers).
    via by Brian Mills,
  • I understand that the git plugin is now using git-client? I can't get my upgraded Jenkins instance to clone a repository at all. I've tried adding -Dorg.jenkinsci.plugins.gitclient.Git.useCLI=true -Dhudson.util.ProcessTree.disable=true I've also tried setting environment variables (GIT_HOME and HOME) in Jenkins as per the details on this page. https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin I've set the tool location of Git (gitk.cmd) . GitInstallations no longer works (I assume because of the use of Git-Client now) Log output from job looks like this: Checkout:workspace / C:\Jenkins\jobs\Maintenance_CollectArtefactVersions\workspace - hudson.remoting.LocalChannel@2b498ab1 Using strategy: Default Cloning the remote Git repository Cloning repository ssh://git@server.com:7999/Repos/deployscripts.git git --version Process leaked file descriptors. See http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for more information Fetching upstream changes from origin FATAL: Invalid id: Process leaked file descriptors. See http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for more information java.lang.IllegalArgumentException: Invalid id: Process leaked file descriptors. See http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for more information at org.eclipse.jgit.lib.ObjectId.fromString(ObjectId.java:232) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.revParse(CliGitAPIImpl.java:264) at hudson.plugins.git.GitAPI.revParse(GitAPI.java:252) I'm still kind of assuming I'm doing something wrong now that git is using git-client, or need to remove something given how much use of Jenkins+Git I've had in the past (3+years on ~50 build servers).
    via by Brian Mills,
  • Jenkins Build Error using GitHub
    via Stack Overflow by user2414772
    ,
  • New Gitlab 7.10 error while serving
    via GitHub by bastianb
    ,
  • Using the git plugin to publish a merged change to a central repository previously was successful. With the 1.2.0 version of the git plugin it is no longer able to push changes to the central repository after they have merged and are successfully built. The stack trace reports: Commencing build of Revision 363396d76a09a12a2f4b5d94fb4e9981e05ad4a9 (origin/proposals) Merging Revision 363396d76a09a12a2f4b5d94fb4e9981e05ad4a9 (origin/proposals) onto master FATAL: Invalid id: origin/master java.lang.IllegalArgumentException: Invalid id: origin/master at org.eclipse.jgit.lib.ObjectId.fromString(ObjectId.java:232) at hudson.plugins.git.GitSCM.computeMergeChangeLog(GitSCM.java:1331) at hudson.plugins.git.GitSCM.access$1200(GitSCM.java:57) at hudson.plugins.git.GitSCM$3.invoke(GitSCM.java:1188) at hudson.plugins.git.GitSCM$3.invoke(GitSCM.java:1133) at hudson.FilePath.act(FilePath.java:852) at hudson.FilePath.act(FilePath.java:834) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1133) at hudson.model.AbstractProject.checkout(AbstractProject.java:1256) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:590) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:495) at hudson.model.Run.execute(Run.java:1502) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Steps to recreate the problem: - configure a Git repository into which the Jenkins user can push changes - create a "master" branch and a "proposals" branch on the Git repository - define a Jenkins job which clones the Git repository with ssh protocol - configure the Jenkins job git plugin to merge from */proposals and */master branches to the "master-proposals" branch - define a post build action to push the resulting merge to the origin/master branch - Submit a change to the central git repository on the "proposals" branch - Run the Jenkins job to confirm it will combine the master and proposals branches - Confirm the Jenkins job fails to push the combined change = IllegalArgumentException because JGit cannot convert "origin/master" into a SHA1, while the older git plugin ObjectId implementation seemed to make that conversion successfully. Refer to merge-proposals.xml for the job definition I used in my tests.
    via by Mark Waite,
    • java.lang.IllegalArgumentException: Invalid id: Process leaked file descriptors. See http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for more information at org.eclipse.jgit.lib.ObjectId.fromString(ObjectId.java:232) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.revParse(CliGitAPIImpl.java:264) at hudson.plugins.git.GitAPI.revParse(GitAPI.java:252)
    No Bugmate found.