[JIRA] [git] (JENKINS-17614) Jenkins triggers builds on git SCM changes, but nothing changed
Mark Waite edited a comment on JENKINS-17614 Jenkins triggers builds on git SCM changes, but nothing changed Andrew Matheny I don't understand how a job which does not poll could trigger on SCM changes. Does that mean you have the job configured to both "Build after other projects are built" and to "Poll SCM"? If you don't intend to poll SCM for changes, couldn't you delete the polling from that job? 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] (JENKINS-17614) Jenkins triggers builds on git SCM changes, but nothing changed
Xavier Shay commented on JENKINS-17614 Jenkins triggers builds on git SCM changes, but nothing changed I am seeing a similiar issue: particular builds always building twice. Still trying to narrow down a repro. 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] (JENKINS-17614) Jenkins triggers builds on git SCM changes, but nothing changed
Xavier Shay edited a comment on JENKINS-17614 Jenkins triggers builds on git SCM changes, but nothing changed I am seeing a similiar issue: particular builds always building twice. Still trying to narrow down a repro. > This issue occurs when a branch with the same name exists in two different subbranches, e.g. 'origin/features/new_feature' and 'origin/new_feature' This is not the case for my setup. 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] (JENKINS-17614) Jenkins triggers builds on git SCM changes, but nothing changed
Georgi Mitsov commented on JENKINS-17614 Jenkins triggers builds on git SCM changes, but nothing changed This issue occurs when a branch with the same name exists in two different subbranches, e.g. 'origin/features/new_feature' and 'origin/new_feature' Hope that helps! 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] (JENKINS-17614) Jenkins triggers builds on git SCM changes, but nothing changed
Karthi Venkataraman updated JENKINS-17614 Jenkins triggers builds on git SCM changes, but nothing changed Circumventing the ghost build that Jenkins triggers, using a Run condition to check the GIT_COMMIT and GIT_PREVIOUS_COMMIT Change By: Karthi Venkataraman (21/Mar/14 11:25 AM) Attachment: Image_1.png 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] (JENKINS-17614) Jenkins triggers builds on git SCM changes, but nothing changed
Karthi Venkataraman
commented on JENKINS-17614
Jenkins triggers builds on git SCM changes, but nothing changed
A Possible workaround to the solution is to check the ${GIT_COMMIT} and ${GIT_PREVIOUS_COMMIT} variables in a job and then based on the outcome of this job, trigger the actual job as a downstream. This would require "Run Condition Plugin" (https://wiki.jenkins-ci.org/display/JENKINS/Run+Condition+Plugin)
Steps:
1. Install the Run Condition Plugin
2. Create a Test Job, which would Poll SCM in the required interval. As a condition in the test job, you can configure to test for a "Strings Match" condition and as a result, in the "Steps to run if condition is met" option, you can execute a windows batch command "exit 1", which will simply fail this test job if the Git current commit and Previous commit matches (a possible duplicate build triggered in Jenkins).
3. If these commits do not match, then it is a valid candidate for execution and the actual job that you want to execute can be called in the "Post Build Action". So essentially, you are checking the current and previous commit and aborting the test job, if they are same, and proceed to build the actual job, if the commits are different.
Let me also try to attach a screen shot for help. Please try out and see if this going to help.
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] (JENKINS-17614) Jenkins triggers builds on git SCM changes, but nothing changed
Andrew Matheny commented on JENKINS-17614 Jenkins triggers builds on git SCM changes, but nothing changed [markewaite] As Alexander said, there is no other trigger on the job. Which is why it is alarming to see builds being triggered on SCM changes. [uvizhe] Unfortunately, I already have the Maven Integration plugin enabled. I'll try recreating this job to see if that helps. 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-17614) Jenkins triggers builds on git SCM changes, but nothing changed
Alexander Uvizhev commented on JENKINS-17614 Jenkins triggers builds on git SCM changes, but nothing changed I don't understand how a job which does not poll could trigger on SCM changes. Mark, that was a reason why I created this issue. However it doesn't occur in my Jenkins anymore. I believe it has disappeared with other strange things when I turned Maven Integration Plugin on (I've disabled it shortly after I installed Jenkins). 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-17614) Jenkins triggers builds on git SCM changes, but nothing changed
Mark Waite commented on JENKINS-17614 Jenkins triggers builds on git SCM changes, but nothing changed [amatheny] I don't understand how a job which does not poll could trigger on SCM changes. Does that mean you have the job configured to both "Build after other projects are built" and to "Poll SCM"? If you don't intend to poll SCM for changes, couldn't you delete the polling from that job? 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-17614) Jenkins triggers builds on git SCM changes, but nothing changed
Andrew Matheny commented on JENKINS-17614 Jenkins triggers builds on git SCM changes, but nothing changed I'm having the same problem for a job where it's only build trigger is "Build after other projects are built". I'm seeing builds that are triggered on SCM changes which is problematic since this particular job is creating AWS resources for deployment. Has anyone came up with a workaround? 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-17614) Jenkins triggers builds on git SCM changes, but nothing changed
Mark Waite updated JENKINS-17614 Jenkins triggers builds on git SCM changes, but nothing changed Change By: Mark Waite (08/Feb/14 2:34 PM) Summary: Jenkins triggers builds on git SCM changes although not configured , but nothing changed 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.
