java.lang.IllegalArgumentException: Invalid id: origin/master

Jenkins JIRA | Mark Waite | 4 years ago
  1. 0

    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.

    Jenkins JIRA | 4 years ago | Mark Waite
    java.lang.IllegalArgumentException: Invalid id: origin/master
  2. 0

    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.

    Jenkins JIRA | 4 years ago | Mark Waite
    java.lang.IllegalArgumentException: Invalid id: origin/master
  3. 0

    FATAL: Invalid id: Process leaked file descriptors - Jenkins (github)

    Stack Overflow | 3 years ago | Digeek
    java.lang.IllegalArgumentException: Invalid id: Process leaked file descriptors. See <a href="http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build" rel="nofollow">http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build</a> for more information
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Jenkins Build Error using GitHub

    Stack Overflow | 4 years ago | user2414772
    java.lang.IllegalArgumentException: Invalid id: Process leaked file descriptors. See [same wiki link] for more information
  6. 0

    Invalid id: Process leaked file descriptors. Jenkins

    Stack Overflow | 3 years ago | Achal Gupta
    java.lang.IllegalArgumentException: Invalid id: Process leaked file descriptors. See http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for more information

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.lang.IllegalArgumentException

      Invalid id: origin/master

      at org.eclipse.jgit.lib.ObjectId.fromString()
    2. JGit - Core
      ObjectId.fromString
      1. org.eclipse.jgit.lib.ObjectId.fromString(ObjectId.java:232)
      1 frame
    3. Hudson GIT plugin
      GitSCM$3.invoke
      1. hudson.plugins.git.GitSCM.computeMergeChangeLog(GitSCM.java:1331)
      2. hudson.plugins.git.GitSCM.access$1200(GitSCM.java:57)
      3. hudson.plugins.git.GitSCM$3.invoke(GitSCM.java:1188)
      4. hudson.plugins.git.GitSCM$3.invoke(GitSCM.java:1133)
      4 frames
    4. Hudson
      FilePath.act
      1. hudson.FilePath.act(FilePath.java:852)
      2. hudson.FilePath.act(FilePath.java:834)
      2 frames
    5. Hudson GIT plugin
      GitSCM.checkout
      1. hudson.plugins.git.GitSCM.checkout(GitSCM.java:1133)
      1 frame
    6. Hudson
      AbstractBuild$AbstractBuildExecution.defaultCheckout
      1. hudson.model.AbstractProject.checkout(AbstractProject.java:1256)
      2. hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:590)
      2 frames
    7. jenkins.scm
      SCMCheckoutStrategy.checkout
      1. jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
      1 frame
    8. Hudson
      Executor.run
      1. hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:495)
      2. hudson.model.Run.execute(Run.java:1502)
      3. hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
      4. hudson.model.ResourceController.execute(ResourceController.java:88)
      5. hudson.model.Executor.run(Executor.java:237)
      5 frames