Continuous Integration of BitBucket pull requests & merges

Hi,

My organization is investigating the effort in switching to using BitBucket instead of TFS, and I was wondering if BuildMaster has support for doing things like continuous integration on a pull request (no deployment, just build and integrate). I know there are SCM triggers, which will work for something like a push - as long as we are willing to create a trigger for every branch we'd like to build (we have this for TFS, but it is annoying to manage). Side note - it woulde be great if the triggers had some sort of branch support!

I know we can call the api to create a package, and subsequently deploy it to an environment, but that isn't something that can easily be accomplished on the BitBucket side. There is a free plugin to call an api endpoint... but it isn't easy to chain the calls to create a package (and also needing to know the current release number), then deploy. It would be a lot easier if there were one method that could kick off a build, and use HTTP status codes to relay the result of the build/integration.

Product: BuildMaster
Version: 5.6.6

It's certainly possible in BuildMaster, but it's not a common workflow anymore. We have considered extending support, but the market generally is moving towards "many single-purpose tools" than "multi-function tools". The general flow these days looks like this:

Source >> CI >> Package >> Deploy

In this case, ProGet is the Package repository and BuildMaster is the deploy tool. The advantage to this workflow is that, the CI tool need only "create a validated package", instead of trying to deploy.

By the way, I also recommend you to look at GitLab; we switched to it after extensive evaluations of similar "simple" tools (GitHub, BitBucket), as well as the enteprrise tools (Perforce, etc).