public inbox for
 help / color / mirror / Atom feed
From: Dodji Seketeli <>
To: Mark Wielaard <>
Subject: Re: buildbot users try branch builders for libabigail
Date: Wed, 20 Jul 2022 11:50:37 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <Ytc/> (Mark Wielaard's message of "Wed, 20 Jul 2022 01:35:26 +0200")

Hello Mark,

Mark Wielaard <> a écrit:

> Hi,
> I setup git users try branches for libabigail. If you have commit
> access to libabigail.git you can now push to a users/<name>/try-xxx
> branch and the buildbot will do builds and sent you (the commit
> author) email about the results. The builds are also visible at:
> My workflow to use this (if I had libabigail commit access) looks
> like:
> - git checkout -b pr29346
> - hack, hack, hack... OK, looks good to submit
> - git commit -a -m "The ultimate PR29346 fix"
> - git push origin pr29346:users/mark/try-pr29346
> - ... wait for the emails to come in or watch buildbot logs ...
> - Send in patches and mention what the try bot reported
> After your patches have been accepted you can delete the branch again:
> - git push origin :users/mark/try-pr29346
> Please use this only for patches you intend to submit and think are
> ready but want to double check. Use the GCC Compile Farm machines if
> you need to hack edit/compile/debug on a specific architecture.
> But if you really need access to one of the buildbot machines for
> investigating an issue, please contact
> The try builders also upload logs to the bunsendb. And so are
> visible here
> Please sent feedback (bad or good) to

Man, this is just great.

We need to write this on the libabigail website!

Thanks a lot.



      reply	other threads:[~2022-07-20  9:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-19 23:35 Mark Wielaard
2022-07-20  9:50 ` Dodji Seketeli [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).