We created a token with write_builds permission, but the actions kept failing silently and it was difficult to troubleshoot why.

We ended up providing Organization Access which resolved the issue.

It would be useful if you could set the output of the step so it could be accessed in subsequent steps (unfortunately, it doesn't look like you can access the json file across steps).

There is a useful looking test script in test/entrypoint.bats can you document how to run it? I have found the bats-core, bats-support and bats-assert projects but a quick walkthrough on how to set them up would be help a lot.

Hi folks, I can see adding WAIT functionality is on your roadmap. Do you have any idea on when that might be available?

In lieu of that I guess I could do some polling to see when the build is done?

Hey BK team, I have the need to create a pipeline trigger that is only called if a specific requirement is met. In my case, if a specific file was changed. I can see this pattern surge as people make their pipelines more and more dynamic.

I was thinking on something like:

steps:
  - trigger: "<trigger-name>"
    label: "Trigger <trigger-name>"
    skip_command: ./check-specific-file-was-changed.sh

If the command return 0, the trigger should be executed. Otherwise skip.

What do you all think? Cheers!

Hello!

I'm having trouble with this action. I set up a test repository with Buildkite GitHub App and as long as I use webhook - PR is marked green, pipeline passes on buildkite, all good.

However, when I try to use this action like so(changed org name):

name: Buildkite test

on:
  pull_request:

jobs:
  test-buildkite:
    runs-on: ubuntu-latest
    steps:
      - name: Trigger Buildkite Pipeline
        uses: buildkite/[email protected]
        env:
          BUILDKITE_API_ACCESS_TOKEN: ${{ secrets.BUILDKITE_API_ACCESS_TOKEN }}
          PIPELINE: "karol-test-org/test-pipeline"

I can see my pipeline being completed successfully on Buildkite, but the action exits with error status and no further info.

Am I doing something wrong? And - is this action still maintained?

Cheers for your help!
Karol

Maybe I'm not understanding something here so I'm happy to be proven wrong, but it looks like the example we have here: https://github.com/buildkite/trigger-pipeline-action#configuration-as-input-parameters doesn't actually work.

There's a few things missing, such asjobs:, build: and runs-on:, as well as it seems you need to use - (hyphens) instead of the underscores and buildkite-token instead of buildkite_api_access_token.

I whipped up a working one below:

on: [push]

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - name: Trigger a Buildkite Build
        uses: "buildkite/[email protected]"
        with:
          buildkite-token: ${{ secrets.TRIGGER_BK_BUILD_TOKEN }} 
          pipeline: "my-org/my-deploy-pipeline"
          branch: "main"
          commit: "HEAD"
          message:  ":github: Triggered from a GitHub Action"
          build-env-vars: '{"TRIGGERED_FROM_GHA": "true"}'
          build-meta-data: '{"FOO": "bar"}'
          ignore-pipeline-branch-filter: true   

Let me know if I'm missing something obvious.

Hi 🙂

The input parameters are not very well documented.
We don't know which are required and which are optional, whether they have default values, what their purpose is, etc.
Could you improve your documentation, please?

Currently the action does not provide any information on the cause of a failure. The API provides useful information but the action does not pass them to the user. This makes it very hard to identify the problem.

Issues #23 and #21 would benefit from such information.

PR #26 fixes this issue.