public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Announcing nightly builds for IPFire 2
Date: Wed, 09 Sep 2015 15:20:25 +0100	[thread overview]
Message-ID: <1441808425.5798.35.camel@ipfire.org> (raw)
In-Reply-To: <612747433a445b235ad82760c9443a68@beert.de>

[-- Attachment #1: Type: text/plain, Size: 1846 bytes --]

Hi,

On Tue, 2015-09-08 at 09:02 +0200, Benjamin Schweikert wrote:
> Hi,
> this sounds great! Are you doing a ./make.sh clean before building
> new stuff, or are you "just" building the changed parts?

no, this is a fresh build from the start. The system cannot be built in
any other way, but for i586 that does not really hurt us too much since
the build is running at night and takes only 3-4 hours. ARM is
completely different though.

Best,
-Michael

> Best regards
> Ben
> Am 2015-09-07 23:26, schrieb Michael Tremer:
> > Hi,
> > 
> > I wanted to announce that since a few days we have a nightly build
> > service for IPFire 2 again.
> > 
> > This has been built to solve two things:
> > 
> > * First of all we now always have a fresh build. Please use that
> > for
> > testing. Just download it and go. And please do not forget to
> > report
> > any bugs you find.
> > 
> > * We will now know if the distribution builds on all architectures.
> > Many people do not have build hardware for all architectures, but
> > some
> > have devices they can use for testing.
> > 
> > 
> > The builds are available here: http://nightly.ipfire.org/
> > 
> > 
> > Every night at 3:00 AM CET the build server will check if the next
> > branch has any new changes and if so start a build job. A couple of
> > hours later it will upload the build so that everyone has a fresh
> > one
> > early in the morning. ARM builds will take usually longer than 24
> > days
> > though.
> > 
> > Builds will automatically be removed after 7 days. The latest build
> > will always be kept.
> > 
> > This is basically just two scripts doing the job. Nothing too
> > exciting,
> > but we think it will be very helpful. If you have any ideas on how
> > to
> > extend this service let me know. Also any other feedback is
> > appreciated.
> > 
> > Best,
> > -Michael
>  
>  

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

       reply	other threads:[~2015-09-09 14:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <612747433a445b235ad82760c9443a68@beert.de>
2015-09-09 14:20 ` Michael Tremer [this message]
2015-09-07 21:26 Michael Tremer
2015-09-07 23:02 ` Rod Rodolico
2015-09-09 14:19   ` Michael Tremer

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=1441808425.5798.35.camel@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox