public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Roy Osherove <roy@osherove.com>
To: Mark Friedenbach <mark@friedenbach.org>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] CI Build for Bitcoin - Some Basic Questions about Gitian and other stuff
Date: Wed, 23 Sep 2015 10:31:22 -0700	[thread overview]
Message-ID: <CAAMhxnw8J8nZbWPBEA9HOfJH0iiWO3uvD_frJ089R1kcbhciSg@mail.gmail.com> (raw)
In-Reply-To: <CAOG=w-uzmC3-2vYbSYDwvDhhP0FyC72G2dBVuj83zBMhqrvGOA@mail.gmail.com>

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

Thanks Mark.
Is there a public server where the gitian builds can be viewed?
Is there a public server that shows the quorum verifications or that shows
how to join in on the verification if such as thing is helpful?

On Wed, Sep 23, 2015 at 10:18 AM, Mark Friedenbach <mark@friedenbach.org>
wrote:

> The builds made by Travis are for the purpose of making sure that the
> source code compiles and tests run successfully on all supported platforms.
> The binaries are not used anywhere else because Travis is not a trusted
> platform.
>
> The binaries on bitcoin.org are built using the gitian process and signed
> by a quorum of developers.
>
> On Wed, Sep 23, 2015 at 10:13 AM, Roy Osherove via bitcoin-dev <
> bitcoin-dev@lists.linuxfoundation.org> wrote:
>
>> Hi Folks.
>> I'm trying my hand at creating a reproducible build of my own for bitcoin
>> and bitcoin-XT, using TeamCity.
>> I believe it is the best way to learn something: To try to build it
>> yourself.
>> Here is what I think I know so far, and I would love corrections, plus
>> questions:
>>
>>    1. Bitcoin is built continuously on travis-CI at
>>    https://travis-ci.org/bitcoin/bitcoin/
>>    2.  there are many flavors that are built, but I'm not sure if all of
>>    them are actually used/necessary. are they all needed, or just to "just in
>>    case"?
>>    3.  There is a gitian build file for bitcoin, but is anyone actually
>>    using it? are the bin files on bitcoin.org taken from that? or the
>>    travis ci builds? or some other place?
>>    4. Are there any things that people would love to have in the build
>>    that do not exist there today? perhaps I can help with that?
>>
>> Here is what I have now: http://btcdev.osherove.com:8111/
>> It does not do the matrix build yet, but it's coming. I'm just wondering
>> if all the platforms need to be supported,and if gitian is truly required
>> to be used, or used in parallel, or at all..
>>
>> Feedback appreciated.
>>
>> --
>> Thanks,
>>
>> Roy Osherove
>>
>>    - *@RoyOsherove* <https://twitter.com/RoyOsherove>
>>    - Read my new book *Notes to a Software Team Leader
>> <http://TeamLeadSkills.com>*
>>    - Or *my new course* about Beautiful Builds
>> <http://courses.osherove.com> and Continuous Delivery
>>    - +1-201-256-5575
>>
>>
>>
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev@lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>
>>
>


-- 
Thanks,

Roy Osherove

   - *@RoyOsherove* <https://twitter.com/RoyOsherove>
   - Read my new book *Notes to a Software Team Leader
<http://TeamLeadSkills.com>*
   - Or *my new course* about Beautiful Builds <http://courses.osherove.com>
and Continuous Delivery
   - +1-201-256-5575
    - Timezone: Eastern Standard Time (New York)

[-- Attachment #2: Type: text/html, Size: 4701 bytes --]

  reply	other threads:[~2015-09-23 17:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-23 17:13 [bitcoin-dev] CI Build for Bitcoin - Some Basic Questions about Gitian and other stuff Roy Osherove
2015-09-23 17:18 ` Mark Friedenbach
2015-09-23 17:31   ` Roy Osherove [this message]
2015-09-23 18:10     ` Mark Friedenbach
2015-09-23 20:54       ` Roy Osherove
2015-09-24  9:18         ` Jonas Schnelli

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=CAAMhxnw8J8nZbWPBEA9HOfJH0iiWO3uvD_frJ089R1kcbhciSg@mail.gmail.com \
    --to=roy@osherove.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=mark@friedenbach.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