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!
Would like to give you some money!
-
Hi
I am about to purchase some upgrades to the express edition and I am trying to work out if I have the correct mix of enhancements.What I like to be able to do the following for a number of applications:
a) Have a standard Integration, Testing, Production workflow with: Integration with sql scripts initiated of an automated build trigged by a SCCM check in with a reduce set of unit tests. Testing initiated manually Production initiated after signed off by Manager b) Once night on Automated build based on a specified time run: 1. Restore of the current production database to a separate db to above 2. Action any sql scripts that may be integration and testing 3. Execute a complete set of complete set of unit tests against the current release/build in integration. c) Similar to above but this time, after a db restore to a different database, a complete set of tests are run against the release currently in production.So I believe I need:
Unlimited Applications - As I have more than 10
Unlimited Automatic Builds Upgrade - As app will have a sccm build and 2 recurring builds
Unlimited Environments - as the dbs will be different in build b and c to the environments in a, plus and there is no deploy required to the target environments
Multiple Promotion Workflows Upgrade - as the Automated build for b and c would be against a different workflow to standard.Do I require Multiple Active Builds - this feature I don't fully understand? Have I missed anything?Plus
I believe there is no limit in the number of database connections?My understanding that the Buildmaster tracks sql scripts with a metatable held in the database. Does the database scripts packager maintain the same table?
Thanks Tim Daborn
-
Hi Tim,
Multiple Active Builds will not auto-reject builds when another one in the same release is deployed to the environment. It's mostly used when testers need to consider which build (of many) will be promoted to the next environment.
There is a limit of "one connection per deployable" in the Express Edition and yes, the packager uses the same metadata table.
Also... as an FYI, Express Edition Upgrades do not include support/maintenance, and we are planning to phase them out soon.
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