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!

    Adding an ad-hoc deployment process to an existing application

    Scheduled Pinned Locked Moved Support
    3 Posts 2 Posters 16 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.
    • M Offline
      mwatt_5816
      last edited by

      I've inherited a BuildMaster instance for deployment of an application I'm responsible for, and I'm very new to BuildMaster.

      I'm looking for advice on how to add the ability to do an ad-hoc deployment to a sandbox environment for an existing application.

      The existing setup consists of a release pipeline that basically does Build -> Deploy to Test -> Deploy to Production. I want to keep that functionality, but I'm trying to support a sandbox environment that I can do a Build and Deploy as requested. This environment is potentially not going to be a permanent one, but to allow users to perform longer term configuration and workflow prototyping without being as disruptive to new features or data refreshes.

      I really don't want to perform any release operations with this build & deploy process.

      Can I accomplish this with BuildMaster? Would it be a secondary pipeline for the application that I can somehow run ad-hoc, or would it make sense to set it up as a New application with a different configuration, one that doesn't generate releases?

      Totally newbie here. Any advice is appreciated.

      dean-houstonD 1 Reply Last reply Reply Quote 0
      • dean-houstonD Offline
        dean-houston inedo-engineer @mwatt_5816
        last edited by

        Hi mwatt_5816,

        BuildMaster does support "release-less" builds, though you may need to enable it under the application's Settings > Configure Build & Release Features > Set Release Usage to optional. That will allow you to create a build that's not associated with a release.

        It's also possible to do "ad-hoc" builds (i.e. builds with no pipeline), but we don't make it easy to do in the UI because it's almost always a mistake (once you already have pipelines configured). So in your case, I think you should create a secondary pipeline for this purpose.

        -- Dean

        1 Reply Last reply Reply Quote 1
        • M Offline
          mwatt_5816
          last edited by

          Thank you for your guidance Dean!

          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