[JIRA] [buildresulttrigger] (JENKINS-18716) build is triggering to early

2013-07-12 Thread [email protected] (JIRA) 














































Marcus Mosttler
 commented on  JENKINS-18716


build is triggering to early















We have daily builds that running every morning (as well as on demand during the day).  We also have a set of deploy jobs that deploy designated builds to our test environments.  The deploy jobs are triggered on the successful completion of the build it is configured to watch (the build that currently is to be deployed to that test environment).
Looking at the builds and deploys this morning I saw that it once again triggered too early causing the previous builds to be deployed.
I cycled the Jenkins service hoping if the memory was cleared that maybe it would start working like it did originally.  After restarting the service a number of deploy jobs were triggered for some reason  and deployed older builds that have already been successfully run in the past.

Not sure why it decided to trigger the jobs after a restart.



























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/groups/opt_out.
 
 

[JIRA] [buildresulttrigger] (JENKINS-18716) build is triggering to early

2013-07-11 Thread [email protected] (JIRA) 














































Marcus Mosttler
 created  JENKINS-18716


build is triggering to early















Issue Type:


Bug



Assignee:


Gregory Boissinot



Components:


buildresulttrigger



Created:


11/Jul/13 4:15 PM



Description:


recently our triggered build is running as soon as the job its watching starts instead of waiting until it is finished then checking its status (which we have configured to trigger on SUCCESS).

I upgraded from .10 to .12 hoping it would fix the issue but it is still triggering too early.




Environment:


Windows 7




Project:


Jenkins



Priority:


Major



Reporter:


Marcus Mosttler

























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/groups/opt_out.