Hmm... I was hoping for something in the UI itself... but thanks for the info, if I'm ever feeling not-lazy (hah!), or actually NEED to know, it will come in handy!
On Wed, Jan 15, 2014 at 11:50 AM, Daniel Beck <[email protected]> wrote: > I don't think it's exposed anywhere on the UI (except indirectly, e.g. > dates in polling logs and when previous builds were started). > > However, you can access it via the Jenkins script console, if you're > willing to work for the information. > > Run the following script, replacing 'job-name' with the name of the job > you're interested in: > --- > Jenkins.instance.getItemByFullName('job-name').triggers.each { desc, trig > -> > println desc.class.name > trig.tabs.tabs.each { it.bits.each { b -> println Long.toBinaryString(b) > } } > println "" > } > return > --- > > This will print something like the following: > --- > hudson.triggers.TimerTrigger$DescriptorImpl > 1000000000000001000000000000001000000000000001 > 1000000000000000 > 1000000000000000 > 1111111111110 > > hudson.triggers.SCMTrigger$DescriptorImpl > 1000000000000000000000000000000 > 10000000000 > 11111111111111111111111111111110 > 11111110000 > --- > > One block per configured trigger, in this case one 'Build periodically' > (TimerTrigger) and one 'Poll SCM' (SCMTrigger). The binary lines correspond > to minutes, hours, day-of-month and month respectively. The bits which are > set indicate when the trigger is set to trigger. The rightmost bit always > represents '0' (which cannot be set for day-of-month and month). > Day-of-week is special and missing here, left as an exercise to the reader. > > In the first example, I used the cron expression 'H/15 H(12-18) 15 * *'. > It is set to trigger on 15:(0,15,30,45) on the 15th of every month. > > In the second example, I used the expression 'H 10 * 4-10 *'. H is > effectively 31, polling SCM every day from April to October on 10:31. > > This uses private members etc. and might break in future versions in > Jenkins. Should be safe from breaking Jenkins though. > > On 15.01.2014, at 18:40, Paul Molodowitch <[email protected]> wrote: > > > I'm a big fan of using the hash in scheduled builds - ie, > > > > H H * * * > > > > to run a job once a day. > > > > The only downside is that it can be hard to know when a job will next > build - is there any way to see that information? > > > > Thanks, > > Paul > > > > -- > > You received this message because you are subscribed to the Google > Groups "Jenkins Users" 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. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-users/XX1-XHC67co/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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.
