Skip to content

Commit b7cae92

Browse files
committed
[libc++] Trigger the BuildKite pipeline from Github Actions
Instead of always triggering the BuildKite pipeline and then determining whether there is anything to do, trigger it from the libc++ CI Github action. Since that Github action is only triggered when relevant files have been modified, this simplifies the triggering logic. Importantly, it will also prevent all of the monorepo CI jobs from waiting on the Buildkite pipeline to report that there's nothing to do.
1 parent c528f60 commit b7cae92

File tree

2 files changed

+13
-34
lines changed

2 files changed

+13
-34
lines changed

.github/workflows/libcxx-build-and-test.yaml

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -288,3 +288,16 @@ jobs:
288288
- name: Build and test
289289
run: |
290290
bash libcxx/utils/ci/run-buildbot ${{ matrix.config }}
291+
292+
buildkite_platforms:
293+
# needs: [ stage2 ] # TODO: temporarily always trigger
294+
runs-on: llvm-premerge-libcxx-next-runners
295+
steps:
296+
- name: Trigger Buildkite pipeline
297+
uses: buildkite/[email protected]
298+
with:
299+
buildkite_api_access_token: ${{ secrets.BUILDKITE_API_ACCESS_TOKEN }}
300+
pipeline: llvm-project/libcxx-ci
301+
branch: ${{ github.ref_name }}
302+
commit: ${{ github.sha }}
303+
message: "Triggered by GitHub Actions PR against ${{ github.ref_name }}"

libcxx/utils/ci/buildkite-pipeline-trigger.sh

Lines changed: 0 additions & 34 deletions
This file was deleted.

0 commit comments

Comments
 (0)