From: ludo@gnu.org (Ludovic Courtès)
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel@gnu.org
Subject: Re: Build passing status icon
Date: Wed, 16 Sep 2015 13:32:25 +0200 [thread overview]
Message-ID: <87fv2ed2gm.fsf@gnu.org> (raw)
In-Reply-To: <20150916043716.GA5617@thebird.nl> (Pjotr Prins's message of "Wed, 16 Sep 2015 06:37:16 +0200")
Pjotr Prins <pjotr.public12@thebird.nl> skribis:
> On Tue, Sep 15, 2015 at 09:05:46PM +0200, Ludovic Courtès wrote:
>> It turns out that Hydra has a bunch of things under
>> lib/Hydra/Controller/API.pm¹. For example:
>>
>> http://hydra.gnu.org/api/latestbuilds?nr=10
>>
>> { "project":"gnu",
>> "timestamp":1442315120,
>> "nixname":"gcr-3.16.0",
>> "job":"gcr-3.16.0.mips64el-linux",
>> "system":"mips64el-linux",
>> "finished":1,
>> "buildstatus":2,
>> "nixname":"core-updates",
>> "id":683368 }
>>
>> The meaning of the “buildstatus” value is given in hydra-postgresql.sql:
>>
>> -- Status codes:
>> -- 0 = succeeded
>> -- 1 = build of this derivation failed
>> -- 2 = build of some dependency failed
>> -- 3 = other failure (see errorMsg)
>> -- 4 = build cancelled (removed from queue; never built)
>> -- 5 = build not done because a dependency failed previously (obsolete)
>> buildStatus integer,
>>
>> So it’s possible to query the build status of some of the latest builds.
>>
>> However, we’d need a different URL to get what you want. That seems to
>> be quite simple to do. Would you or someone else be willing to hack on
>> this?
>
> I think that if sub latestbuilds simply accepts a nixname we are set!
Oh actually there’s nothing to do: just fetch
http://hydra.gnu.org/api/latestbuilds?nr=1&project=gnu&jobset=master&job=ruby-2.2.3.x86_64-linux
Ludo’.
prev parent reply other threads:[~2015-09-16 11:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 8:10 Build passing status icon Pjotr Prins
2015-07-31 17:00 ` Thompson, David
2015-09-15 13:24 ` Pjotr Prins
2015-09-15 19:05 ` Ludovic Courtès
2015-09-16 4:37 ` Pjotr Prins
2015-09-16 11:32 ` Ludovic Courtès [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fv2ed2gm.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=pjotr.public12@thebird.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).