Hi,
Although I used extensively FinalBuilder in my previous company (which I left a month ago), in my current company there is no implementation of build tool.
My first priority here is automising the release proccess, in which Automise can help me a LOT (minus the ssh Linux connection which consists 20% of the rollout which does not exist yet in AM)
My question is if we decide to buy Automise and later implement FB as the build tool, will there be some kind of discount in buying FB, since it’s 90% the same software.
Thanks,
NirS
At this time we are not planning to offer an upgrade path from Automise to FinalBuilder (or from FinalBuilder to Automise).
The products will begin to separate more as time goes on too. My suggestion would be that if you will need anything to do with software development, you stick with FinalBuilder (eg. Compilers, Version Control Systems, .NET tools, etc).
A follow up question…actually I’m sharing my dilemma
My current use of FB/AM would be for deployement, i.e. killing proccesses, copying files etc. (Windows and Unix)
My future use will consist both on deployment and build management. Since FB seems a more ‘complete’ product for these, I might go for FB. The question will I miss advanced deployment related actions developed for AM.
Thanks,
NirS
The question will I miss advanced deployment related actions developed for AM.
What sort of deployment related actions are you thinking about?
We haven’t planned out too much in the way of new actions for Automise, but currently in development is an Image Manipulation action and a set of PDF actions.
.t8
Currenty the deployment related actions I will use (assuming we will decide to go with FB), are Xcopy, WMI Kill Proccess, the iterators, Wait for Proccess, Extract Version info, and XML Actions… if these will remain available in FB I don’t think I’ll have problem.
NirS
ic.
well, we certainly won't be _removing_ any functionality from FinalBuilder or Automise :)