Run suppressed in scheduleBuild2
 
https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/jenkins/model/ParameterizedJobMixIn.java#L108-L109

On Monday, March 23, 2015 at 8:19:14 PM UTC+3, Kanstantsin Shautsou wrote:
>
> Suppressing Triggers itself is not performance friendly. You may have 
> hundred jobs with "* * * * *" but only one enabled.
> I see no changes in triggers package since previous year, so i mostly test 
> on 1.565.3
> Search in jira found only thousands issues for triggering jobs. 
>
> Created job timerTrigger with cron "* * * * *" and disabled.
> Logger for hudson.triggers shows:
>
> Mar 23, 2015 8:16:00 PM FINE hudson.triggers.Trigger
>
> cron checking hudson.model.FreeStyleProject@6878439f[timerTrigger] with spec 
> ‘* * * * *’
>
> Mar 23, 2015 8:16:00 PM CONFIG hudson.triggers.Trigger
>
> cron triggered hudson.model.FreeStyleProject@6878439f[timerTrigger]
>
> According to code it calls job.scheduleBuild(0, new TimerTriggerCause()) 
> and then probably suppressed in queue...
>
> On Monday, March 23, 2015 at 7:57:12 PM UTC+3, Jesse Glick wrote:
>>
>> On Mon, Mar 23, 2015 at 11:11 AM, Kanstantsin Shautsou 
>> <kanstan...@gmail.com> wrote: 
>> > I got weird situation when Trigger is executed for disabled project. 
>>
>> Possible that each Trigger is expected to suppress itself at some 
>> point for a disabled project, or possible that this is a mistake. Does 
>> this happen for standard TimerTrigger and SCMTrigger? Is the behavior 
>> the same in old Jenkins releases? 
>>
>> > I also had a case when .run() was called before .start() on Trigger 
>>
>> Seems like a bug (race condition). 
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/17b06115-b91b-4288-8be9-bdca31701c2b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to