Hi David I'm describing all of this for background. What I'm asking the community > is, is this a reasonable strategy? I can't help the feeling that this is > taking reusability a bit too far. I can't give any technical arguments > against it, so I'm just looking for some perspective. >
I think this is a sound strategy. Without this, projects will quickly become snowflakes. Every team will start to invent their own solution for similar problems. Many of those will be haphazard because people don't have time and/or knowledge to understand the underlying issue and correctly fix many problems. So the solutions tend to be brittle and there will be a lot of conversations: "Jenkins sucks. It always breaks" "What happened?" "Well ... [long explanation]" "Hey, we had that too. We just [...]" "Oh." Regards, Aaron Digulla -- 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/9c086c8c-587b-43dd-9da0-5e2d6ee4319d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
