| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
This is mostly a workaround for the occasional problems with the guix-commits
mailing list, as it can break and then the data service doesn't learn about
new revisions until the problem is fixed.
I think it's still a generally good feature though, and allows deploying the
data service without it consuming emails to learn about new revisions, and is
a step towards integrating some kind of way of notifying the data service to
poll.
|
| |
|
|
|
| |
This is so that data.qa.guix.gnu.org can be configured only to query the
branches from the main repository.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
And create a proper git_branches table in the process.
I'm hoping this will help with slow deletions from the
package_derivations_by_guix_revision_range table in the case where there are
lots of branches, since it'll separate the data for one branch from another.
These migrations will remove the existing data, so
rebuild-package-derivations-table will currently need manually running to
regenerate it.
|
| |
|
|
| |
While maintaining compatibility for older versions of squee.
|
| |
|
|
| |
To allow using the Guix Data Service when commits aren't authenticated.
|
| |
|
|
|
| |
So that you can have the Guix Data Service only pay attention to some of the
branches.
|
| | |
|
| |
|
|
|
| |
Rather than expecting it always to be "guix", store the expected value in the
database, and use the value of the header to find the relevant repository.
|
| |
|
|
| |
That were missing them.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
squee, returns all data as strings, and expects strings as inputs to
queries. So, keeping the ids as strings was easy initially, but it means that
you can't tell from the type whether it should be quoted, or not...
Therefore, handle ids as strings, converting them to numbers when they're
fetched from the database, and back to strings as part of the queries.
|
| | |
|
| |
|
|
|
| |
Make the link between repositories and branches clearer, replacing the
/branches and /branch pages by /repository/ and /repository/*/branch/* pages.
|
| |
|
|
|
| |
Also flip the branch and revision columns around, and add date information to
the branch column.
|
| |
|
|
|
|
| |
I'm not sure quite how to treat these yet, but for now, just stick with the
previous behaviour of showing revisions which haven't been processed yet,
along with the ones that have been successfully processed.
|
| |
|
|
|
|
|
|
| |
Create a new events table for the new guix revision jobs, and update this when
processing a job starts, as well as finished with success or failure.
Additionally, remove the dependnency on open-inferior/container, as this
functionality isn't merged in to Guix master yet.
|
| |
|
|
| |
So at least they're stable.
|
| |
|
|
|
|
|
| |
Store the location a package can be found at, and display this on the package
page.
If available, link off to the git repository containing the package.
|
|
|
Rather than just storing the URL in the guix_revisions and
load_new_guix_revision_jobs tables. This will help when storing more
information like tags and branches in the future.
|