Moving jobs that never have been run to attic

[deepssin]

Solves issue - #2336

[jmundack]

can we just remove these? (and if need be - we can always git revert and pull it back in?)

my concern with moving this to the attic is - now we have a "new" dumping ground for things :)

hoping we can just leverage git instead of moving things around

[dmick]

I created attic/ to 1) address the uncertainty that some consumer of a job wasn't upset when I disabled their job, and 2) allow study of "how we once did things". Both of those motivations obviously lose importance over time, as the original consumers of the job fade away, and as the code moves past the archiving point. It's enough easier for casual browsers that I thought it was a reasonable compromise at the time. It doesn't bother me to ignore a top-level directory, but at some point the value of the contents approaches zero.

[dmick]

So @jmundack: I see that you did the investigation of this issue to start in the GitHub issue linked here. I think the "never have been run" is not strictly correct; I know those jobs have run in the past, and I suspect the stats have been reset by a reboot or reinstall of the jenkins server.

[deepssin]

Apologies for the delayed response @jmundack @dmick , was tied up with other priority tasks over the past few weeks.

Thanks for clarifying earlier. Since Jenkins history can get reset, is there a reliable way for us to confirm whether a job has ever run before?

[jmundack]

So @jmundack: I see that you did the investigation of this issue to start in the GitHub issue linked here. I think the "never have been run" is not strictly correct; I know those jobs have run in the past, and I suspect the stats have been reset by a reboot or reinstall of the jenkins server.

@dmick - looking at this job for example - it failed 5 years ago. The fact that we have some jobs with history from 5 years ago, i would expect it to be safe to say the the "never been run" jobs reported by Jenkins - has not been run at least in the last 5 years? if so, we should be good to kill it?

my take on this is - we need to have some lifecycle for cleaning these up otherwise we will accumulate a lot of crud with community members coming in and our of the project