I discovered today while checking on load on builds.apache.org that not only does DeltaSpike have a huge number of jobs that poll and run whenever there's a change in Git - all those jobs are then kicked off *again* by https://builds.apache.org/job/DeltaSpike%20Deploy/, which is kicked off by the same polling! The end result is running 50 or so jobs *twice*, taking half an hour or so each, for every single change that goes into DeltaSpike. Please, please, please fix this to only trigger your jobs once each, not twice, and ideally, it'd be great if you could rationalize your jobs and cut down the number of jobs, so as not to hog basically all the available slots for non-Hadoop-related jobs on builds.apache.org. Thanks.
A.
