Well, we have lots of jobs, both freestyle and different styles of the new pipeline, not all for sw that's currently in active development but we still need to know we can build these. We would rather invest our time in something that's useful for all jobs without changing all those old job definitions. Also everything that we keep for a while on Jenkins as an artifact is not necessarily something that we would deploy to artifactory. Coupling the artifact retention to the number of builds in Jenkins is often easier than having a "works for all cleanup policy" in artifactory.
-- 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/429aa64d-c305-4bbe-b6a9-67a4c08a232c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
