On 29/06/11 6:24 PM, Schwab,Wilhelm K wrote:
+1 to Sig's answer. Old builds are great, and we should (and do) keep them around, but they do not need to be on the CI server. As Sig said, the old versions don't change, so CI gets pretty boring.
There is the option to disable the build job, so that no further builds take place (until there are maintenance releases to build).
There is also the option to use the CI server as the build archive as well. You can mark some build numbers as "never remove". Normally, only the last N builds are kept, and the oldest is deleted after the new build completes (unless that oldest build is the last successful build, then it's kept until the next successful build). Whichever builds are marked "never remove" would form the archive. That would eliminate the apparent confusion caused by having the archive at https://gforge.inria.fr/frs/?group_id=1299
The other factor is that a transition to Jenkins from Hudson is happening, which is driving the desire to drop the Hudson based 1.2 builds.
