Thats fine, but insisting that I dump the contents of that repository onto disk in a specific fashion may or may not help me use the contents. You keep insisting that a checkout into a directory controlled by the Jenkins server is a necessary part of the way one must use the contents. I disagree.
On Wed, Mar 26, 2014 at 11:44 AM, Les Mikesell <[email protected]>wrote: > On Wed, Mar 26, 2014 at 1:31 PM, Peter Savage <[email protected]> > 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 > [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.
