ahuston-0/hydra
1
0
Fork 0
Code Issues Pull Requests 1 Packages Projects Releases Wiki Activity

When manually scheduling an eval, force re-instantiation of store derivations

Browse Source 
Without this, if (failed or aborted) derivations have been
garbage-collected, there is no way to restart them, which is very
annoying. Now we set a forceEval flag in the jobset to cause it to be
re-evaluated even if none of the inputs have changed.
This commit is contained in:
Eelco Dolstra
2016-10-24 20:20:20 +02:00
parent 140cbe9302
commit a12e9478e7
5 changed files with 18 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
src/lib/Hydra/Schema/Jobsets.pm
View File

@ -129,6 +129,11 @@ __PACKAGE__->table("Jobsets");
data_type: 'text'
is_nullable: 1
=head2 forceeval
data_type: 'boolean'
is_nullable: 1
=cut
__PACKAGE__->add_columns(
@ -166,6 +171,8 @@ __PACKAGE__->add_columns(
{ data_type => "integer", default_value => 100, is_nullable => 0 },
"fetcherrormsg",
{ data_type => "text", is_nullable => 1 },
"forceeval",
{ data_type => "boolean", is_nullable => 1 },
);
=head1 PRIMARY KEY
@ -338,8 +345,8 @@ __PACKAGE__->has_many(
);
# Created by DBIx::Class::Schema::Loader v0.07043 @ 2015-07-30 16:52:20
# DO NOT MODIFY THIS OR ANYTHING ABOVE! md5sum:Coci9FdBAvUO9T3st2NEqA
# Created by DBIx::Class::Schema::Loader v0.07045 @ 2016-10-24 20:12:51
# DO NOT MODIFY THIS OR ANYTHING ABOVE! md5sum:PSR66NnVRNTMFhDEm10erA
my %hint = (
columns => [