[JIRA] [git-plugin] (JENKINS-26314) Using a Tag in Branch Specifier causes the polling to not detect the head revision
Jan Klass commented on JENKINS-26314 Using a Tag in Branch Specifier causes the polling to not detect the head revision Is this bug the cause for the following issue? Through defining the refspec we fetch tags into the local branches directory, so we can build any release tags with a branch-wildcard-trigger. Occasionaly, a tag will be built again. It seems to only be the second most recent one though, when the most recent one is built after a notify-trigger. 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-plugin] (JENKINS-26314) Using a Tag in Branch Specifier causes the polling to not detect the head revision
Mark Waite commented on JENKINS-26314 Using a Tag in Branch Specifier causes the polling to not detect the head revision Nathan Smith it is still a bug. 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-plugin] (JENKINS-26314) Using a Tag in Branch Specifier causes the polling to not detect the head revision
Nathan Smith commented on JENKINS-26314 Using a Tag in Branch Specifier causes the polling to not detect the head revision Enabling 'force polling using workspace' does seem to workaround the issue thanks. Do you agree that this should still be considered a bug since some plugin users would encounter still encounter JENKINS-10131? 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-plugin] (JENKINS-26314) Using a Tag in Branch Specifier causes the polling to not detect the head revision
Mark Waite commented on JENKINS-26314 Using a Tag in Branch Specifier causes the polling to not detect the head revision If you force polling to use a workspace, does it resolve the problem? 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-plugin] (JENKINS-26314) Using a Tag in Branch Specifier causes the polling to not detect the head revision
Nathan Smith created JENKINS-26314 Using a Tag in Branch Specifier causes the polling to not detect the head revision Issue Type: Bug Assignee: Nicolas De Loof Components: git-plugin Created: 07/Jan/15 1:43 AM Description: Use a Tag in the Branch Specifier. Polling on the remote repo will occur. It will run git ls-remote -h MY_REMOTE MY_TAG This will result in nothing returned from the remote repository. git ls-remote has a --tags option which will return the SHA of the Tag. Polling is enabled because the Job also checkouts an SVN repository using the Jenkins Multiple SCMs plugin which doesn't refer to a tag. Environment: Jenkins 1.584 Jenkins Git Plugin 2.3.1 Jenkins Multiple SCMs plugin 0.3 Project: Jenkins Priority: Major Reporter: Nathan Smith 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.