[JIRA] [git-parameter-plugin] (JENKINS-24544) GIT revision's list empty while GIT tag's list populated correctly
Title: Message Title Mark Waite commented on JENKINS-24544 Re: GIT revision's list empty while GIT tag's list populated correctly The "master is ambiguous" message likely means that you need to ask for the rev-list with the name of the origin in the request. Instead of "rev-list my-project", I think you want "rev-list origin/my-project" where "origin" is determined from the name of the remote specified by the user. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-24544) GIT revision's list empty while GIT tag's list populated correctly
Title: Message Title Boguslaw Klimas assigned an issue to Boguslaw Klimas Jenkins / JENKINS-24544 GIT revision's list empty while GIT tag's list populated correctly Change By: Boguslaw Klimas Assignee: Boguslaw Klimas Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-24544) GIT revision's list empty while GIT tag's list populated correctly
russ k commented on JENKINS-24544 GIT revisions list empty while GIT tags list populated correctly Can you try whether upgrading to 0.4.0 solves your problem or not? I upgraded and it still gives the same error. Otherwise would it be possible give the URL where your experience this problem. This is a private intranet site so giving access is not possible, sorry! Or you could checkout the git-parameter plugin, add lines like I see the plugin crashing at `generateContents(GitParameterDefinition.java:333)` so those debugging lines would never be called. I get an error: Caused by: hudson.plugins.git.GitException: Command "git rev-list my-project" returned status code 128: stdout: stderr: fatal: ambiguous argument 'my-project': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git command revision... file...' When I go to my projects git folder and run the same command I get the exact same error. However running --all works: my-project$ git rev-list --all 6e70eaabb2fe1d087158013ec0802ec4b4841d88 b59ea24a5bac309ad20c8853385f022857cc2da0 dc704b7aab8c707a78d972bbcf2b5eee43d58b0a 17d90081f96155946ed32dc9329aded72b900167 b98aa3a1a3e2831e48a5889d47e6cd9b49684d06 b7ef4dff66c390dc4f0047af8d240b782210f80a my-project$ git rev-list my-project fatal: ambiguous argument 'my-project': unknown revision or path not in the working tree. Now the git functionality is included by the gitclient plugin. I hesitate to touch that plugin as many others use it as well. 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/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-24544) GIT revision's list empty while GIT tag's list populated correctly
russ k edited a comment on JENKINS-24544 GIT revisions list empty while GIT tags list populated correctly Can you try whether upgrading to 0.4.0 solves your problem or not? I upgraded and it still gives the same error. Otherwise would it be possible give the URL where your experience this problem. This is a private intranet site so giving access is not possible, sorry! Or you could checkout the git-parameter plugin, add lines like I see the plugin crashing at `generateContents(GitParameterDefinition.java:333)` so those debugging lines would never be called. I get an error: Caused by: hudson.plugins.git.GitException: Command "git rev-list my-project" returned status code 128: stdout: stderr: fatal: ambiguous argument 'my-project': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git command revision... file...' When I go to my projects git folder and run the same command I get the exact same error. However running --all works: my-project$ git rev-list --all 6e70eaabb2fe1d087158013ec0802ec4b4841d88 b59ea24a5bac309ad20c8853385f022857cc2da0 dc704b7aab8c707a78d972bbcf2b5eee43d58b0a 17d90081f96155946ed32dc9329aded72b900167 b98aa3a1a3e2831e48a5889d47e6cd9b49684d06 b7ef4dff66c390dc4f0047af8d240b782210f80a my-project$ git rev-list my-project fatal: ambiguous argument 'my-project': unknown revision or path not in the working tree. Now the git functionality is included by the gitclient plugin. I hesitate to touch that plugin as many other plugins use it as well. 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/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-24544) GIT revision's list empty while GIT tag's list populated correctly
ngiger commented on JENKINS-24544 GIT revisions list empty while GIT tags list populated correctly Can you try whether upgrading to 0.4.0 solves your problem or not? Otherwise would it be possible give the URL where your experience this problem. I suspect that we have a weird git commit with a comment that causes havoc. Or you could checkout the git-parameter plugin, add lines like LOGGER.log(Level.INFO, "generateContents add SHA1 " + r.getSha1String()); LOGGER.log(Level.INFO, "generateContents add prettyRevisionInfo " + r.prettyRevisionInfo(newgit, r)); before the calls to paramList.put. Then call mvn clean install to build the plugin. And test it by adding the target/git-parameter.hpi via http://jenkins-url/pluginManager/advanced. The output of the jenkins log should then more details. 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/d/optout.
