Data storage functionality
Data storage functionality
(build-exists? s sid)
Checks efficiently if the build exists. This is cheaper than trying to fetch it
and checking if the result is nil
.
Checks efficiently if the build exists. This is cheaper than trying to fetch it and checking if the result is `nil`.
(create-build-metadata s md)
(create-build-metadata s sid md)
(find-build-metadata s sid)
Reads the build metadata given the build coordinates (required to build the path)
Reads the build metadata given the build coordinates (required to build the path)
(find-build-results s sid)
Reads the build results given the build coordinates
Reads the build results given the build coordinates
(find-repo s [cust-id id])
Reads the repo, as part of the customer object's projects
Reads the repo, as part of the customer object's projects
(legacy-build-exists? s sid)
Similar to build-exists?
but for legacy builds that consist of metadata and
result entities.
Similar to `build-exists?` but for legacy builds that consist of metadata and result entities.
(list-builds s sid)
Lists the ids of the builds for given repo sid
Lists the ids of the builds for given repo sid
(patch-build-results st sid f & args)
Finds the build result with given sid, then applies f
to it with arguments
and saves the return value back into the result.
Finds the build result with given sid, then applies `f` to it with arguments and saves the return value back into the result.
(save-build s build)
Creates or updates the build entity
Creates or updates the build entity
(save-repo s {:keys [customer-id id] :as r})
Saves the repository by updating the customer it belongs to
Saves the repository by updating the customer it belongs to
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close