|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
Patrick Hemmer I don't see this result on any of my 100+ jobs, on multiple machines.
I use many combinations of authentication (read only, read/write, ssh keys, username/password, etc.), transport (git, ssh, https) and servers (bitbucket, github, assembla, local git server). I'm not seeing a tag per build on any of my jobs, unless the "Additional Behaviours" has been enabled to "Create a tag for every build".
Is this happening on every job, including newly created jobs, or only on jobs which were defined prior to your upgrade to git plugin version 2 ?
Is "Create a tag for every build" enabled in the job configuration?
Is there anything else which might be unique or different about your configuration?