Whatever you choose if you change what you would build as a result then you have to take into account that others downstream will have cached something they downloaded (even if it is a developer machine rather than a Nexus/Artifactory etc) and then you are allowing different builds in your CI than a developer or another CI consuming those artifacts would get. I would heavily caution you against doing anything that knowingly introduces a difference between what would happen in CI and on a developer machine configured with the Jenkins maven proxy.
given most plugins are released from someone own machine that will have cached these libraries, you will continue to have these libraries used and included in plugins. > (And while we're at it: Do we want our caches to expire, or have consistent builds in favor of alignment with upstream re-releases?) No never. (unless it is a snapshot). - especially because of 2 but also If it expires you are then allowing changes and then you *will *get a different result locally and on a developer machine. Re releasing artifacts is considered a very very bad thing to do, if a repo is doing that its likely doing other bad things and we need to tread very carefully. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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-dev/56fa7699-ad33-450f-802b-4f453ed7e49c%40googlegroups.com.
