| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
This is to allow for build servers where only the substitutes should be
queried, and it shouldn't be assumed that they're running Cuirass.
|
|
|
|
|
|
| |
Turns out, at the moment, this is ineffective when combined with the archive
formats, like the custom format in use. Therefore, move it to the pg_restore
command, where hopefully it'll work.
|
|
|
|
|
|
|
|
|
|
|
| |
This is a comprimise, as this won't help restoring the backup in situations
you want tablespaces, but I'm currently viewing tablespaces as a deployment
concern, so maybe the right thing to do is exclude them. This approach will at
least keep the same behaviour in terms of restoring the backups locally.
This will fix the small dump creation process on data.guix.gnu.org, which is
currently broken because of the tablespace assignments when trying to restore
the backups.
|
|
|
|
|
|
| |
These are related things, but somewhat separate. This change should make it
easier to deal with changes regarding querying build servers, and querying
substitute servers.
|
|
|
|
|
| |
This will help stop queries running for an unnecessarily long time, longer
than NGinx will wait for example.
|
|
|
|
|
|
| |
This is better than just deleting the entries that don't match up with the
remaining revisions, but also not very useful for local development (due to
the lack of data).
|
|
|
|
| |
In the hope that this makes the script faster.
|
|
|
|
|
| |
In the create-small-backup script, as this is quite a slow part, it's useful
to get more information.
|
|
|
|
|
| |
derivation_output_details_sets, and derivations_by_output_details_set. This
required moving around some of the code.
|
|
|
|
|
|
|
|
|
|
| |
Hopefully this will help with the pg_restore in the create-small-backup
script:
pg_restore: [archiver (db)] Error while PROCESSING TOC:
pg_restore: [archiver (db)] Error from TOC entry 2875; 0 0 COMMENT EXTENSION plpgsql
pg_restore: [archiver (db)] could not execute query: ERROR: must be owner of extension plpgsql
Command was: COMMENT ON EXTENSION plpgsql IS 'PL/pgSQL procedural language';
|
|
|
|
| |
Otherwise this table is empty.
|
|
|
|
| |
Otherwise this table is empty.
|
|
|
|
| |
It's been replaced by the package_derivations_by_guix_revision_range table.
|
|
|
|
|
| |
These parts of the backup scripts are optional, so don't fail if they don't
work.
|
|
|
|
| |
Move it after the output relating to narinfo signing, and include the host.
|
|
|
|
|
| |
Adjust the previously unused error page code, and start to use it. Only show
the error if configured to do so, to avoid leaking secret information.
|
|
|
|
| |
As it makes it clearer what tables will be truncated.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This makes it possible to set a higher or lower value depending on what you
want.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
So you can select to query specific build servers.
|
|
|
|
|
| |
As well as making it possible to only query build servers for builds relating
to a specific revision.
|
|
|
|
|
|
|
| |
Allow for build status information to be submitted by POST request. This
required some changes to the builds and build_status tables, as for example,
the Cuirass build id may not be available, and the derivation may not be know
yet, so just record the derivation file name.
|
|
|
|
|
| |
This computes and displays the tokens needed to send build events to the Guix
Data Service.
|
|
|
|
| |
As this means that like psql, the unix socket will be used.
|
|
|
|
|
| |
This can be used with the mbox files for the guix-commits mailing list to add
older emails in to the database.
|
|
|
|
|
| |
This is better, as different parts of the email might be encoded differently,
and guile-email will take care of this if handed a bytevector.
|
| |
|
|
|
|
|
|
| |
This allows easily processing an individual job by id. This may be useful to
use manually, but also when processing jobs in parallel, as forking doesn't
work well with the libpq library used by squee.
|
|
|
|
| |
This helps when working out which connection to the database is doing what.
|
|
|
|
|
| |
As these are used for logging, which is done on a line by line basis. Remove
the now redundant calls to (force-output).
|
| |
|
|
|
|
|
| |
This'll help the a service manager (like the shepherd) know when the service
is ready, which at the moment, means the database migrations have happened.
|
|
|
|
| |
As this means it can find the relevant files.
|
|
|
|
| |
So that it can always find psql.
|
| |
|
|
|
|
|
|
| |
This runs Sqitch on startup, which should make managing the database easier,
as you just have to restart the service with this option, and the database
should be updated if necessary.
|
| |
|
| |
|
|
|
|
| |
It should never have been committed.
|