delroth/hydra
0
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity

* Be a bit less aggressive in rescheduling builds that have already

Browse source 
been done.
This commit is contained in:
Eelco Dolstra 2009-10-19 12:36:15 +00:00
parent cec3201720
commit 8f9417f822
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
src/script/hydra_scheduler.pl
View file

@ -280,10 +280,10 @@ sub checkJob {
# cached result from the first). This ensures that the builds # cached result from the first). This ensures that the builds
# with the highest ID will always be the ones that we want in # with the highest ID will always be the ones that we want in
# the channels. # the channels.
# !!! Checking $drvPath doesn't take meta-attributes into # !!! Checking $outPath doesn't take meta-attributes into
# account. For instance, do we want a new build to be # account. For instance, do we want a new build to be
# scheduled if the meta.maintainers field is changed? # scheduled if the meta.maintainers field is changed?
my @previousBuilds = $jobInDB->builds->search({drvPath => $drvPath, isCurrent => 1}); my @previousBuilds = $jobInDB->builds->search({outPath => $outPath, isCurrent => 1});
if (scalar(@previousBuilds) > 0) { if (scalar(@previousBuilds) > 0) {
print "already scheduled/built\n"; print "already scheduled/built\n";
$currentBuilds->{$_->id} = 1 foreach @previousBuilds; $currentBuilds->{$_->id} = 1 foreach @previousBuilds;