bitrise-io / bitrise

Bitrise runner CLI - run your automations on your Mac or Linux machine -
https://www.bitrise.io/cli
MIT License
839 stars 130 forks source link

Bitrise trigger does not work #857

Open sergeiyassir opened 1 year ago

sergeiyassir commented 1 year ago

Hey guys,

Was thinking to use the cli tool instead of REST API to start and monitor a build, but could not make it work.

I used a docker image from here, it had a c35db96d25b0 tag and the cli version inside is 2.2.3.

Here is what I get on the terminal:

root@2cf6b89cf89e:/bitrise/src# bitrise workflows
Workflows
---------
⚡️ preproductionRelease
  Title:
  Summary:
  Run with: bitrise run preproductionRelease

⚡️ productionRelease
  Title:
  Summary:
  Run with: bitrise run productionRelease

⚡️ stagingDebug
  Title:
  Summary:
  Run with: bitrise run stagingDebug

⚡️ stagingRelease
  Title:
  Summary:
  Run with: bitrise run stagingRelease

root@2cf6b89cf89e:/bitrise/src# bitrise trigger-check --push-branch add_release_signing_config
no matching pipeline & workflow found with trigger params: push-branch: add_release_signing_config, pr-source-branch: , pr-target-branch: , tag:
root@2cf6b89cf89e:/bitrise/src# bitrise trigger-check --push-branch add_release_signing_config signingRelease
no matching pipeline & workflow found with trigger params: push-branch: signingRelease, pr-source-branch: , pr-target-branch: , tag:
root@2cf6b89cf89e:/bitrise/src# bitrise trigger-check --push-branch add_release_signing_config --pattern signingRelease
no matching pipeline & workflow found with trigger params: push-branch: signingRelease, pr-source-branch: , pr-target-branch: , tag:
root@2cf6b89cf89e:/bitrise/src# bitrise trigger-check --pattern signingRelease
no matching pipeline & workflow found with trigger params: push-branch: signingRelease, pr-source-branch: , pr-target-branch: , tag:
root@2cf6b89cf89e:/bitrise/src# bitrise trigger-check signingRelease
no matching pipeline & workflow found with trigger params: push-branch: signingRelease, pr-source-branch: , pr-target-branch: , tag:
root@2cf6b89cf89e:/bitrise/src# bitrise version
2.2.3
root@2cf6b89cf89e:/bitrise/src#

Did I miss some important steps before trying to trigger the workflow?

As a side note, push-branch seem to not take its value from --push-branch option sometimes.

Thank you!

lukewakeford commented 1 year ago

Realise this was 3 weeks ago but still..

What does your trigger_map look like in your bitrise.yml?


trigger_map:
- push_branch: add_release_signing_config
  workflow: preproductionRelease
sergeiyassir commented 1 year ago

Hey @lukewakeford! There is no such key in our config, I guess this is because we do not react to events from our repo on Bitrise.