From: Carlos O'Donell <carlos@redhat.com>
To: Tulio Magno Quites Machado Filho <tuliom@linux.vnet.ibm.com>,
Roland McGrath <roland@hack.frob.com>,
"GNU C. Library" <libc-alpha@sourceware.org>
Subject: Re: buildbot status
Date: Mon, 25 Apr 2016 17:24:00 -0000 [thread overview]
Message-ID: <571E52B5.9010400@redhat.com> (raw)
In-Reply-To: <877fft3ab0.fsf@linux.vnet.ibm.com>
On 04/19/2016 11:09 AM, Tulio Magno Quites Machado Filho wrote:
> Tulio Magno Quites Machado Filho <tuliom@linux.vnet.ibm.com> writes:
>
>> Carlos O'Donell <carlos@redhat.com> writes:
>>
>>> On 03/03/2016 05:38 PM, Roland McGrath wrote:
>>>> For the new bugzilla component, I'm automatically CC'd but there is no
>>>> default assignee. I didn't want to imply that I will necessarily jump on
>>>> every buildbot bug filed myself, though I will try to keep track of it.
>>>> Indeed I would very much like to encourage more folks to get involved with
>>>> improving the bot stuff.
>>>
>>> I'd love to just repeat the same process Tulio used :-)
>>>
>>> Tulio,
>>>
>>> Any status on updating the wiki page with more instructions?
>>
>> Sorry. Give me a few more days.
>> I'm validating the steps in a new BuildSlave.
>>
>>> https://sourceware.org/glibc/wiki/Buildbot
>>
>> I'll update this wiki page as I complete each of the steps.
>
> Most of the steps to create a BuildSlave are already documented in our wiki
> page. However, I still have to review step 7, which is the process
> to create a patch adding the BuildSlave. I don't believe it makes sense to
> automate this step, but we should have at least some hints on what needs to
> be changed.
As long as you have hints, thats the best.
> I'm attaching an Ansible playbook as RFC that does the exact same thing
> documented there.
Awesome!
Cheers,
Carlos.
--
Cheers,
Carlos.
prev parent reply other threads:[~2016-04-25 17:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 22:38 Roland McGrath
2016-04-12 16:01 ` Carlos O'Donell
2016-04-14 12:41 ` Tulio Magno Quites Machado Filho
2016-04-19 15:09 ` Tulio Magno Quites Machado Filho
2016-04-25 17:24 ` Carlos O'Donell [this message]
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=571E52B5.9010400@redhat.com \
--to=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=roland@hack.frob.com \
--cc=tuliom@linux.vnet.ibm.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).