|
||||||||
|
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.
My use case is that my Jenkins builds create tags like "J-<project>
<buildnumber>" and then I use as tag-filter "J", but using "" should work (just tested on my project).But maybe the explanation is not correct, as I did not consider the case of adding the git-parameter plug-in to an existing jenkins project.
Did you build once your project after adding the git parameter plugin? If not please build it once (it will use the default) and check whether your tags get listed now. If they do, I have to change the explanation, else it might be helpful if you could grep your jenkins log to check for any error and / or log entries like
May 26, 2014 11:24:25 AM net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition generateContents
INFO: generateContents contenttype PT_TAG RemoteConfig https://github.com/elexis/elexis-3-base/