< User:Bkabrda | BuildSys
BuildSys Frontend <-> Backend API
Getting Waiting Builds From Frontend
To get 10 oldest submitted builds, use http://deployed_frontend_instance/waiting_builds/ - JSON is returned by default, example response:
{ "builds": [ { "copr_id": 5, "user_id": 1, "results": null, "started_on": null, "copr": { "owner_id": 2, "repos": null, "chroots": "fedora-17-i386 fedora-17-x86_64", "id": 5, "name": "ff2" }, "submitted_on": 1351157544, "ended_on": null, "pkgs": "http://foo/pkg.src.rpm", "id": 5 }, { "copr_id": 3, "user_id": 1, "results": null, "started_on": null, "copr": { "owner_id": 1, "repos": "http://foo/repo http://bar/repo", "chroots": "fedora-rawhide-i386 fedora-rawhide-x86_64", "id": 3, "name": "baz" }, "submitted_on": 1351153692, "ended_on": null, "pkgs": "http://foo/pkg-1.src.rpm http://foo/spam-2.src.rpm", "id": 4 }, ] }
Questions:
* What the repos should be: repofiles or urls of the actual repos? * Do we want separate repos for different chroots in one copr (as in "fedora-rawhide-i386: foo-i386", "fedora-rawhide-x86_64: foo-x86_64") or it doesn't matter?