public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sam Bishop <sam@cygnus.email>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] CI Continuous Integration
Date: Wed, 17 Dec 2014 11:59:17 +0800	[thread overview]
Message-ID: <CAC9sXgndUXxBitZNnKXVcbN6S5NXzUFpaCyCnrzQQsuSY0A2Yg@mail.gmail.com> (raw)
In-Reply-To: <loom.20141216T180816-985@post.gmane.org>

Very interesting. A great example of how something can be both Gentoo
and Not Gentoo. This is 100% Gentoo unlike Funtoo or Sabayon, but it
brings in some of their advantages. Gentoo doesn't prevent us from
having multiple package variants and this leads to cool stuff like
being able to have a set of layman repositories that ebuilds graduate
through in stages, from 'dev' to 'test' to 'stable'.

And this is why I feel so strongly about Gentoo + Git + CI
While github may not be the right place and raw 'git' not the right
tool. I am a big fan of how phabricator + arcanist provides workflow
guarantees on top of using git, such as the 'must pass the linter
rules + tests' workflow and how it can track and reference external
repos side by side with the repos it hosts.

I feel the future belongs to Gentoo as steward of the ebuild format,
portage and related tools more than as a 'meta distro'. CI is the
force multiplier, when anyone who wants to build a "Gentoo powered
distro" has a documented set of tools they can use to 'stand up the
infrastructure' for things like package QA using a CI Server, a Binary
Package build server/server farm, and Binary Package hosting for the
build artefacts. By rights Gentoo not Debian, Arch or Fedora should be
the Distro of choice for creating experimental niche distros from but
we lack the kind of tools to make it 'easy' for people to do. I'm
currently experimenting to see how many of these I can prototype
inside Docker containers or LXC images and it looks quite promising.

The future looks bright for Gentoo. :-)


On 17 December 2014 at 01:15, James <wireless@tampabay.rr.com> wrote:
> Well,
>
> For all of those who are interested in Continuous Integration, especially
> with the demise of Tinderbox, Look at what I just stumbled (googling)
> across
>
>
> "Zentoo Linux also provides a bunch of experimental overlays for special
> setups (like Continuous Integration system needing X11 and browsers) and for
> testing experimental new packages. "
>
>
> [1] http://www.zentoo.org/
>
>
> I have not had a chance to look it over, but at first glance it seems
> some folks are already taking  (CI) ideas to the next level?
>
>
> interesting,
> James
>
>


  reply	other threads:[~2014-12-17  3:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-16 17:15 [gentoo-user] CI Continuous Integration James
2014-12-17  3:59 ` Sam Bishop [this message]
2014-12-17 15:37   ` [gentoo-user] " James
2014-12-18  6:25     ` Sam Bishop
2014-12-18  9:07       ` Alan McKinnon

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=CAC9sXgndUXxBitZNnKXVcbN6S5NXzUFpaCyCnrzQQsuSY0A2Yg@mail.gmail.com \
    --to=sam@cygnus.email \
    --cc=gentoo-user@lists.gentoo.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