From: Luis Felipe <luis.felipe.la@protonmail.com>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Cuirass badges
Date: Fri, 28 May 2021 16:49:41 +0000 [thread overview]
Message-ID: <OpLRh7tFfvzDMsi-AAHupnAW_gq_driaHkS-rp3IhbvHpH627SvkYnzd2sUzc04H1PZ5699n4qg9iYP-eBWWrD-8ypc4tqHjCWbz23CMiH8=@protonmail.com> (raw)
In-Reply-To: <87lf7zf1h6.fsf@gnu.org>
On Friday, May 28, 2021 1:10 PM, Mathieu Othacehe <othacehe@gnu.org> wrote:
> Hello,
>
> Cuirass is now able to generate badges like any respectable CI
> system. For instance:
>
> - https://ci.guix.gnu.org/jobset/master/badge generates a badge showing
> the percentage of successful jobs for the master specification.
>
> - https://ci.guix.gnu.org/jobset/guix/badge generates a badge showing
> the percentage of successful jobs for the guix specification.
>
> You can integrate those badges in your Git forge. There's a screenshot
> of a Gitlab integration attached.
>
> I think that the badge design[1] could be significantly improved by
> anyone with artistic abilities. It would also be nice if the badge could
> display the specification name so that badges corresponding to multiple
> specifications can be displayed together.
>
> Thanks,
>
> Mathieu
>
> [1]:
> https://git.savannah.gnu.org/cgit/guix/guix-cuirass.git/tree/src/static/images/badge-per.svg
>
I'm giving this a try.
next prev parent reply other threads:[~2021-05-28 16:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 13:10 Cuirass badges Mathieu Othacehe
2021-05-28 16:49 ` Luis Felipe [this message]
2021-05-28 19:24 ` Luis Felipe
2021-05-28 19:34 ` Leo Famulari
2021-05-30 8:28 ` Mathieu Othacehe
2021-06-08 13:07 ` Ludovic Courtès
2021-06-09 12:27 ` Mathieu Othacehe
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='OpLRh7tFfvzDMsi-AAHupnAW_gq_driaHkS-rp3IhbvHpH627SvkYnzd2sUzc04H1PZ5699n4qg9iYP-eBWWrD-8ypc4tqHjCWbz23CMiH8=@protonmail.com' \
--to=luis.felipe.la@protonmail.com \
--cc=guix-devel@gnu.org \
--cc=othacehe@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.