On Sat, Jan 2, 2016 at 4:08 PM, Daniel Beck <[email protected]> wrote:
> Workflows use the previous (completed) build's checkouts to determine what > SCMs should participate in polling. Without such a build, it's not known > whether there's even an SCM in use. If I have a checkout() command directly in the workflow script itself, why can't the workflow detect that an SCM is in use? In the checkout() command, there is a parameter poll. If you set it to *poll: True* or omit it, then that SCM is supposed to participate in polling. If you set *poll: False*, then that SCM is not supposed to participate in polling. I omitted it the parameter, because in the workflow snippet generator, if you select *Include in polling*, then it omits the parameter. So the option with no previous (completed) build is to never build, or to > always build, on polling. Are you sure about that? How can I configure this behavior? -- Craig -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAG%3DrPVcZ%3D1_5i9gXZCEppjCb8eCrxF9M27P%3DcfZ1FKhuaS%3DsYg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
