Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    Continuous Integration of BitBucket pull requests & merges

    Scheduled Pinned Locked Moved Support
    triggered-buildsbitbucketbuildmaster
    2 Posts 1 Posters 34 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • ? This user is from outside of this forum
      Guest
      last edited by

      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

      1 Reply Last reply Reply Quote 0
      • ? This user is from outside of this forum
        Guest
        last edited by

        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).

        1 Reply Last reply Reply Quote 0

        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

        With your input, this post could be even better 💗

        Register Login
        • 1 / 1
        • First post
          Last post
        Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation