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!
Multiple deployment targets on same server
-
Hi Inedo community,
we are currently evaluating BuildMaster for running our deployments of mostly .NET (ASP) based software to our Windows servers with IIS.
Right now we are missing an option to define and later select a specific deployment target on a server.
Let's say we have the same kind of software running for three different customers, each having a test and a production system, but having only two servers:
Server 1:
- Customer A - production
- Customer A - test
Server 2:
- Customer B - production
- Customer B - test
- Customer C - production
- Customer C - test
For each of these systems we have an IIS application pool and an application directory (and maybe some other configurations) that we need to define in variables somehow.
How can we model this in BuildMaster, so that we can define the variables and scripts once and then just deploy a software release to either all production systems, all test systems or just a single one out of all these systems?
We know that there is an option to assign variables to a server, but then we would need to register a server multiple times, once for each system that is running there and always with different variables.
Maybe we are missing an option or even a whole concept in BuildMaster? It would be nice if someone could help us get on track regarding the scenario described above.
Thank you very much in advance!
-
Hi @koe ,
This is definitely a problem that you can solve with BuildMaster, but before giving any kind of technical guidance, I'd like to understand the business processes.
On first glance, this sounds like one of two scenarios:
- Quasi-custom Software, where you create a customized build of a software application (perhaps bundled with their plugins, etc)
- User-driven Deployments, where you maintain a single application but deploy a new version of that application based on user requirements (new feature they requested, bug fix, etc)
Are either of those close?
Whatever the case, can you describe the decision-making process or rationale that goes into "deploy a software release to either all production systems, all test systems or just a single one out of all these systems?"
Are there different types of releases (e.g. a "patch" release of an old version)? Or is everyone "forward only, latest version"?
BuildMaster is, of course, an automation platform - but more importantly, it's about modeling process and visualization. And when it comes to process, consistency is key - even when there are variations.
We don't believe a decision like above is "arbitrary, and based on the whims of an application director", but there's probably some rationale that goes into it. So, with BuildMaster, our goal is to help get everyone on the same page about which process to follow for different releases.
Anyway, how you model this will have a big impact down the line.
Cheers,
Alana
