[JIRA] [git] (JENKINS-17898) Git plugin: tags triggers don't work as expected
Mark Waite updated JENKINS-17898 Git plugin: tags triggers dont work as expected Change By: Mark Waite (16/May/13 3:47 AM) Issue Type: Bug Improvement 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] [git] (JENKINS-17898) Git plugin: tags triggers don't work as expected
Ferry Huberts
created JENKINS-17898
Git plugin: tags triggers dont work as expected
Issue Type:
Bug
Affects Versions:
current
Assignee:
Nicolas De Loof
Components:
git
Created:
08/May/13 11:06 AM
Description:
I trigger Jenkins from a post-receive hook on my git server:
curl -s "${jenkinsUrl}/git/notifyCommit?url="">
When I push a tag on the latest commit that Jenkins has already built, no new built is started.
Since the commit sha of the branch to build doesn't change that's logical.
However, since I use 'git describe' to provide traceability of my artifacts, this is not what I'd like to happen: the 'git describe' output actually changes because of the new tag.
To fix this, the git plugin must not only look at the commit sha but also check the tags on the latest commit that it has built; if there is a new/changed tag on that commit, a new build has to be started.
Environment:
Fedora 17 64bit
Project:
Jenkins
Priority:
Major
Reporter:
Ferry Huberts
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] [git] (JENKINS-17898) Git plugin: tags triggers don't work as expected
Ferry Huberts
updated JENKINS-17898
Git plugin: tags triggers dont work as expected
Change By:
Ferry Huberts
(08/May/13 11:07 AM)
Description:
ItriggerJenkinsfromapost-receivehookonmygitserver:curl-s${jenkinsUrl}/git/notifyCommit?url="">WhenIpushatagonthelatestcommitthatJenkinshasalreadybuilt,nonew
built
build
isstarted.Sincethecommitshaofthebranchtobuilddoesntchangethatslogical.However,sinceIusegitdescribetoprovidetraceabilityofmyartifacts,thisisnotwhatIdliketohappen:thegitdescribeoutputactuallychangesbecauseofthenewtag.Tofixthis,thegitpluginmustnotonlylookatthecommitshabutalsocheckthetagsonthelatestcommitthatithasbuilt;ifthereisanew/changedtagonthatcommit,anewbuildhastobestarted.
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] [git] (JENKINS-17898) Git plugin: tags triggers don't work as expected
Ferry Huberts
updated JENKINS-17898
Git plugin: tags triggers dont work as expected
Change By:
Ferry Huberts
(08/May/13 11:08 AM)
Description:
ItriggerJenkinsfromapost-receivehookonmygitserver:curl-s${jenkinsUrl}/git/notifyCommit?url="">WhenIpusha
(annotated)
tagonthelatestcommitthatJenkinshasalreadybuilt,nonewbuildisstarted.Sincethecommitshaofthebranchtobuilddoesntchangethatslogical.However,sinceIusegitdescribetoprovidetraceabilityofmyartifacts,thisisnotwhatIdliketohappen:thegitdescribeoutputactuallychangesbecauseofthenewtag.Tofixthis,thegitpluginmustnotonlylookatthecommitshabutalsocheckthetagsonthelatestcommitthatithasbuilt;ifthereisanew/changedtagonthatcommit,anewbuildhastobestarted.
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.
