For schema upgrades, hydra-init executes the files src/sql/upgrade-<N>.sql, each of which upgrades the schema from version N-1 to N. The upgrades are wrapped in a transaction.
E.g. http://server/build/1341335/api/get-info returns a JSON record containing information about the build.
to predict how much disk space a package will require. * Compute the output / closure size using the info stored in the Nix database (rather than doing a slow "du").
…em)' to allow better continous integration in one jobset for multiple system. it makes sure that the system of the build that is passed as input for a job has the same system as the job.
3 environment variables are important: TWITTER_USER TWITTER_PASS HYDRA_BUILD_BASEURL - twitter notification is off when TWITTER_USER and TWITTER_PASS are not defined - if HYDRA_BUILD_BASEURL is not defined, no URL is put in the twitter messages
profile for easy testing.