[JIRA] [git] (JENKINS-17411) Pushing a fast-forward merge does not trigger a build

[blinov.vyaches...@gmail.com (JIRA)]

Vyacheslav Blinov
 commented on  JENKINS-17411


Pushing a fast-forward merge does not trigger a build















Same here. Our environment uses automated deployment based on branching. As we merge changes to master we expect Jenkins to build them in master providing new artefact independently of is this the same SHA as in other branch, that Jenkins builded earlier. There is no way to choose such strategy atm.



























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-17411) Pushing a fast-forward merge does not trigger a build

[vinc...@latombe.net (JIRA)]

Vincent Latombe
 updated  JENKINS-17411


Pushing a fast-forward merge does not trigger a build
















Change By:


Vincent Latombe
(15/May/13 6:32 PM)




Component/s:


pollscm



























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.