In the interests of attempting to trim Jenkins down a more manageable size, I'd like those of us who have admin access to Jenkins and have private jobs configured that are not for general use to please remove them if they are not required.
You don't have to remove these, just do a mental audit of what you need to keep, these are not free because Jenkins has to load lots of .xml junk from disk for each of them and we're really pushing the limits of Jenkins performance with our cluster.
@jbergstroem I think we should be more aggressive with build trimming, we have nearly 500 builds in the last 30 days for node-test-commit alone. I can't find where we set this though.
In the interests of attempting to trim Jenkins down a more manageable size, I'd like those of us who have admin access to Jenkins and have private jobs configured that are not for general use to please remove them if they are not required.
@thealphanerd you have three but one of them is for general use, would you mind renaming
thealphanerd-smokerto justsmokeror something more generic? You also have https://ci.nodejs.org/view/All/job/thealphanerd-npm/ and https://ci.nodejs.org/view/All/job/thealphanerd-smoker-ppc/You don't have to remove these, just do a mental audit of what you need to keep, these are not free because Jenkins has to load lots of .xml junk from disk for each of them and we're really pushing the limits of Jenkins performance with our cluster.
@jbergstroem I think we should be more aggressive with build trimming, we have nearly 500 builds in the last 30 days for node-test-commit alone. I can't find where we set this though.