I think a better answer to this is that this is not a typical use case for people or teams using Jenkins. Although I can see some value to something like this, it may not have enough support in general to change the behavior of Jenkins. I had a situation in the past for a similar need. At that time, the code base was sufficiently small that the checkout was fast enough for my needs. It sounds like another tool or process may suit your needs better if this is not the case.
Hope this helps, topher Thanks, Chris topher1...@gmail.com On Wed, Mar 26, 2014 at 12:44 PM, Les Mikesell <lesmikes...@gmail.com>wrote: > On Wed, Mar 26, 2014 at 1:31 PM, Peter Savage <gorillates...@gmail.com> > wrote: > > "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. > > Yes, and it matches the assumptions built into jenkins. That is, it > works as designed for a lot of people. I think it is a reasonable > assumption that if you trigger a job on a repository change that you > are planning to use the contents. > > -- > Les Mikesell > lesmikes...@gmail.com > > -- > 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 jenkinsci-users+unsubscr...@googlegroups.com. > 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
