Skip to content

Add explanation to buildbots.rst about triggering buildbot on a PR #1605

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 8 commits into from
Jul 23, 2025
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
Add explanation to buildbots.rst about triggering buildbot on a PR
  • Loading branch information
hoodmane committed Jul 15, 2025
commit e40058f3c50277b2502db99a2c3f604128931bca
20 changes: 20 additions & 0 deletions testing/buildbots.rst
Original file line number Diff line number Diff line change
Expand Up @@ -48,6 +48,26 @@ after each commit. In particular, reference leaks builds take several hours to
complete so they are done periodically. This is why it's important for you to
be able to check the results yourself, too.

Triggering a buildbot on a pull request
=======================================

If you want a pull request tested against a given platform, you can trigger one
or more build bots by posting a comment that begins with:

.. code-block:: none

!buildbot regex-matching-target


For example to run both the iOS and Android build bot, you can use:

.. code-block:: none

!buildbot ios|android

If this worked, bedevere-bot will post a comment indicating which build bots, if
any, were matched. If none were matched, it will tell you that too.

Checking results of automatic builds
====================================

Expand Down
Loading
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy