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
-
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.
-
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
-
Thank you for your guidance Dean!
