From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [POC] buildroot packages site
Date: Fri, 3 Jan 2020 13:46:07 +0100 [thread overview]
Message-ID: <20200103134607.1b6a7f55@windsurf> (raw)
In-Reply-To: <CAEyMn7YbbC+Nb0PbvFsS=BMh7aEi_nLZaOSS4URYzqfrzwUoYg@mail.gmail.com>
Hello,
On Fri, 3 Jan 2020 13:33:28 +0100
Heiko Thiery <heiko.thiery@gmail.com> wrote:
> > Wow, that's really nice. We definitely want to deploy this as a
> > replacement to http://autobuild.buildroot.org/stats/. Perhaps we should
> > even promote this to http://stats.buildroot.org/ or something like that.
>
> This sounds good :-)
OK, let's work on getting this in place. We need to sync with Peter
Korsgaard to see how it can be deployed on the existing infrastructure.
> > One question: how did you collect the stats history at
> > http://packages.buildroot.thiery.it/packages/stats?commit=198bdaadd03f75fe959c21089c354d36c90069bc ?
>
> Fist I have a cron job that does updates the latest.json in a fixed
> interval (e.g. every hour). In addition I use that output and strip
> the packages stuff from the json with jq and only store the stats part
> of the output for every day.
> For having the stats back in the past I have a script that does a
> checkout for every day in the past and generates this stats output.
OK, sounds good. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-01-03 12:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-03 10:48 [Buildroot] [POC] buildroot packages site Heiko Thiery
2020-01-03 10:59 ` Giulio Benetti
2020-01-03 11:08 ` Heiko Thiery
2020-01-03 14:19 ` Giulio Benetti
2020-01-03 12:26 ` Thomas Petazzoni
2020-01-03 12:33 ` Heiko Thiery
2020-01-03 12:46 ` Thomas Petazzoni [this message]
2020-01-09 14:58 ` Heiko Thiery
2020-01-09 15:12 ` Thomas Petazzoni
2020-01-03 14:46 ` Thomas Petazzoni
2020-01-03 14:57 ` Heiko Thiery
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=20200103134607.1b6a7f55@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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.
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.