[JIRA] (JENKINS-16940) Git publisher fails with Invalid id: origin/master when trying to publish changes
Mark Waite commented on JENKINS-16940 Git publisher fails with Invalid id: origin/master when trying to publish changes The git client plugin 1.4.0 reported the push but did not actually push enough information to the remote server so that others could use it. I have confirmed that the git client plugin 1.5.0 does push enough information for others to use the resulting push. The full fix of this bug requires git client plugin 1.5.0 and glit plugin 1.3.0. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16940) Git publisher fails with Invalid id: origin/master when trying to publish changes
Mark Waite resolved JENKINS-16940 as Fixed Git publisher fails with Invalid id: origin/master when trying to publish changes Seems to be resolved in Git plugin 1.3.0 and Git Client plugin 1.4.0. Unfortunately, that combination does not seem to push enough information to the destination repository in the post build action, so the Git publisher function still seems to be broken. Refer to https://groups.google.com/d/msg/jenkinsci-users/sVlEKgagwdg/CgRoyGE01xcJ for more information on the behavior of Git plugin 1.3.0 when pushing to a repository Change By: Mark Waite (14/Mar/13 9:31 AM) Status: Open Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16940) Git publisher fails with Invalid id: origin/master when trying to publish changes
Meng Xin Zhu commented on JENKINS-16940 Git publisher fails with Invalid id: origin/master when trying to publish changes +1 It's a regression bug, very annoying. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [JIRA] (JENKINS-16940) Git publisher fails with Invalid id: origin/master when trying to publish changes
This is blocking us as well. git --version git version 1.7.0.4 Fetching upstream changes from cloudforge Cleaning workspace Resetting working tree Commencing build of Revision bdcbf15cb22058e5fdbb0e12ffeb9db8a15cc394 (cloudforge/develop) Merging Revision bdcbf15cb22058e5fdbb0e12ffeb9db8a15cc394 (cloudforge/develop) onto master FATAL: Invalid id: cloudforge/master java.lang.IllegalArgumentException: Invalid id: cloudforge/master Please let me know if there is anything I can provide to help. -- View this message in context: http://jenkins.361315.n4.nabble.com/JIRA-JENKINS-16940-Git-publisher-fails-with-Invalid-id-origin-master-when-trying-to-publish-changes-tp4656853p4657102.html Sent from the Jenkins issues mailing list archive at Nabble.com. -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16940) Git publisher fails with Invalid id: origin/master when trying to publish changes
markewaite created JENKINS-16940 Git publisher fails with Invalid id: origin/master when trying to publish changes Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Attachments: merge-proposals.xml Components: git Created: 23/Feb/13 5:06 AM Description: 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" to "master-proposals" 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. Environment: Linux master server executing job on master server Project: Jenkins Priority: Major Reporter: markewaite This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16940) Git publisher fails with Invalid id: origin/master when trying to publish changes
markewaite commented on JENKINS-16940 Git publisher fails with Invalid id: origin/master when trying to publish changes Refer to https://issues.jenkins-ci.org/browse/JENKINS-16888 for a similar issue with a different symptom but likely the same root cause. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16940) Git publisher fails with Invalid id: origin/master when trying to publish changes
Mark Waite updated JENKINS-16940 Git publisher fails with Invalid id: origin/master when trying to publish changes Change By: Mark Waite (23/Feb/13 5:16 AM) Description: Usingthegitplugintopublishamergedchangetoacentralrepositorypreviouslywassuccessful.Withthe1.2.0versionofthegitpluginitisnolongerabletopushchangestothecentralrepositoryaftertheyhavemergedandaresuccessfullybuilt.Thestacktracereports:CommencingbuildofRevision363396d76a09a12a2f4b5d94fb4e9981e05ad4a9(origin/proposals)MergingRevision363396d76a09a12a2f4b5d94fb4e9981e05ad4a9(origin/proposals)ontomasterFATAL:Invalidid:origin/masterjava.lang.IllegalArgumentException:Invalidid:origin/master atorg.eclipse.jgit.lib.ObjectId.fromString(ObjectId.java:232) athudson.plugins.git.GitSCM.computeMergeChangeLog(GitSCM.java:1331) athudson.plugins.git.GitSCM.access$1200(GitSCM.java:57) athudson.plugins.git.GitSCM$3.invoke(GitSCM.java:1188) athudson.plugins.git.GitSCM$3.invoke(GitSCM.java:1133) athudson.FilePath.act(FilePath.java:852) athudson.FilePath.act(FilePath.java:834) athudson.plugins.git.GitSCM.checkout(GitSCM.java:1133) athudson.model.AbstractProject.checkout(AbstractProject.java:1256) athudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:590) atjenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:495) athudson.model.Run.execute(Run.java:1502) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) athudson.model.ResourceController.execute(ResourceController.java:88) athudson.model.Executor.run(Executor.java:237)Stepstorecreatetheproblem:-configureaGitrepositoryintowhichtheJenkinsusercanpushchanges-createamasterbranchandaproposalsbranchontheGitrepository-defineaJenkinsjobwhichclonestheGitrepositorywithsshprotocol-configuretheJenkinsjobgitplugintomergefrom */proposals and */master branches to the master-proposals branch -defineapostbuildactiontopushtheresultingmergetotheorigin/masterbranch-Submitachangetothecentralgitrepositoryontheproposalsbranch-RuntheJenkinsjobtoconfirmitwillcombinethemasterandproposalsbranches-ConfirmtheJenkinsjobfailstopushthecombinedchange=IllegalArgumentExceptionbecauseJGitcannotconvertorigin/masterintoaSHA1,whiletheoldergitpluginObjectIdimplementationseemedtomakethatconversionsuccessfully.Refertomerge-proposals.xmlforthejobdefinitionIusedinmytests. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
