* buildbot users try branch builders for libabigail
@ 2022-07-19 23:35 Mark Wielaard
2022-07-20 9:50 ` Dodji Seketeli
0 siblings, 1 reply; 2+ messages in thread
From: Mark Wielaard @ 2022-07-19 23:35 UTC (permalink / raw)
To: libabigail; +Cc: buildbot
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:
https://builder.sourceware.org/buildbot/#/builders?tags=libabigail-try
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.
https://cfarm.tetaneutral.net/
But if you really need access to one of the buildbot machines for
investigating an issue, please contact buildbot@sourceware.org.
The try builders also upload logs to the bunsendb. And so are
visible here https://builder.sourceware.org/testruns/
Please sent feedback (bad or good) to buildbot@sourceware.org
Cheers,
Mark
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: buildbot users try branch builders for libabigail
2022-07-19 23:35 buildbot users try branch builders for libabigail Mark Wielaard
@ 2022-07-20 9:50 ` Dodji Seketeli
0 siblings, 0 replies; 2+ messages in thread
From: Dodji Seketeli @ 2022-07-20 9:50 UTC (permalink / raw)
To: Mark Wielaard; +Cc: libabigail, buildbot
Hello Mark,
Mark Wielaard <mark@klomp.org> 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:
> https://builder.sourceware.org/buildbot/#/builders?tags=libabigail-try
>
> 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.
> https://cfarm.tetaneutral.net/
>
> But if you really need access to one of the buildbot machines for
> investigating an issue, please contact buildbot@sourceware.org.
>
> The try builders also upload logs to the bunsendb. And so are
> visible here https://builder.sourceware.org/testruns/
>
> Please sent feedback (bad or good) to buildbot@sourceware.org
Man, this is just great.
We need to write this on the libabigail website!
Thanks a lot.
Cheers,
--
Dodji
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2022-07-20 9:50 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-07-19 23:35 buildbot users try branch builders for libabigail Mark Wielaard
2022-07-20 9:50 ` Dodji Seketeli
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).