[JIRA] (JENKINS-17195) InvalidTagNameException with version 1.0.4 of git client
Mark Waite commented on JENKINS-17195 InvalidTagNameException with version 1.0.4 of git client Since git-client-plugin 1.0.5 reverted to using the git CLI instead of using JGit as its default, I think this bug is fixed by git-client-plugin 1.0.5. Can you check that the issue is resolved by installing git-client-plugin 1.0.5? 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-17195) InvalidTagNameException with version 1.0.4 of git client
Matt Williamson commented on JENKINS-17195 InvalidTagNameException with version 1.0.4 of git client I'm running "Jenkins GIT client plugin" 1.0.4, but it doesn't show any updates available. 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-17195) InvalidTagNameException with version 1.0.4 of git client
Mark Waite commented on JENKINS-17195 InvalidTagNameException with version 1.0.4 of git client Go to the "Advanced" tab in the "Manage Plugins" section and you'll see an "Update Now" button in the bottom right corner. Above that "Update Now" button it will show the last time it polled for updates. If you press the "Update Now", it will poll immediately, and should then show the 1.0.5 plugin is available. 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-17195) InvalidTagNameException with version 1.0.4 of git client
Matt Williamson commented on JENKINS-17195 InvalidTagNameException with version 1.0.4 of git client Great, looks like that fixed all our issues! For others... Manage Jenkins - Manage Plugins - Advanced Tab - Check now button (bottom right corner) Manage Jenkins - Manage Plugins - Updates Tab - Install all (specifically Jenkins GIT Client Plugin 1.0.5) Thank you!! 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-17195) InvalidTagNameException with version 1.0.4 of git client
Mark Waite resolved JENKINS-17195 as Fixed InvalidTagNameException with version 1.0.4 of git client git-client-plugin 1.0.5 resolved this by switching back to the CLI as the default git implementation. Change By: Mark Waite (22/Mar/13 6:10 PM) Status: Reopened Resolved 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-17195) InvalidTagNameException with version 1.0.4 of git client
Matt Williamson commented on JENKINS-17195 InvalidTagNameException with version 1.0.4 of git client This is a major issue for us as well. Selecting "Skip Internal Tag" doesn't work for us either, the post-build still fails with InvalidTagNameException when the branch is supposed to be merged into master. Sounds like the issue has been identified and fixed, but how will we know when the update will be available through yum? 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-17195) InvalidTagNameException with version 1.0.4 of git client
Jeff Fairchild updated JENKINS-17195 InvalidTagNameException with version 1.0.4 of git client Change By: Jeff Fairchild (21/Mar/13 3:40 PM) Priority: Major Blocker 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-17195) InvalidTagNameException with version 1.0.4 of git client
David Tanner commented on JENKINS-17195 InvalidTagNameException with version 1.0.4 of git client Also found the issue in one other location inside GitPublisher. Submitted pull request. https://github.com/jenkinsci/git-plugin/pull/142 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-17195) InvalidTagNameException with version 1.0.4 of git client
David Tanner reopened JENKINS-17195 InvalidTagNameException with version 1.0.4 of git client GitTagAction wasn't the culprit if you look at the stack trace. The error was created by line 1090 in GitSCM. Please pull my request, or fix that line and build 1.0.5 ASAP. Change By: David Tanner (20/Mar/13 1:43 PM) Resolution: Fixed Status: Resolved Reopened 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-17195) InvalidTagNameException with version 1.0.4 of git client
SCM/JIRA link daemon commented on JENKINS-17195 InvalidTagNameException with version 1.0.4 of git client Code changed in jenkins User: Nicolas De loof Path: src/main/java/hudson/plugins/git/GitSCM.java http://jenkins-ci.org/commit/git-plugin/68eea05dccac95bede80bdbe0ff558ac767b207f Log: Merge pull request #141 from dlvenable/whitespace-fix Replace whitespace with underscore - JENKINS-17195 Compare: https://github.com/jenkinsci/git-plugin/compare/b0a6db04e3af...68eea05dccac You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. 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-17195) InvalidTagNameException with version 1.0.4 of git client
David Venable commented on JENKINS-17195 InvalidTagNameException with version 1.0.4 of git client This does not fix this issue on my server. The following commit has fixed the issue on my server. https://github.com/dlvenable/git-plugin/commit/d5af3de2657de6b94bb810c7f69cd19720497911 I can create a pull request if you'd like. 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-17195) InvalidTagNameException with version 1.0.4 of git client
David Venable edited a comment on JENKINS-17195 InvalidTagNameException with version 1.0.4 of git client The previous commit does not fix this issue on my server. The following commit has fixed the issue on my server. https://github.com/dlvenable/git-plugin/commit/d5af3de2657de6b94bb810c7f69cd19720497911 I can create a pull request if you'd like. 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-17195) InvalidTagNameException with version 1.0.4 of git client
Christoph B commented on JENKINS-17195 InvalidTagNameException with version 1.0.4 of git client This is pretty severe to me. Our complete build system stopped running because all of our 250 projects are prefixed by a text and followed by a space. Please repair this. 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-17195) InvalidTagNameException with version 1.0.4 of git client
Christian Lipphardt commented on JENKINS-17195 InvalidTagNameException with version 1.0.4 of git client Same here. Please fix it! 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-17195) InvalidTagNameException with version 1.0.4 of git client
Christian Lipphardt edited a comment on JENKINS-17195 InvalidTagNameException with version 1.0.4 of git client Same here. Please fix it! (We can live with the fix to disable the internal tag for the moment tho) 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-17195) InvalidTagNameException with version 1.0.4 of git client
Christoph B commented on JENKINS-17195 InvalidTagNameException with version 1.0.4 of git client I'm not going to disable the internal tagging temporarily by changing the configuration of 250 projects 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-17195) InvalidTagNameException with version 1.0.4 of git client
SCM/JIRA link daemon commented on JENKINS-17195 InvalidTagNameException with version 1.0.4 of git client Code changed in jenkins User: Nicolas De Loof Path: src/main/java/hudson/plugins/git/GitTagAction.java http://jenkins-ci.org/commit/git-plugin/b0a6db04e3afa05ec054757e076090e51be91755 Log: FIXED JENKINS-17195 avoid whitespace in tag name (enforced by JGit) Compare: https://github.com/jenkinsci/git-plugin/compare/8fb5de484064...b0a6db04e3af You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. 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-17195) InvalidTagNameException with version 1.0.4 of git client
SCM/JIRA link daemon resolved JENKINS-17195 as Fixed InvalidTagNameException with version 1.0.4 of git client Change By: SCM/JIRA link daemon (14/Mar/13 4:49 PM) Status: Open Resolved 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-17195) InvalidTagNameException with version 1.0.4 of git client
Edward Hartwell Goose created JENKINS-17195 InvalidTagNameException with version 1.0.4 of git client Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 13/Mar/13 2:12 PM Description: I just upgraded our git-client-plugin from 1.0.2 to 1.0.4 and now get an InvalidTagNameException. We were running Jenkins 1.505. The exception implies I've created a tag, which I certainly haven't, so I'm not sure how the issue is occurring. I'm assuming the issue is because the tag it believes it is receiving contains spaces. Here's the stacktrace: Using strategy: Default Last Built Revision: Revision b6db3c79b4f208e6989e4f10f00f564d189b7590 (origin/develop) Fetching changes from 1 remote Git repository Commencing build of Revision 8862b04b711a283d4e53962cc60e9b4203807d3a (origin/develop) Checking out Revision 8862b04b711a283d4e53962cc60e9b4203807d3a (origin/develop) FATAL: org.eclipse.jgit.api.errors.InvalidTagNameException: tag name jenkins-WOW - Dev-872 is invalid hudson.plugins.git.GitException: org.eclipse.jgit.api.errors.InvalidTagNameException: tag name jenkins-WOW - Dev-872 is invalid at org.jenkinsci.plugins.gitclient.JGitAPIImpl.tag(JGitAPIImpl.java:179) at hudson.plugins.git.GitAPI.tag(GitAPI.java:220) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1239) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1196) at hudson.FilePath.act(FilePath.java:865) at hudson.FilePath.act(FilePath.java:838) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1196) at hudson.model.AbstractProject.checkout(AbstractProject.java:1353) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:683) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:588) at hudson.model.Run.execute(Run.java:1567) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Caused by: org.eclipse.jgit.api.errors.InvalidTagNameException: tag name jenkins-WOW - Dev-872 is invalid at org.eclipse.jgit.api.TagCommand.processOptions(TagCommand.java:198) at org.eclipse.jgit.api.TagCommand.call(TagCommand.java:112) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.tag(JGitAPIImpl.java:175) ... 14 more Project: Jenkins Labels: plugin exception Priority: Major Reporter: Edward Hartwell Goose 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.
