Skip to content
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

Build workflow added to bitrise.yml on a seperate branch #599

Open
peboozt opened this issue Nov 5, 2021 · 1 comment
Open

Build workflow added to bitrise.yml on a seperate branch #599

peboozt opened this issue Nov 5, 2021 · 1 comment

Comments

@peboozt
Copy link

peboozt commented Nov 5, 2021

We host the bitrise.yml together with our codebase in our GIT repo, but cannot add or rename workflows to it and make a test run of them before merging to the main branch, as only workflows from the main branch are listed in the Schedule Build dialog.

To make the config file follow our current GIT flow, we create feature branches, make changes to code and build config there (which are often connected somehow. e.g. adding a new script to the codebase which you want to call from Bitrise), but as the workflow names are always pulled from the main branch, we cannot add new workflow names to a feature branchs bitrise.yml, and trigger them on the build server before they are actually merged to main.

It would be great if there was a possibility on the Schedule Build dialog to either:

  • fetch workflow names from the branch name you enter in the dialog
    or
  • enter a custom workflow name in the Workflow drop-down box.

Any suggestions for how to otherwise achieve this is very welcome :)

@bitce
Copy link

bitce commented Dec 6, 2021

Hi @peboozt, thanks for the feature request! This would make perfect sense. For the time being though, I would recommend considering to use the API instead of the web UI, which should allow you more freedom in this sense.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants