A new trigger for pipelines

Issue #16568 duplicate
created an issue


Are there plans to add a path trigger (or something similar) to pipelines ? It may come in handy for some use cases. Here is one :

We are working on a new serverless environment and we have a lot of seperate bits of code that get tossed to the cloud to do their work. For the moment, we cannot use bitbucket pipelines to automate deployments since the existing triggers are not working for us. All these functions are grouped in the same repo(s) :

  • It is not practical to have a repository per function since it will be a hell to set up for new recruits

  • Nor is it practical to have a branch per function since a feature may affect more than one function at once.

  • Tags don't work either since there is no way to filter what needs to be deployed and what stays still

  • Custom triggers may work but it is not much different than manual commands we use right now to deploy

Since functions count in our projects grows constantly, it would be nicer if deployments are handled automatically.

Also, combining path and branch triggers would be ideal for deploying into multiple environments.

Are there plans for an additional trigger that does the job or something similar to help with serverless development ?

Comments (3)

  1. Aneita Yang

    Hi @Amine,

    Thanks for reaching out and for the suggestion.

    We're currently tracking a similar request on issue #16560. As mentioned on that issue, we don't have plans to support this anytime soon; however, I encourage you to vote for that issue if it is something that you're interested in so that we can keep track of how many users are interested in the functionality.

  2. Log in to comment