ahuston-0/hydra
1
0
Fork 0
Code Issues Pull Requests 1 Packages Projects Releases Wiki Activity
hydra/src/lib/Hydra/Schema/Result/Jobsets.pm

436 lines
7.8 KiB
Perl
Raw Normal View History

Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
use utf8;
DBIx::Class: migrate to use_namespaces This gives us a place to put helper functions that act on entire tables, not just individual records. This should be a backwards compatible change, except in places we're manually using result class names.
2021-08-26 12:03:00 -04:00
package Hydra::Schema::Result::Jobsets;
* Basic job info in the database.
2008-11-04 18:23:28 +00:00
2009-10-23 15:05:16 +00:00
# Created by DBIx::Class::Schema::Loader
# DO NOT MODIFY THE FIRST PART OF THIS FILE
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
=head1 NAME
DBIx::Class: migrate to use_namespaces This gives us a place to put helper functions that act on entire tables, not just individual records. This should be a backwards compatible change, except in places we're manually using result class names.
2021-08-26 12:03:00 -04:00
Hydra::Schema::Result::Jobsets
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
=cut
* Basic job info in the database.
2008-11-04 18:23:28 +00:00
use strict;
use warnings;
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
use base 'DBIx::Class::Core';
Merge in the first bits of the API work The catalyst-action-rest branch from shlevy/hydra was an exploration of using Catalyst::Action::REST to create a JSON API for hydra. This commit merges in the best bits from that experiment, with the goal that further API endpoints can be added incrementally. In addition to migrating more endpoints, there is potential for improvement in what's already been done: * The web interface can be updated to use the same non-GET endpoints as the JSON interface (using x-tunneled-method) instead of having a separate endpoint * The web rendering should use the $c->stash->{resource} data structure where applicable rather than putting the same data in two places in the stash * Which columns to render for each endpoint is a completely debatable question * Hydra::Component::ToJSON should turn has_many relations that have strings as their primary keys into objects instead of arrays Fixes NixOS/hydra#98 Signed-off-by: Shea Levy <shea@shealevy.com>
2013-06-17 12:34:21 -04:00
=head1 COMPONENTS LOADED
=over 4
=item * L<Hydra::Component::ToJSON>
=back
=cut
__PACKAGE__->load_components("+Hydra::Component::ToJSON");
sql: Generate models from postgresql Lowercasing is due to postgresql not having case-sensitive table names. It always technically workde before, but those table names never existed literally. The switch to generating from postgresql is to handle an upcoming addition of an auto-incrementign ID to the Jobset table. Sqlite doesn't seem to be able to handle the table having an auto incrementing ID field which isn't the primary key, but we can't change the primary key trivially. Since hydra doesn't support sqlite and hasn't for many year anyway, it is easier to just generate from pgsql directly.
2020-02-06 12:23:47 -05:00
=head1 TABLE: C<jobsets>
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
=cut
* Basic job info in the database.
2008-11-04 18:23:28 +00:00
sql: Generate models from postgresql Lowercasing is due to postgresql not having case-sensitive table names. It always technically workde before, but those table names never existed literally. The switch to generating from postgresql is to handle an upcoming addition of an auto-incrementign ID to the Jobset table. Sqlite doesn't seem to be able to handle the table having an auto incrementing ID field which isn't the primary key, but we can't change the primary key trivially. Since hydra doesn't support sqlite and hasn't for many year anyway, it is easier to just generate from pgsql directly.
2020-02-06 12:23:47 -05:00
__PACKAGE__->table("jobsets");
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
=head1 ACCESSORS
=head2 name
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
data_type: 'text'
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
is_nullable: 0
Jobsets: add a SERIAL, unique, non-null id column A postgresql column which is non-null and unique is treated with the same optimisations as a primary key, so we have no need to try and recreate the `id` as the primary key. No read paths are impacted by this change, and the database will automatically create an ID for each insert. Thus, no code needs to change.
2020-02-05 14:06:21 -05:00
=head2 id
data_type: 'integer'
is_auto_increment: 1
is_nullable: 0
sequence: 'jobsets_id_seq'
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
=head2 project
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
data_type: 'text'
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
is_foreign_key: 1
is_nullable: 0
=head2 description
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
data_type: 'text'
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
is_nullable: 1
=head2 nixexprinput
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
data_type: 'text'
Copy the flake migration from the flake branch hydra.nixos.org is already running this rev, and it should be safe to apply to everyone else. If we make changes to this migration, we'll need to write another migration anyway.
2020-02-09 15:17:24 -05:00
is_nullable: 1
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
=head2 nixexprpath
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
data_type: 'text'
Copy the flake migration from the flake branch hydra.nixos.org is already running this rev, and it should be safe to apply to everyone else. If we make changes to this migration, we'll need to write another migration anyway.
2020-02-09 15:17:24 -05:00
is_nullable: 1
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
=head2 errormsg
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
data_type: 'text'
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
is_nullable: 1
=head2 errortime
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
data_type: 'integer'
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
is_nullable: 1
=head2 lastcheckedtime
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
data_type: 'integer'
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
is_nullable: 1
Support push notification of repository changes External machines can now notify Hydra that it should check a repository by sending a GET or PUSH request to /api/push, providing a list of jobsets to be checked and/or a list of repository URLs. In the latter case, all jobsets that have any of the specified repositories as an input will be checked. For instance, you can configure GitHub or BitBucket to send a request to the URL http://hydra.example.org/api/push?repos=git://github.com/NixOS/nixpkgs.git to trigger evaluation of all jobsets that have git://github.com/NixOS/nixpkgs.git as an input, or to the URL http://hydra.example.org/api/push?jobsets=patchelf:trunk,nixpkgs:trunk to trigger evaluation of just the specified jobsets.
2013-02-25 21:04:10 +01:00
=head2 triggertime
data_type: 'integer'
is_nullable: 1
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
=head2 enabled
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
data_type: 'integer'
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
default_value: 1
is_nullable: 0
=head2 enableemail
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
data_type: 'integer'
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
default_value: 1
is_nullable: 0
added hide feature for project/jobset
2010-06-04 14:43:28 +00:00
=head2 hidden
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
data_type: 'integer'
added hide feature for project/jobset
2010-06-04 14:43:28 +00:00
default_value: 0
is_nullable: 0
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
=head2 emailoverride
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
data_type: 'text'
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
is_nullable: 0
hydra: make nr of build to keep configurable per jobset
2010-08-10 06:48:45 +00:00
=head2 keepnr
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
data_type: 'integer'
hydra: make nr of build to keep configurable per jobset
2010-08-10 06:48:45 +00:00
default_value: 3
is_nullable: 0
Allow a per-jobset check interval This allows checking a jobset (say) at most once a day. It's also possible to disable polling by setting the interval to 0. This is useful for jobsets that use push notification or are manually evaluated.
2013-05-02 17:51:38 +02:00
=head2 checkinterval
data_type: 'integer'
default_value: 300
is_nullable: 0
hydra-queue-runner: Improved scheduling Each jobset now has a "scheduling share" that determines how much of the build farm's time it is entitled to. For instance, if a jobset has 100 shares and the total number of shares of all jobsets is 1000, it's entitled to 10% of the build farm's time. When there is a free build slot for a given system type, the queue runner will select the jobset that is furthest below its scheduling share over a certain time window (currently, the last day). Withing that jobset, it will pick the build with the highest priority. So meta.schedulingPriority now only determines the order of builds within a jobset, not between jobsets. This makes it much easier to prioritise one jobset over another (e.g. nixpkgs:trunk over nixpkgs:stdenv).
2013-09-21 14:47:52 +00:00
=head2 schedulingshares
data_type: 'integer'
default_value: 100
is_nullable: 0
Distinguish between permanent evaluation errors and transient input errors Fixes #112.
2013-09-25 16:21:16 +02:00
=head2 fetcherrormsg
data_type: 'text'
is_nullable: 1
When manually scheduling an eval, force re-instantiation of store derivations 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.
2016-10-24 20:20:20 +02:00
=head2 forceeval
data_type: 'boolean'
is_nullable: 1
hydra-evaluator improvements * The "Jobset" page now shows when evaluations are in progress (rather than just pending). * Restored the ability to do a single evaluation from the command line by doing "hydra-evaluator <project> <jobset>". * Fix some consistency issues between jobset status in PostgreSQL and in hydra-evaluator. In particular, "lastCheckedTime" was never updated internally.
2017-03-13 16:19:22 +01:00
=head2 starttime
data_type: 'integer'
is_nullable: 1
Copy the flake migration from the flake branch hydra.nixos.org is already running this rev, and it should be safe to apply to everyone else. If we make changes to this migration, we'll need to write another migration anyway.
2020-02-09 15:17:24 -05:00
=head2 type
data_type: 'integer'
default_value: 0
is_nullable: 0
=head2 flake
data_type: 'text'
is_nullable: 1
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
=cut
hydra * remove trailing spaces from email notification * option to disable email notification for jobset
2010-01-06 13:07:59 +00:00
__PACKAGE__->add_columns(
"name",
sql: Generate models from postgresql Lowercasing is due to postgresql not having case-sensitive table names. It always technically workde before, but those table names never existed literally. The switch to generating from postgresql is to handle an upcoming addition of an auto-incrementign ID to the Jobset table. Sqlite doesn't seem to be able to handle the table having an auto incrementing ID field which isn't the primary key, but we can't change the primary key trivially. Since hydra doesn't support sqlite and hasn't for many year anyway, it is easier to just generate from pgsql directly.
2020-02-06 12:23:47 -05:00
{ data_type => "text", is_nullable => 0 },
Jobsets: add a SERIAL, unique, non-null id column A postgresql column which is non-null and unique is treated with the same optimisations as a primary key, so we have no need to try and recreate the `id` as the primary key. No read paths are impacted by this change, and the database will automatically create an ID for each insert. Thus, no code needs to change.
2020-02-05 14:06:21 -05:00
"id",
{
data_type => "integer",
is_auto_increment => 1,
is_nullable => 0,
sequence => "jobsets_id_seq",
},
hydra * remove trailing spaces from email notification * option to disable email notification for jobset
2010-01-06 13:07:59 +00:00
"project",
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
{ data_type => "text", is_foreign_key => 1, is_nullable => 0 },
hydra * remove trailing spaces from email notification * option to disable email notification for jobset
2010-01-06 13:07:59 +00:00
"description",
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
{ data_type => "text", is_nullable => 1 },
hydra * remove trailing spaces from email notification * option to disable email notification for jobset
2010-01-06 13:07:59 +00:00
"nixexprinput",
Copy the flake migration from the flake branch hydra.nixos.org is already running this rev, and it should be safe to apply to everyone else. If we make changes to this migration, we'll need to write another migration anyway.
2020-02-09 15:17:24 -05:00
{ data_type => "text", is_nullable => 1 },
hydra * remove trailing spaces from email notification * option to disable email notification for jobset
2010-01-06 13:07:59 +00:00
"nixexprpath",
Copy the flake migration from the flake branch hydra.nixos.org is already running this rev, and it should be safe to apply to everyone else. If we make changes to this migration, we'll need to write another migration anyway.
2020-02-09 15:17:24 -05:00
{ data_type => "text", is_nullable => 1 },
hydra * remove trailing spaces from email notification * option to disable email notification for jobset
2010-01-06 13:07:59 +00:00
"errormsg",
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
{ data_type => "text", is_nullable => 1 },
hydra * remove trailing spaces from email notification * option to disable email notification for jobset
2010-01-06 13:07:59 +00:00
"errortime",
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
{ data_type => "integer", is_nullable => 1 },
hydra * remove trailing spaces from email notification * option to disable email notification for jobset
2010-01-06 13:07:59 +00:00
"lastcheckedtime",
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
{ data_type => "integer", is_nullable => 1 },
Support push notification of repository changes External machines can now notify Hydra that it should check a repository by sending a GET or PUSH request to /api/push, providing a list of jobsets to be checked and/or a list of repository URLs. In the latter case, all jobsets that have any of the specified repositories as an input will be checked. For instance, you can configure GitHub or BitBucket to send a request to the URL http://hydra.example.org/api/push?repos=git://github.com/NixOS/nixpkgs.git to trigger evaluation of all jobsets that have git://github.com/NixOS/nixpkgs.git as an input, or to the URL http://hydra.example.org/api/push?jobsets=patchelf:trunk,nixpkgs:trunk to trigger evaluation of just the specified jobsets.
2013-02-25 21:04:10 +01:00
"triggertime",
{ data_type => "integer", is_nullable => 1 },
hydra * remove trailing spaces from email notification * option to disable email notification for jobset
2010-01-06 13:07:59 +00:00
"enabled",
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
{ data_type => "integer", default_value => 1, is_nullable => 0 },
hydra * remove trailing spaces from email notification * option to disable email notification for jobset
2010-01-06 13:07:59 +00:00
"enableemail",
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
{ data_type => "integer", default_value => 1, is_nullable => 0 },
added hide feature for project/jobset
2010-06-04 14:43:28 +00:00
"hidden",
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
{ data_type => "integer", default_value => 0, is_nullable => 0 },
hydra * remove trailing spaces from email notification * option to disable email notification for jobset
2010-01-06 13:07:59 +00:00
"emailoverride",
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
{ data_type => "text", is_nullable => 0 },
hydra: make nr of build to keep configurable per jobset
2010-08-10 06:48:45 +00:00
"keepnr",
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
{ data_type => "integer", default_value => 3, is_nullable => 0 },
Allow a per-jobset check interval This allows checking a jobset (say) at most once a day. It's also possible to disable polling by setting the interval to 0. This is useful for jobsets that use push notification or are manually evaluated.
2013-05-02 17:51:38 +02:00
"checkinterval",
{ data_type => "integer", default_value => 300, is_nullable => 0 },
hydra-queue-runner: Improved scheduling Each jobset now has a "scheduling share" that determines how much of the build farm's time it is entitled to. For instance, if a jobset has 100 shares and the total number of shares of all jobsets is 1000, it's entitled to 10% of the build farm's time. When there is a free build slot for a given system type, the queue runner will select the jobset that is furthest below its scheduling share over a certain time window (currently, the last day). Withing that jobset, it will pick the build with the highest priority. So meta.schedulingPriority now only determines the order of builds within a jobset, not between jobsets. This makes it much easier to prioritise one jobset over another (e.g. nixpkgs:trunk over nixpkgs:stdenv).
2013-09-21 14:47:52 +00:00
"schedulingshares",
{ data_type => "integer", default_value => 100, is_nullable => 0 },
Distinguish between permanent evaluation errors and transient input errors Fixes #112.
2013-09-25 16:21:16 +02:00
"fetcherrormsg",
{ data_type => "text", is_nullable => 1 },
When manually scheduling an eval, force re-instantiation of store derivations 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.
2016-10-24 20:20:20 +02:00
"forceeval",
{ data_type => "boolean", is_nullable => 1 },
hydra-evaluator improvements * The "Jobset" page now shows when evaluations are in progress (rather than just pending). * Restored the ability to do a single evaluation from the command line by doing "hydra-evaluator <project> <jobset>". * Fix some consistency issues between jobset status in PostgreSQL and in hydra-evaluator. In particular, "lastCheckedTime" was never updated internally.
2017-03-13 16:19:22 +01:00
"starttime",
{ data_type => "integer", is_nullable => 1 },
Copy the flake migration from the flake branch hydra.nixos.org is already running this rev, and it should be safe to apply to everyone else. If we make changes to this migration, we'll need to write another migration anyway.
2020-02-09 15:17:24 -05:00
"type",
{ data_type => "integer", default_value => 0, is_nullable => 0 },
"flake",
{ data_type => "text", is_nullable => 1 },
hydra * remove trailing spaces from email notification * option to disable email notification for jobset
2010-01-06 13:07:59 +00:00
);
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
=head1 PRIMARY KEY
hydra * remove trailing spaces from email notification * option to disable email notification for jobset
2010-01-06 13:07:59 +00:00
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
=over 4
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
=item * L</project>
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
=item * L</name>
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
=back
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
=cut
hydra * remove trailing spaces from email notification * option to disable email notification for jobset
2010-01-06 13:07:59 +00:00
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
__PACKAGE__->set_primary_key("project", "name");
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
Jobsets: add a SERIAL, unique, non-null id column A postgresql column which is non-null and unique is treated with the same optimisations as a primary key, so we have no need to try and recreate the `id` as the primary key. No read paths are impacted by this change, and the database will automatically create an ID for each insert. Thus, no code needs to change.
2020-02-05 14:06:21 -05:00
=head1 UNIQUE CONSTRAINTS
=head2 C<jobsets_id_unique>
=over 4
=item * L</id>
=back
=cut
__PACKAGE__->add_unique_constraint("jobsets_id_unique", ["id"]);
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
=head1 RELATIONS
Add support for tracking custom metrics Builds can now emit metrics that Hydra will store in its database and render as time series via flot charts. Typical applications are to keep track of performance indicators, coverage percentages, artifact sizes, and so on. For example, a coverage build can emit the coverage percentage as follows: echo "lineCoverage $pct %" > $out/nix-support/hydra-metrics Graphs of all metrics for a job can be seen at http://.../job/<project>/<jobset>/<job>#tabs-charts Specific metrics are also visible at http://.../job/<project>/<jobset>/<job>/metric/<metric> The latter URL also allows getting the data in JSON format (e.g. via "curl -H 'Accept: application/json'").
2015-07-31 00:57:30 +02:00
=head2 buildmetrics
Type: has_many
DBIx::Class: migrate to use_namespaces This gives us a place to put helper functions that act on entire tables, not just individual records. This should be a backwards compatible change, except in places we're manually using result class names.
2021-08-26 12:03:00 -04:00
Related object: L<Hydra::Schema::Result::BuildMetrics>
Add support for tracking custom metrics Builds can now emit metrics that Hydra will store in its database and render as time series via flot charts. Typical applications are to keep track of performance indicators, coverage percentages, artifact sizes, and so on. For example, a coverage build can emit the coverage percentage as follows: echo "lineCoverage $pct %" > $out/nix-support/hydra-metrics Graphs of all metrics for a job can be seen at http://.../job/<project>/<jobset>/<job>#tabs-charts Specific metrics are also visible at http://.../job/<project>/<jobset>/<job>/metric/<metric> The latter URL also allows getting the data in JSON format (e.g. via "curl -H 'Accept: application/json'").
2015-07-31 00:57:30 +02:00
=cut
__PACKAGE__->has_many(
"buildmetrics",
DBIx::Class: migrate to use_namespaces This gives us a place to put helper functions that act on entire tables, not just individual records. This should be a backwards compatible change, except in places we're manually using result class names.
2021-08-26 12:03:00 -04:00
"Hydra::Schema::Result::BuildMetrics",
Add support for tracking custom metrics Builds can now emit metrics that Hydra will store in its database and render as time series via flot charts. Typical applications are to keep track of performance indicators, coverage percentages, artifact sizes, and so on. For example, a coverage build can emit the coverage percentage as follows: echo "lineCoverage $pct %" > $out/nix-support/hydra-metrics Graphs of all metrics for a job can be seen at http://.../job/<project>/<jobset>/<job>#tabs-charts Specific metrics are also visible at http://.../job/<project>/<jobset>/<job>/metric/<metric> The latter URL also allows getting the data in JSON format (e.g. via "curl -H 'Accept: application/json'").
2015-07-31 00:57:30 +02:00
{
"foreign.jobset" => "self.name",
"foreign.project" => "self.project",
},
undef,
);
Builds: add a nullable jobset_id foreign key to Jobsets. Also, adds an explicitly named "builds" accessor to the Jobsets Schema object, which uses the project/jobset name.
2020-02-05 15:11:56 -05:00
=head2 builds_jobset_ids
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
Type: has_many
DBIx::Class: migrate to use_namespaces This gives us a place to put helper functions that act on entire tables, not just individual records. This should be a backwards compatible change, except in places we're manually using result class names.
2021-08-26 12:03:00 -04:00
Related object: L<Hydra::Schema::Result::Builds>
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
=cut
* Basic job info in the database.
2008-11-04 18:23:28 +00:00
__PACKAGE__->has_many(
Builds: add a nullable jobset_id foreign key to Jobsets. Also, adds an explicitly named "builds" accessor to the Jobsets Schema object, which uses the project/jobset name.
2020-02-05 15:11:56 -05:00
"builds_jobset_ids",
DBIx::Class: migrate to use_namespaces This gives us a place to put helper functions that act on entire tables, not just individual records. This should be a backwards compatible change, except in places we're manually using result class names.
2021-08-26 12:03:00 -04:00
"Hydra::Schema::Result::Builds",
Builds: add a nullable jobset_id foreign key to Jobsets. Also, adds an explicitly named "builds" accessor to the Jobsets Schema object, which uses the project/jobset name.
2020-02-05 15:11:56 -05:00
{ "foreign.jobset_id" => "self.id" },
undef,
);
=head2 builds_project_jobsets
Type: has_many
DBIx::Class: migrate to use_namespaces This gives us a place to put helper functions that act on entire tables, not just individual records. This should be a backwards compatible change, except in places we're manually using result class names.
2021-08-26 12:03:00 -04:00
Related object: L<Hydra::Schema::Result::Builds>
Builds: add a nullable jobset_id foreign key to Jobsets. Also, adds an explicitly named "builds" accessor to the Jobsets Schema object, which uses the project/jobset name.
2020-02-05 15:11:56 -05:00
=cut
__PACKAGE__->has_many(
"builds_project_jobsets",
DBIx::Class: migrate to use_namespaces This gives us a place to put helper functions that act on entire tables, not just individual records. This should be a backwards compatible change, except in places we're manually using result class names.
2021-08-26 12:03:00 -04:00
"Hydra::Schema::Result::Builds",
* Support variant builds.
2008-11-06 18:26:29 +00:00
{
"foreign.jobset" => "self.name",
"foreign.project" => "self.project",
},
Remove the logfile and logSize columns from the database It's pointless to store these, since Nix knows where the logs are. Also handle (in fact require) Nix's new log storage scheme. Also some cleanups in the build page.
2013-01-22 22:48:02 +01:00
undef,
* Basic job info in the database.
2008-11-04 18:23:28 +00:00
);
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
=head2 jobsetevals
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
Type: has_many
DBIx::Class: migrate to use_namespaces This gives us a place to put helper functions that act on entire tables, not just individual records. This should be a backwards compatible change, except in places we're manually using result class names.
2021-08-26 12:03:00 -04:00
Related object: L<Hydra::Schema::Result::JobsetEvals>
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
=cut
* Cleaned up the foreign key constraints. * Generate SQLite and PostgreSQL schemas from hydra.sql.
2009-10-21 12:25:43 +00:00
__PACKAGE__->has_many(
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
"jobsetevals",
DBIx::Class: migrate to use_namespaces This gives us a place to put helper functions that act on entire tables, not just individual records. This should be a backwards compatible change, except in places we're manually using result class names.
2021-08-26 12:03:00 -04:00
"Hydra::Schema::Result::JobsetEvals",
jobsetevals: refer to jobset by ID
2021-01-25 14:51:33 -05:00
{ "foreign.jobset_id" => "self.id" },
Remove the logfile and logSize columns from the database It's pointless to store these, since Nix knows where the logs are. Also handle (in fact require) Nix's new log storage scheme. Also some cleanups in the build page.
2013-01-22 22:48:02 +01:00
undef,
* Cleaned up the foreign key constraints. * Generate SQLite and PostgreSQL schemas from hydra.sql.
2009-10-21 12:25:43 +00:00
);
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
=head2 jobsetinputs
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
Type: has_many
DBIx::Class: migrate to use_namespaces This gives us a place to put helper functions that act on entire tables, not just individual records. This should be a backwards compatible change, except in places we're manually using result class names.
2021-08-26 12:03:00 -04:00
Related object: L<Hydra::Schema::Result::JobsetInputs>
generated schema with new dbix class schema loader, grrrrrr
2010-02-25 09:50:04 +00:00
=cut
* Prevent repeated evaluation of a jobset with the same inputs. This should make the Hydra scheduler a lot less CPU-intensive, since it won't run hydra_eval_jobs all the time.
2009-11-17 13:55:22 +00:00
__PACKAGE__->has_many(
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
"jobsetinputs",
DBIx::Class: migrate to use_namespaces This gives us a place to put helper functions that act on entire tables, not just individual records. This should be a backwards compatible change, except in places we're manually using result class names.
2021-08-26 12:03:00 -04:00
"Hydra::Schema::Result::JobsetInputs",
* Prevent repeated evaluation of a jobset with the same inputs. This should make the Hydra scheduler a lot less CPU-intensive, since it won't run hydra_eval_jobs all the time.
2009-11-17 13:55:22 +00:00
{
"foreign.jobset" => "self.name",
"foreign.project" => "self.project",
},
Remove the logfile and logSize columns from the database It's pointless to store these, since Nix knows where the logs are. Also handle (in fact require) Nix's new log storage scheme. Also some cleanups in the build page.
2013-01-22 22:48:02 +01:00
undef,
* Prevent repeated evaluation of a jobset with the same inputs. This should make the Hydra scheduler a lot less CPU-intensive, since it won't run hydra_eval_jobs all the time.
2009-11-17 13:55:22 +00:00
);
* Basic job info in the database.
2008-11-04 18:23:28 +00:00
When renaming a jobset, add a redirect from the old name
2014-04-23 23:12:00 +02:00
=head2 jobsetrenames
Type: has_many
DBIx::Class: migrate to use_namespaces This gives us a place to put helper functions that act on entire tables, not just individual records. This should be a backwards compatible change, except in places we're manually using result class names.
2021-08-26 12:03:00 -04:00
Related object: L<Hydra::Schema::Result::JobsetRenames>
When renaming a jobset, add a redirect from the old name
2014-04-23 23:12:00 +02:00
=cut
__PACKAGE__->has_many(
"jobsetrenames",
DBIx::Class: migrate to use_namespaces This gives us a place to put helper functions that act on entire tables, not just individual records. This should be a backwards compatible change, except in places we're manually using result class names.
2021-08-26 12:03:00 -04:00
"Hydra::Schema::Result::JobsetRenames",
When renaming a jobset, add a redirect from the old name
2014-04-23 23:12:00 +02:00
{ "foreign.project" => "self.project", "foreign.to_" => "self.name" },
undef,
);
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
=head2 project
Type: belongs_to
DBIx::Class: migrate to use_namespaces This gives us a place to put helper functions that act on entire tables, not just individual records. This should be a backwards compatible change, except in places we're manually using result class names.
2021-08-26 12:03:00 -04:00
Related object: L<Hydra::Schema::Result::Projects>
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
=cut
Remove the logfile and logSize columns from the database It's pointless to store these, since Nix knows where the logs are. Also handle (in fact require) Nix's new log storage scheme. Also some cleanups in the build page.
2013-01-22 22:48:02 +01:00
__PACKAGE__->belongs_to(
"project",
DBIx::Class: migrate to use_namespaces This gives us a place to put helper functions that act on entire tables, not just individual records. This should be a backwards compatible change, except in places we're manually using result class names.
2021-08-26 12:03:00 -04:00
"Hydra::Schema::Result::Projects",
Remove the logfile and logSize columns from the database It's pointless to store these, since Nix knows where the logs are. Also handle (in fact require) Nix's new log storage scheme. Also some cleanups in the build page.
2013-01-22 22:48:02 +01:00
{ name => "project" },
{ is_deferrable => 0, on_delete => "CASCADE", on_update => "CASCADE" },
);
Keep track of the database schema version The singleton table SchemaVersion contains the current version of the Hydra database schema. This can be used to upgrade the schema on the fly. Also reran the DBIx::Class schema loader.
2011-12-05 14:29:29 +01:00
Add a dashboard Currently the dashboard allows users to get a quick overview of the status of jobs they're interested in, but more will be added, e.g. viewing all your jobsets or all jobs of which you're a maintainer.
2013-10-14 20:07:26 +02:00
=head2 starredjobs
* Basic job info in the database.
2008-11-04 18:23:28 +00:00
Add a dashboard Currently the dashboard allows users to get a quick overview of the status of jobs they're interested in, but more will be added, e.g. viewing all your jobsets or all jobs of which you're a maintainer.
2013-10-14 20:07:26 +02:00
Type: has_many
DBIx::Class: migrate to use_namespaces This gives us a place to put helper functions that act on entire tables, not just individual records. This should be a backwards compatible change, except in places we're manually using result class names.
2021-08-26 12:03:00 -04:00
Related object: L<Hydra::Schema::Result::StarredJobs>
Add a dashboard Currently the dashboard allows users to get a quick overview of the status of jobs they're interested in, but more will be added, e.g. viewing all your jobsets or all jobs of which you're a maintainer.
2013-10-14 20:07:26 +02:00
=cut
__PACKAGE__->has_many(
"starredjobs",
DBIx::Class: migrate to use_namespaces This gives us a place to put helper functions that act on entire tables, not just individual records. This should be a backwards compatible change, except in places we're manually using result class names.
2021-08-26 12:03:00 -04:00
"Hydra::Schema::Result::StarredJobs",
Add a dashboard Currently the dashboard allows users to get a quick overview of the status of jobs they're interested in, but more will be added, e.g. viewing all your jobsets or all jobs of which you're a maintainer.
2013-10-14 20:07:26 +02:00
{
"foreign.jobset" => "self.name",
"foreign.project" => "self.project",
},
undef,
);
DBIx::Class: migrate to use_namespaces This gives us a place to put helper functions that act on entire tables, not just individual records. This should be a backwards compatible change, except in places we're manually using result class names.
2021-08-26 12:03:00 -04:00
# Created by DBIx::Class::Schema::Loader v0.07049 @ 2021-08-26 12:02:36
# DO NOT MODIFY THIS OR ANYTHING ABOVE! md5sum:iI44C3BFTo6IsS1tBwWYsg
Builds: add a nullable jobset_id foreign key to Jobsets. Also, adds an explicitly named "builds" accessor to the Jobsets Schema object, which uses the project/jobset name.
2020-02-05 15:11:56 -05:00
Jobsets,JobsetInputs: use JSON
2021-04-29 08:32:47 -04:00
use JSON;
Builds: add a nullable jobset_id foreign key to Jobsets. Also, adds an explicitly named "builds" accessor to the Jobsets Schema object, which uses the project/jobset name.
2020-02-05 15:11:56 -05:00
=head2 builds
Type: has_many
DBIx::Class: migrate to use_namespaces This gives us a place to put helper functions that act on entire tables, not just individual records. This should be a backwards compatible change, except in places we're manually using result class names.
2021-08-26 12:03:00 -04:00
Related object: L<Hydra::Schema::Result::Builds>
Builds: add a nullable jobset_id foreign key to Jobsets. Also, adds an explicitly named "builds" accessor to the Jobsets Schema object, which uses the project/jobset name.
2020-02-05 15:11:56 -05:00
=cut
__PACKAGE__->has_many(
"builds",
DBIx::Class: migrate to use_namespaces This gives us a place to put helper functions that act on entire tables, not just individual records. This should be a backwards compatible change, except in places we're manually using result class names.
2021-08-26 12:03:00 -04:00
"Hydra::Schema::Result::Builds",
Jobsets.builds: Fetch via Jobsets.id
2020-02-05 16:35:39 -05:00
{ "foreign.jobset_id" => "self.id" },
Builds: add a nullable jobset_id foreign key to Jobsets. Also, adds an explicitly named "builds" accessor to the Jobsets Schema object, which uses the project/jobset name.
2020-02-05 15:11:56 -05:00
undef,
);
Jobs: add a nullable jobset_id foreign key to Jobsets. Also, adds an explicitly named "jobs" accessor to the Jobsets Schema object, which uses the project/jobset name.
2020-02-05 17:10:50 -05:00
Jobsets: add a SERIAL, unique, non-null id column A postgresql column which is non-null and unique is treated with the same optimisations as a primary key, so we have no need to try and recreate the `id` as the primary key. No read paths are impacted by this change, and the database will automatically create an ID for each insert. Thus, no code needs to change.
2020-02-05 14:06:21 -05:00
__PACKAGE__->add_column(
"+id" => { retrieve_on_insert => 1 }
);
hydra * remove trailing spaces from email notification * option to disable email notification for jobset
2010-01-06 13:07:59 +00:00
Jobsets: update schema to align with the API To further align with the API, we return custom JSON in order to display a `visible` field rather than `hidden` -- a `PUT` request expects `visible`, while a `GET` request returns `hidden`. This also allows us to rename the `jobsetinputs` field to `inputs` for the same reason: `PUT` expects `inputs`, while `GET` returns `jobsetinputs`.
2021-04-28 12:41:05 -07:00
sub as_json {
my $self = shift;
my %json = (
# columns
"errortime" => $self->get_column("errortime"),
"lastcheckedtime" => $self->get_column("lastcheckedtime"),
"triggertime" => $self->get_column("triggertime"),
"enabled" => $self->get_column("enabled"),
"keepnr" => $self->get_column("keepnr"),
"checkinterval" => $self->get_column("checkinterval"),
"schedulingshares" => $self->get_column("schedulingshares"),
"starttime" => $self->get_column("starttime"),
# string_columns
"name" => $self->get_column("name") // "",
"project" => $self->get_column("project") // "",
"description" => $self->get_column("description") // "",
"nixexprinput" => $self->get_column("nixexprinput") // "",
"nixexprpath" => $self->get_column("nixexprpath") // "",
"errormsg" => $self->get_column("errormsg") // "",
"emailoverride" => $self->get_column("emailoverride") // "",
"fetcherrormsg" => $self->get_column("fetcherrormsg") // "",
"type" => $self->get_column("type") // "",
"flake" => $self->get_column("flake") // "",
# boolean_columns
"enableemail" => $self->get_column("enableemail") ? JSON::true : JSON::false,
"visible" => $self->get_column("hidden") ? JSON::false : JSON::true,
"inputs" => { map { $_->name => $_ } $self->jobsetinputs }
);
return \%json;
Cleanup Jobset serialization Signed-off-by: Shea Levy <shea@shealevy.com>
2013-10-24 11:01:17 -04:00
}
* Basic job info in the database.
2008-11-04 18:23:28 +00:00
1;
Reference in New Issue Copy Permalink