"It seems odd to care if the contents of a repository changed if you aren't going to use them in the job that is triggered."
That is so loaded with inherent assumptions I don't even know how to touch it. On Wed, Mar 26, 2014 at 11:08 AM, Les Mikesell <[email protected]>wrote: > On Wed, Mar 26, 2014 at 12:42 PM, <[email protected]> wrote: > > It seems pretty inflexible. Why not just separate polling from checkout? > One > > step to poll repositories, and one step to checkout. > > It seems odd to care if the contents of a repository changed if you > aren't going to use them in the job that is triggered. Do you have > some unusual requirement? > > -- > Les Mikesell > [email protected] > > -- > 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/-WqmXrEdAEg/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- 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/d/optout.
